Installing CS5 With SCCM 2007
Hi,
I have followed the instructions and used the Adobe Application Manager Enterprise to create a package to install CS5. The package was distributed via SCCM and starts to install, It installs most of the products and then encounters an error and rolls back the install, uninstalling all the components again.
Im not sure what the issue is, i have tried to remake the package and had no luck still. There are no errors in the application log in event viewer and I have attached the installation logs from \syswow64\common\adobe. The error that stands out is the following:
adobe cs5 DB001: Database file 'Install.db' does not exist
However i checked each payload component and the install.db is present, and as i said i remade the package in case the files were corrupt and had no success.
I tried analysing the logs with Adobe support advisor and it only showed one error about flash player allready being a new version (there was no flash player installed in actual fact) and another error regarding an old version of photoshop (again, there was no photoshop).
I have tried the installation on multiple machines, it fails on them all.
The last machine i tried it on was a sony vaio, i5, 6gb ram, 1gb gfx card, 500gb HDD. It was a clean install of windows 7 with all updates applied.
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Visit http://www.adobe.com/go/loganalyzer/ for more information
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
START - Installer Session
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
RIBS version: 4.0.50.0
Win OS version: 6.1.1.0 64 bit Type: 1
::START TIMER:: [Total Timer]
CHECK: Single instance running
CHECK : Credentials
Load Deployment File
Create Required Folders
Assuming install mode
Looking up install source path
Sync Media DB ...
::START TIMER:: [Sync Media DB]
Pre check media db sync
End of Pre check media db sync. Exit code: 0
:: END TIMER :: [Sync Media DB] took 3354.89 milliseconds (3.35489 seconds) DTR = 10778.3 KBPS (10.5257 MBPS)
##### Running EDT Workflow #####
Ready to initialize session to start with ...
::START TIMER:: [CreatePayloadSession]
-------------------- BEGIN - Updating Media Sources - BEGIN --------------------
Updated source path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup
Updating media info for: {02731921-5711-4E7A-A898-D6BCF0F2A1CD}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCSXSInfrastructure2-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCSXSInfrastructure2-mul\Install.db
Updating media info for: {033E378E-6AD3-4AD5-BDEB-CBD69B31046C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_ATL_x86\Microsoft_VC90_ATL_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_ATL_x86\Microsoft_VC90_ATL_x86.msi
Updating media info for: {03B6AF5B-A024-43DE-8DD2-8FB7B6A4149A}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAMP1.8-mul\AdobeAIRInstaller.exe
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAMP1.8-mul\AdobeAIRInstaller.exe
Updating media info for: {03EEF3DA-71F9-4FE5-92AD-D10142E26459}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\SiteCatalystNetAverages1-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\SiteCatalystNetAverages1-mul\Install.db
Updating media info for: {0669F23C-1B69-41B4-A3ED-4F54A5986D66}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeLinguisticsAll_x64\AdobeLinguisticsAll_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeLinguisticsAll_x64\AdobeLinguisticsAll_x64.msi
Updating media info for: {08D2E121-7F6A-43EB-97FD-629B44903403}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_CRT_x86\Microsoft_VC90_CRT_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_CRT_x86\Microsoft_VC90_CRT_x86.msi
Updating media info for: {0A6FC585-E761-4776-A4F3-BDA1E4FE1B7A}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Support\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Support\Install.db
Updating media info for: {0A9AAB1E-0FEA-1033-851A-888C0B8E78B5}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonLang-en_US\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonLang-en_US\Install.db
Updating media info for: {0D067D13-C3D7-4EA6-B346-740CD91FD547}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeBridge4-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeBridge4-mul\Install.db
Updating media info for: {0F3647F8-E51D-4FCC-8862-9A8D0C5ACF25}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_ATL_x86\Microsoft_VC80_ATL_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_ATL_x86\Microsoft_VC80_ATL_x86.msi
Updating media info for: {11C0657F-2BD4-4CBC-87F3-9455DC91886E}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRecommended_x64-mul\AdobeFontsRecommended_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRecommended_x64-mul\AdobeFontsRecommended_x64-mul.msi
Updating media info for: {14A2CC02-4638-405D-8190-ECD7BFD32D6E}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlash11-en_USLanguagePack\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlash11-en_USLanguagePack\Install.db
Updating media info for: {157D044B-C60D-1015-B0DB-A40823CC0F49}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeToolhints-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeToolhints-mul\Install.db
Updating media info for: {164965E8-4BB0-4EEB-AFBA-75785A2A2A7F}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11All\Install.db
Updating media info for: {17C6080E-F475-4B49-A30C-EEB85673E999}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFL9.9_x64-mul\AdobePDFL9.9_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFL9.9_x64-mul\AdobePDFL9.9_x64-mul.msi
Updating media info for: {1D809D80-28A4-11DF-A816-0024E8692489}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\DeviceCentral3LP-en_US\DeviceCentral3LP-en_US.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\DeviceCentral3LP-en_US\DeviceCentral3LP-en_US.msi
Updating media info for: {1D830E80-28A4-11DF-A025-0024E8692489}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\DeviceCentral3LP-en_GB\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\DeviceCentral3LP-en_GB\Install.db
Updating media info for: {1E9FC118-651D-4934-97BE-E53CAE5C7D45}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFCLOC_x86_x64\Microsoft_VC80_MFCLOC_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFCLOC_x86_x64\Microsoft_VC80_MFCLOC_x86_x64.msi
Updating media info for: {26B0DF8D-3A8D-4BA9-B131-3B0D9EE87655}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMobileExtension_Flash11-en_US\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMobileExtension_Flash11-en_US\Install.db
Updating media info for: {26B63C3A-0BFF-1033-B389-A7ACEC31657E}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppLang-en_GB\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppLang-en_GB\Install.db
Updating media info for: {2EBE92C3-F9D8-48B5-A32B-04FA5D1709FA}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeXMPPanelsAll\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeXMPPanelsAll\Install.db
Updating media info for: {2F6B67F4-A2BB-45D7-A80C-25FF646CC1C5}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAPE3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAPE3-mul\Install.db
Updating media info for: {30221E3E-4C47-4560-A296-DD9ABB500C21}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AIR2_Flash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AIR2_Flash11-mul\Install.db
Updating media info for: {37AB3C65-E02C-4DCF-B0E0-4C2E253D8FA3}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRaw6.0All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRaw6.0All\Install.db
Updating media info for: {39CB2E53-5326-4939-8B5A-0402C6EFBFE3}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorCommonSetCMYK3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorCommonSetCMYK3-mul\Install.db
Updating media info for: {3A8C7CB3-2A2E-4EB9-99C9-DF08C324BA70}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11en_USLanguagePack\AdobeFireworks11en_USLanguagePack.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11en_USLanguagePack\AdobeFireworks11en_USLanguagePack.msi
Updating media info for: {3BF96AC2-0CA1-11DF-B07B-459956D89593}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeHelp\AIRInstallerRunner.exe
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeHelp\AIRInstallerRunner.exe
Updating media info for: {3F023875-4A52-4605-9DB6-A88D4A813E8D}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRawProfile6.0All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRawProfile6.0All\Install.db
Updating media info for: {3F6B5CAC-733F-1029-B5BD-C0F5E35809F0}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeBuzzword-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeBuzzword-mul\Install.db
Updating media info for: {40F95A03-885A-45fb-9A14-486BEFEDDF34}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashPlayer10_plRel_mul\AdobeFlashPlayer10_plRel_mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashPlayer10_plRel_mul\AdobeFlashPlayer10_plRel_mul.msi
Updating media info for: {4438C826-1FD0-4D04-A70B-24FE1580AB21}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMiniBridge1-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMiniBridge1-mul\Install.db
Updating media info for: {4569AD91-47F4-4D9E-8FC9-717EC32D7AE1}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_CRT_x86_x64\Microsoft_VC80_CRT_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_CRT_x86_x64\Microsoft_VC80_CRT_x86_x64.msi
Updating media info for: {4C08199E-0D93-4227-8325-F024E71CA7A1}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeSING3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeSING3-mul\Install.db
Updating media info for: {50A16F0B-47DA-4583-B4FE-E026719A2024}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_US_x64\AdobePhotoshop12-en_US_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_US_x64\AdobePhotoshop12-en_US_x64.msi
Updating media info for: {54F4466A-091A-46DA-B697-43D55CEF9DF6}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorJA_ExtraSettings3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorJA_ExtraSettings3-mul\Install.db
Updating media info for: {56540320-C921-1029-83D9-FE864D1FC1DF}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeReviewPanel2-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeReviewPanel2-mul\Install.db
Updating media info for: {5658F35F-15B9-1033-8337-97B78F2D0BE0}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7IconHandler64-mul\AdobeInDesign7IconHandler64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7IconHandler64-mul\AdobeInDesign7IconHandler64-mul.msi
Updating media info for: {579FDC01-BA85-49E7-B16A-2C4CB55F7ACD}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMobileExtension_Flash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeMobileExtension_Flash11-mul\Install.db
Updating media info for: {5E08533A-2C1B-469D-AFD5-953C9D00031F}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\BrowserLabCSLive-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\BrowserLabCSLive-mul\Install.db
Updating media info for: {61A3D10A-AA4D-4E4C-B9DB-6A08D318EA41}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRaw6.0All-x64\AdobeCameraRaw6.0All-x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCameraRaw6.0All-x64\AdobeCameraRaw6.0All-x64.msi
Updating media info for: {635DCFA5-3A47-4452-AEC7-D3B23FFE929D}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\iPhone_Flash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\iPhone_Flash11-mul\Install.db
Updating media info for: {635FED5B-2C6D-49BE-87E6-7A6FCD22BC5A}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_MFC_x86\Microsoft_VC90_MFC_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_MFC_x86\Microsoft_VC90_MFC_x86.msi
Updating media info for: {66173EC7-974E-4652-9468-4A93D2481BF0}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeStoryExtension-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeStoryExtension-mul\Install.db
Updating media info for: {667C8B6C-3EAF-4646-A8EC-D85CCC4D3D84}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Core_x64\AdobePhotoshop12-Core_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Core_x64\AdobePhotoshop12-Core_x64.msi
Updating media info for: {68CEA5C9-2964-4ECB-84A4-D77C511332BC}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AMECore5All_x64\AMECore5All_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AMECore5All_x64\AMECore5All_x64.msi
Updating media info for: {694213D7-1E0E-4C8F-B822-E2E3680C0FCE}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AMECore5All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AMECore5All\Install.db
Updating media info for: {69582206-7E5D-4476-A8F4-ECF90E9C8A69}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_US\AdobePhotoshop12-en_US.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_US\AdobePhotoshop12-en_US.msi
Updating media info for: {6B485102-4593-43F6-BA45-F14D690B0C64}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeSuiteSharedConfiguration-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeSuiteSharedConfiguration-mul\Install.db
Updating media info for: {6C7D437A-D2E9-4FE9-A4D9-A6329860835C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeLinguisticsAll\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeLinguisticsAll\Install.db
Updating media info for: {6D96660C-1444-410E-9A84-681C0AFB8937}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFSettings10-mul\AdobePDFSettings10-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFSettings10-mul\AdobePDFSettings10-mul.msi
Updating media info for: {6E505C8F-2896-11DF-9B64-0013724DD917}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDeviceCentral3-all\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDeviceCentral3-all\Install.db
Updating media info for: {6F29BE46-E5F3-4146-8A84-20301E5C985A}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorEU_ExtraSettings3-mul\AdobeColorEU_ExtraSettings3-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorEU_ExtraSettings3-mul\AdobeColorEU_ExtraSettings3-mul.msi
Updating media info for: {6F3A624B-1B72-4081-96E8-23261F389C5C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeTypeSupport10-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeTypeSupport10-mul\Install.db
Updating media info for: {73A4DC5E-226E-42BA-8ECA-2822592AC044}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeVideoProfilesCS3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeVideoProfilesCS3-mul\Install.db
Updating media info for: {7745F18B-FD8A-4011-BE16-588900C503D0}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashFonts1-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashFonts1-mul\Install.db
Updating media info for: {78A53622-CDBA-49D1-A3D0-D563FB398D0C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorCommonSetRGB3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorCommonSetRGB3-mul\Install.db
Updating media info for: {7A33510F-1580-42C2-877E-8C5502566292}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAPE3_x64-mul\AdobeAPE3_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAPE3_x64-mul\AdobeAPE3_x64-mul.msi
Updating media info for: {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Core\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-Core\Install.db
Updating media info for: {7E5AA19B-0B85-4f44-BA26-728851489200}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashPlayer10_axRel_mul\AdobeFlashPlayer10_axRel_mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashPlayer10_axRel_mul\AdobeFlashPlayer10_axRel_mul.msi
Updating media info for: {7EB208EE-0C2B-1033-A6DC-E1BD0289A1F4}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppLang-en_US\AdobeInDesign7AppLang-en_US.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppLang-en_US\AdobeInDesign7AppLang-en_US.msi
Updating media info for: {7F9C94CD-0BAC-4F8F-8990-6A5886F4D550}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRequired_x64-mul\AdobeFontsRequired_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRequired_x64-mul\AdobeFontsRequired_x64-mul.msi
Updating media info for: {805ABF27-1582-1033-B4AC-82A1DE0DD827}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonBase-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonBase-mul\Install.db
Updating media info for: {8557397C-A42D-486F-97B3-A2CBC2372593}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_ATL_x86_x64\Microsoft_VC90_ATL_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_ATL_x86_x64\Microsoft_VC90_ATL_x86_x64.msi
Updating media info for: {87AFDFF2-D852-4B1F-ABFB-0EAFA5A39B7B}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_GB\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_GB\Install.db
Updating media info for: {8CCA90E1-F5BA-456F-84BF-AD5FB2CCE13F}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCSXSExtensions2-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCSXSExtensions2-mul\Install.db
Updating media info for: {925D058B-564A-443A-B4B2-7E90C6432E55}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_ATL_x86_x64\Microsoft_VC80_ATL_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_ATL_x86_x64\Microsoft_VC80_ATL_x86_x64.msi
Updating media info for: {925ED7E4-E1B6-4544-8141-1C98A18D2E2E}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeOutputModuleAll\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeOutputModuleAll\Install.db
Updating media info for: {92A3CA0D-55CD-4C5D-BA95-5C2600C20F26}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_CRT_x86_x64\Microsoft_VC90_CRT_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_CRT_x86_x64\Microsoft_VC90_CRT_x86_x64.msi
Updating media info for: {92D58719-BBC1-4CC3-A08B-56C9E884CC2C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_CRT_x86\Microsoft_VC80_CRT_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_CRT_x86\Microsoft_VC80_CRT_x86.msi
Updating media info for: {955EB78F-C938-4EA8-8470-C6EA71685834}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AIR2_Flash11-en_US\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AIR2_Flash11-en_US\Install.db
Updating media info for: {966B69F2-0FBD-1033-B01C-D13C02FFF33F}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonLang-en_GB\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7CommonLang-en_GB\Install.db
Updating media info for: {98DD55B6-C58C-462F-B8A4-F0585BFEBB15}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCMaps3_x64-mul\AdobeCMaps3_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCMaps3_x64-mul\AdobeCMaps3_x64-mul.msi
Updating media info for: {9A8B01C5-78D1-465F-B5F6-BD59B7800EC7}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeTypeSupport10_x64-mul\AdobeTypeSupport10_x64-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeTypeSupport10_x64-mul\AdobeTypeSupport10_x64-mul.msi
Updating media info for: {9B97EC91-B3FD-4BFF-88FC-5345A26AC2E7}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15-mul\Install.db
Updating media info for: {A1BC7068-C1BA-410F-8B9A-DB807C803DE2}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDesignPremium5-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDesignPremium5-mul\Install.db
Updating media info for: {A472B9E4-0AFF-4F7B-B25D-F64F8E928AAB}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_MFC_x86_x64\Microsoft_VC90_MFC_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC90_MFC_x86_x64\Microsoft_VC90_MFC_x86_x64.msi
Updating media info for: {A47C8AE9-D51B-4A58-A051-396158FC3012}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_GB_x64\AdobePhotoshop12-en_GB_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePhotoshop12-en_GB_x64\AdobePhotoshop12-en_GB_x64.msi
Updating media info for: {A8798E04-96FF-4564-9157-0D4C89CB794C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDynamiclinkSupport5All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDynamiclinkSupport5All\Install.db
Updating media info for: {AE9B837F-D135-42FC-BE03-33545B5DCBDC}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeWinSoftLinguisticsPluginAll\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeWinSoftLinguisticsPluginAll\Install.db
Updating media info for: {B55FDCCB-8A45-4943-8D90-585C3490A032}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeWinSoftLinguisticsPluginAll_x64\AdobeWinSoftLinguisticsPluginAll_x64.ms i
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeWinSoftLinguisticsPluginAll_x64\AdobeWinSoftLinguisticsPluginAll_x64.ms i
Updating media info for: {B60B8713-F828-44F9-BEEE-7596F814E540}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorEU_Recommended3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorEU_Recommended3-mul\Install.db
Updating media info for: {BAE5212B-6651-4AD8-B26A-1B284D2665C6}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFL9.9-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFL9.9-mul\Install.db
Updating media info for: {BB024724-14D5-4AB6-B21C-74EDA63A0A39}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\HIL_Help_Search\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\HIL_Help_Search\Install.db
Updating media info for: {BD0D6363-E961-410F-8BF4-ECD8795F3923}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCMaps3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeCMaps3-mul\Install.db
Updating media info for: {BEC5B482-32A1-43E0-B7F7-9BF9592A1069}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorNA_ExtraSettings3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorNA_ExtraSettings3-mul\Install.db
Updating media info for: {C79312BD-3E76-4474-A10C-1435D1856A4B}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDreamweaver11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDreamweaver11-mul\Install.db
Updating media info for: {C8C1BAD5-54E6-4146-AD07-3A8AD36569C3}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFC_x86_x64\Microsoft_VC80_MFC_x86_x64.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFC_x86_x64\Microsoft_VC80_MFC_x86_x64.msi
Updating media info for: {CBDD7465-CE11-4A58-9497-C370B65923F1}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRequired-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRequired-mul\Install.db
Updating media info for: {CFA46C39-C539-4BE9-9364-495003C714AD}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\SwitchBoard2.0All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\SwitchBoard2.0All\Install.db
Updating media info for: {CFC9F871-7C40-40B6-BE4A-B98A5B309716}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlash11-mul\Install.db
Updating media info for: {D0DAEA50-AD52-4BF9-AD5F-3E09564A8692}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15en_GBLanguagePack\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15en_GBLanguagePack\Install.db
Updating media info for: {D1A19B02-817E-4296-A45B-07853FD74D57}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFC_x86\Microsoft_VC80_MFC_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFC_x86\Microsoft_VC80_MFC_x86.msi
Updating media info for: {D26EEF95-420A-4726-B85D-AFBE752EF526}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorNA_Recommended3-mul\AdobeColorNA_Recommended3-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorNA_Recommended3-mul\AdobeColorNA_Recommended3-mul.msi
Updating media info for: {D31D91FE-F0E8-4DF1-812C-9400BE92A386}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorPhotoshop3-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorPhotoshop3-mul\Install.db
Updating media info for: {D3A8C87E-ED6A-41DB-8B21-C29EDA65B154}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15en_USLanguagePack\AdobeIllustrator15en_USLanguagePack.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeIllustrator15en_USLanguagePack\AdobeIllustrator15en_USLanguagePack.msi
Updating media info for: {D5CC77BE-BC5B-424E-8E45-DF60AFF7BE9C}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\aifsdk-win\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\aifsdk-win\Install.db
Updating media info for: {D92BBB52-82FF-42ED-8A3C-4E062F944AB7}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFCLOC_x86\Microsoft_VC80_MFCLOC_x86.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Microsoft_VC80_MFCLOC_x86\Microsoft_VC80_MFCLOC_x86.msi
Updating media info for: {DE99CD25-C87E-499F-AFB8-88D00F0BAEB3}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFSettings10-ja_JP\AdobePDFSettings10-ja_JP.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobePDFSettings10-ja_JP\AdobePDFSettings10-ja_JP.msi
Updating media info for: {DEC9BB26-1381-1033-A965-E3BD5F2EF8BC}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppBase2-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppBase2-mul\Install.db
Updating media info for: {E319B9F9-4DE6-462C-970B-77D06C7807EE}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Players_Flash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\Players_Flash11-mul\Install.db
Updating media info for: {E39A5ABD-516B-46F9-A042-694BBA6A4E08}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRecommended-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFontsRecommended-mul\Install.db
Updating media info for: {E3E040E8-4CCD-4C71-8BAF-80BB2AD5DA04}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDreamweaver11en_USLanguagePack\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeDreamweaver11en_USLanguagePack\Install.db
Updating media info for: {E4CB336B-159D-1033-B84D-B9A01A0BE4A9}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7IconHandler-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7IconHandler-mul\Install.db
Updating media info for: {E4E188D2-27D5-4E4C-92CE-87F9D24AD2F6}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeExtensionManager5.0All\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeExtensionManager5.0All\Install.db
Updating media info for: {E5087BCA-6496-47A7-B9C4-B85D1CF062AE}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorJA_Recommended3-mul\AdobeColorJA_Recommended3-mul.msi
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeColorJA_Recommended3-mul\AdobeColorJA_Recommended3-mul.msi
Updating media info for: {E5DD149F-8370-48F9-A32C-2E3DC776CFFB}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeJRECS5-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeJRECS5-mul\Install.db
Updating media info for: {E8815668-95B0-443D-AC92-2BFD7DD8F16A}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashCatalyst-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFlashCatalyst-mul\Install.db
Updating media info for: {E995AC53-954A-48D2-A861-613B8D42A9BE}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeExtendScriptToolkit3.5.0-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeExtendScriptToolkit3.5.0-mul\Install.db
Updating media info for: {F1599C36-2EAB-448F-B8F9-7DBEE9D5B345}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\TLF_Flash11-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\TLF_Flash11-mul\Install.db
Updating media info for: {F6CCA85F-7527-4AFF-82B6-26532A74A244}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11en_GBLanguagePack\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeFireworks11en_GBLanguagePack\Install.db
Updating media info for: {F6FA54C9-3E8F-4416-905C-DA5398DF9640}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAIR1.5.3-mul\AdobeAIRInstaller.exe
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeAIR1.5.3-mul\AdobeAIRInstaller.exe
Updating media info for: {F9766AC1-1461-1033-B862-DF8FE1C033BE}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppBase-mul\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppBase-mul\Install.db
Updating media info for: {FD5603A3-1375-1033-872D-8F09140FFDB2}
NOTE: Ignoring media info and setting media path as: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppFSet-Roman\Install.db
Type: 0, Volume Order: 1, Media Name:
Path: C:\Windows\SysWOW64\CCM\Cache\ATS00059.1.S-1-5-21-3366194839-456487643-3404528383-2135\\S etup\payloads\AdobeInDesign7AppFSet-Roman\Install.db
-------------------- END - Updating Media Sources - END --------------------
[ 1776] Mon Apr 23 12:37:13 2012 INFO
Supported RIBS version range: [0.0.66.0,4.0.50.0]
----------------- CreatePayloadSession: machine is x64 ---------------
______ Verify Dependency Subscribers ______
BEGIN Operation order for all session payloads: mediaGroup (requires,satisfies)
{08D2E121-7F6A-43EB-97FD-629B44903403} Microsoft_VC90_CRT_x86 1.0.0.0: 1 (0,17)
{92D58719-BBC1-4CC3-A08B-56C9E884CC2C} Microsoft_VC80_CRT_x86 1.0.0.0: 2 (0,16)
{D92BBB52-82FF-42ED-8A3C-4E062F944AB7} Microsoft_VC80_MFCLOC_x86 1.0.0.0: 3 (0,12)
{D1A19B02-817E-4296-A45B-07853FD74D57} Microsoft_VC80_MFC_x86 1.0.0.0: 3 (0,12)
{2F6B67F4-A2BB-45D7-A80C-25FF646CC1C5} Adobe Player for Embedding 3.1.0.0: 4 (0,11)
{635FED5B-2C6D-49BE-87E6-7A6FCD22BC5A} Microsoft_VC90_MFC_x86 1.0.0.0: 5 (0,10)
{033E378E-6AD3-4AD5-BDEB-CBD69B31046C} Microsoft_VC90_ATL_x86 1.0.0.0: 6 (0,9)
{E5DD149F-8370-48F9-A32C-2E3DC776CFFB} AdobeJRE 1.6.0.0: 7 (0,6)
{3F023875-4A52-4605-9DB6-A88D4A813E8D} Camera Profiles Installer 6.0.0.0: 7 (0,6)
{6B485102-4593-43F6-BA45-F14D690B0C64} Suite Shared Configuration CS5 2.0.0.0: 8 (3,10)
{02731921-5711-4E7A-A898-D6BCF0F2A1CD} Adobe CSXS Infrastructure CS5 2.0.0.0: 9 (3,8)
{BD0D6363-E961-410F-8BF4-ECD8795F3923} AdobeCMaps CS5 3.0.0.0: 10 (0,7)
{6F3A624B-1B72-4081-96E8-23261F389C5C} AdobeTypeSupport CS5 10.0.0.0: 10 (0,7)
{0F3647F8-E51D-4FCC-8862-9A8D0C5ACF25} Microsoft_VC80_ATL_x86 1.0.0.0: 10 (0,7)
{925ED7E4-E1B6-4544-8141-1C98A18D2E2E} AdobeOutputModule 3.0.0.0: 11 (0,6)
{BAE5212B-6651-4AD8-B26A-1B284D2665C6} AdobePDFL CS5 9.9.0.0: 11 (0,6)
{CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0: 12 (2,5)
{A8798E04-96FF-4564-9157-0D4C89CB794C} DynamiclinkSupport 5.0.0.0: 13 (3,5)
{92A3CA0D-55CD-4C5D-BA95-5C2600C20F26} Microsoft_VC90_CRT_x86_x64 1.0.0.0: 14 (0,4)
{8557397C-A42D-486F-97B3-A2CBC2372593} Microsoft_VC90_ATL_x86_x64 1.0.0.0: 15 (0,3)
{A472B9E4-0AFF-4F7B-B25D-F64F8E928AAB} Microsoft_VC90_MFC_x86_x64 1.0.0.0: 15 (0,3)
{3BF96AC2-0CA1-11DF-B07B-459956D89593} AdobeHelp 1.0.0.0: 16 (0,10)
{E4E188D2-27D5-4E4C-92CE-87F9D24AD2F6} Adobe Extension Manager CS5 5.0.0.0: 17 (6,8)
{2EBE92C3-F9D8-48B5-A32B-04FA5D1709FA} Adobe XMP Panels CS5 3.0.0.0: 18 (0,7)
{E995AC53-954A-48D2-A861-613B8D42A9BE} Adobe ExtendScript Toolkit CS5 3.5.0.0: 19 (5,7)
{37AB3C65-E02C-4DCF-B0E0-4C2E253D8FA3} Photoshop Camera Raw 6.0.0.0: 20 (1,4)
{8CCA90E1-F5BA-456F-84BF-AD5FB2CCE13F} Adobe CSXS Extensions CS5 2.0.0.0: 21 (0,7)
{39CB2E53-5326-4939-8B5A-0402C6EFBFE3} AdobeColorCommonSetCMYK 3.0.0.0: 22 (0,5)
{78A53622-CDBA-49D1-A3D0-D563FB398D0C} AdobeColorCommonSetRGB 3.0.0.0: 22 (0,5)
{6F29BE46-E5F3-4146-8A84-20301E5C985A} AdobeColorEU CS5 3.0.0.0: 22 (0,5)
{B60B8713-F828-44F9-BEEE-7596F814E540} AdobeColorEU CS5 3.0.0.0: 22 (0,5)
{54F4466A-091A-46DA-B697-43D55CEF9DF6} AdobeColorJA CS5 3.0.0.0: 22 (0,5)
{E5087BCA-6496-47A7-B9C4-B85D1CF062AE} AdobeColorJA CS5 3.0.0.0: 22 (0,5)
{BEC5B482-32A1-43E0-B7F7-9BF9592A1069} AdobeColorNA CS5 3.0.0.0: 22 (0,5)
{D26EEF95-420A-4726-B85D-AFBE752EF526} AdobeColorNA CS5 3.0.0.0: 22 (0,5)
{AE9B837F-D135-42FC-BE03-33545B5DCBDC} Adobe WinSoft Linguistics Plugin CS5 1.2.0.0: 23 (0,4)
{0A6FC585-E761-4776-A4F3-BDA1E4FE1B7A} Adobe Photoshop CS5 Support 12.0.0.0: 24 (0,2)
{DEC9BB26-1381-1033-A965-E3BD5F2EF8BC} Adobe InDesign CS5 Application Base Files2 7.0.0.0: 25 (0,1)
{FD5603A3-1375-1033-872D-8F09140FFDB2} Adobe InDesign CS5 Application Feature Set Files 7.0.0.0: 25 (0,1)
{805ABF27-1582-1033-B4AC-82A1DE0DD827} Adobe InDesign CS5 Common Base Files 7.0.0.0: 25 (0,1)
{925D058B-564A-443A-B4B2-7E90C6432E55} Microsoft_VC80_ATL_x86_x64 1.0.0.0: 25 (0,1)
{4569AD91-47F4-4D9E-8FC9-717EC32D7AE1} Microsoft_VC80_CRT_x86_x64 1.0.0.0: 25 (0,1)
{1E9FC118-651D-4934-97BE-E53CAE5C7D45} Microsoft_VC80_MFCLOC_x86_x64 1.0.0.0: 25 (0,1)
{C8C1BAD5-54E6-4146-AD07-3A8AD36569C3} Microsoft_VC80_MFC_x86_x64 1.0.0.0: 25 (0,1)
{D5CC77BE-BC5B-424E-8E45-DF60AFF7BE9C} Pixel Bender Toolkit 2.0.0.0: 26 (2,1)
{F6FA54C9-3E8F-4416-905C-DA5398DF9640} Adobe AIR 1.5.3.0: 27 (0,8)
{03B6AF5B-A024-43DE-8DD2-8FB7B6A4149A} Adobe Media Player 1.8.0.0: 27 (0,8)
{56540320-C921-1029-83D9-FE864D1FC1DF} Adobe ReviewPanel CS5 2.0.0.0: 28 (0,6)
{6E505C8F-2896-11DF-9B64-0013724DD917} DeviceCentral 3.0.0.0: 29 (3,6)
{1D809D80-28A4-11DF-A816-0024E8692489} DeviceCentral_DeviceCentral3LP-en_US 3.0.0.0: 30 (0,0)
{1D830E80-28A4-11DF-A025-0024E8692489} DeviceCentral_DeviceCentral3LP-en_GB 3.0.0.0: 30 (0,0)
{6D96660C-1444-410E-9A84-681C0AFB8937} PDF Settings CS5 10.0.0.0: 31 (0,5)
{DE99CD25-C87E-499F-AFB8-88D00F0BAEB3} PDF Settings CS5 10.0.0.0: 31 (0,5)
{6C7D437A-D2E9-4FE9-A4D9-A6329860835C} Adobe Linguistics CS5 5.0.0.0: 32 (1,5)
{0D067D13-C3D7-4EA6-B346-740CD91FD547} Adobe Bridge CS5 4.0.0.0: 33 (18,5)
{66173EC7-974E-4652-9468-4A93D2481BF0} CSXS Story Extension 1.0.0.0: 34 (0,4)
{BB024724-14D5-4AB6-B21C-74EDA63A0A39} HIL Help Search 1.0.0.0: 34 (0,4)
{E39A5ABD-516B-46F9-A042-694BBA6A4E08} Recommended Common Fonts Installation 1.0.0.0: 34 (0,4)
{CBDD7465-CE11-4A58-9497-C370B65923F1} Required Common Fonts Installation 1.0.0.0: 34 (0,4)
{03EEF3DA-71F9-4FE5-92AD-D10142E26459} SiteCatalyst NetAverages 1.0.0.0: 34 (0,4)
{5E08533A-2C1B-469D-AFD5-953C9D00031F} Adobe BrowserLab CS Live 1.0.0.0: 35 (0,3)
{4438C826-1FD0-4D04-A70B-24FE1580AB21} Adobe Mini Bridge CS5 1.0.0.0: 36 (3,3)
{68CEA5C9-2964-4ECB-84A4-D77C511332BC} Adobe Media Encoder CS5 X64 5.0.0.0: 37 (4,3)
{694213D7-1E0E-4C8F-B822-E2E3680C0FCE} Adobe Media Encoder CS5 5.0.0.0: 38 (8,3)
{7E5AA19B-0B85-4f44-BA26-728851489200} Adobe Flash Player 10 ActiveX 10.0.0.0: 39 (0,2)
{40F95A03-885A-45fb-9A14-486BEFEDDF34} Adobe Flash Player 10 Plugin 10.0.0.0: 39 (0,2)
{7A33510F-1580-42C2-877E-8C5502566292} Adobe Player for Embedding x64 3.1.0.0: 39 (0,2)
{B55FDCCB-8A45-4943-8D90-585C3490A032} Adobe WinSoft Linguistics Plugin CS5 x64 1.2.0.0: 39 (0,2)
{98DD55B6-C58C-462F-B8A4-F0585BFEBB15} AdobeCMaps x64 CS5 3.0.0.0: 39 (0,2)
{D31D91FE-F0E8-4DF1-812C-9400BE92A386} AdobeColorPhotoshop CS5 3.0.0.0: 39 (0,2)
{73A4DC5E-226E-42BA-8ECA-2822592AC044} AdobeColorVideoProfilesCS CS5 3.0.0.0: 39 (0,2)
{17C6080E-F475-4B49-A30C-EEB85673E999} AdobePDFL x64 CS5 9.9.0.0: 39 (0,2)
{9A8B01C5-78D1-465F-B5F6-BD59B7800EC7} AdobeTypeSupport x64 CS5 10.0.0.0: 39 (0,2)
{61A3D10A-AA4D-4E4C-B9DB-6A08D318EA41} Photoshop Camera Raw (64 bit) 6.0.0.0:
Hi Andrew,
May i know how did you created the package?
Did you saved the package locally or on a server?
Where were the installation files stored? Were they stored locally or on a server?
Did you follow the steps mentioned under the Adobe Deployment guide?
Did you try to actually run the setup file and install CS5 locally?
I would recommend you to take a fresh machine and create the CS5 package locally once again by following the steps mentioned in the above guide and then "Test the Package"(page 37) and check if the issue is with the package or the actual installation files.
Please feel free to respond to this thread if you have any questions about the steps listed within the document. If you could also respond with the specific error message you receive, It would be appreciated.
Regards
Arpit
Similar Messages
-
SCCM 2012 R2 coexist with SCCM 2007 - DPs issue
Hi all,
I have a SCCM 2012 R2 which coexists with SCCM 2007 and I'm not interested in a migration, but my question concerning the use of DPs. Is it possible for 2012 R2 clients to use a 2007 DPs, i.e. are there settings for a sort of compatibility? I've looked among
links, but most of them are related to migration.
Please advise,
DomenicoNo, you can only share a distribution point during a migration between a source and destination hierarchy (see also:
http://technet.microsoft.com/en-us/library/gg712275.aspx). Without a migration that's not possible.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Can you deploy an application sequenced with App-V v5 with SCCM 2007?
We are currently in the process of upgrading to SCCM 2012. We are also embarking on testing App-V v5. Can we deploy sequenced applications from App-V v5 using SCCM 2007? What limitations will exist with SCCM 2007? What release of
SCCM 2007 should we be at for App-V v5 sequenced applications to be deployed and/or streamed?This KB article is now available: Supported Configuration Manager and Microsoft Application Virtualization scenarios
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V -
Hello,
i have to make inventory with SCCM 2007.My boss asked me to collect important information (from hardwares and softwares) for both .The problem is that he didn't specify me whcih informations to collect.He just told me to do it seems like i'm
the the workstation infrastructure manager and asked myself which crucial informations i have to collect.For information,we have both laptops and desktops in our infrastructure.And we have two types of OS for our workstation:Windows XP and windows 7.
I really need help to know which crucial information do i have to collect.
Thank you in advance yor all your propositions.You can refer this link for inventory : http://technet.microsoft.com/en-us/library/bb693889.aspx
Later you can decide on the type of inventory.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread. -
For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007
While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
Command Line: x86\Silverlight.exe /q (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
On the Advanced tab: Suppress program notifications
All other options leave default.
2. Name: Visual C++ x86
Command Line: x86\vcredist_x86.exe /q
On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
Environment and Advanced tabs: same as Silverlight
(If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
(Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes. -
Photoshop Elements 8.0: deplovment with SCCM 2007
Hello
We are currently planning the transition to Windows 7 Enterprise.
The deployment will take place with MS SCCM 2007 - we could not find any policies regarding this case.
We need to know if Photoshop Elements 8.0 with the following client applications, SCCM and standard user-rights is running.
Used software products / local application deployed on clients:
• Microsoft Windows 7 Enterprise
• Internet Explorer 8.0
• Adobe Flash Player 10.0.32.18
• Adobe Shockwave Player 11.5.2
• Adobe Acrobat Reader 9.2
• Windows Media Player 12.0
• Microsoft Office 2007 Enterprise mit SP2
• Sun Java Runtime Environment (JRE) 6.17
• Microsoft .NET Framework 3.5
• Ghostscript 8.7
• Software-Deployment: Microsoft SCCM 2007 R2 SP2
• Server-Plattform: Microsoft Windows Server 2008R2
• Standard User-Rights
We ask for verification of requirements, whether the necessary conditions are met by PSE 8.0.
Best wishes,
SimonHi Simon,
I would request you to contact the Adobe Tech Support/Customer Care team and they should able to provide a confirmation on these queries.
As per my knowledge, we dont impose any explicit restrictions on PSE working with Ms SCCM 2007/Server 2008/ or with Standard User Rights.
But for installing PSE and doing a certain operations, you need to have admin rights.
Again, I would request you to get in touch with support team and get a confirmation.
Regards,
Ankush -
Updates failed to install after deployment - SCCM 2007
Hi folks,
I wonder could anyone help!
We deployed JAVA 7 U 45 last night using SCCM 2007 and most went out ok although some computers keep showing up the Config Manager – Available Software Updates and showing the status as failed.
Can someone please tell me how I get a list of the PCs that the update successfully went out to and was installed and how do I find out which computers failed to get the update or failed to successfully install it.
I see under Deployment Status machines targeted i.e. 50 and installed says 30 and failed says 5 but how do I actually see the computers for those categories?
I was looking in the event viewer on a PC I know had issues with the update and I can’t see any errors in the Setup log for the JAVA rollout using SCOM so wonder could you tell me the best way for me to see why the updates failed?
l final question is if I have multiple versions of Java on my PC how do I set which version I want as the default version for some applications to use as some applications need different versions of JAVA.
Any advice greatly appreciated!
Thanks,
BonemisterHello, we do not use SCCM for Windows updates but I think that error msg. Souns like your updates deadline is coming. You can choose the default client settings about the pop-ups and all. Check this article i think it is the: "Hide all deployments
from end users" This setting specifies that all deployments are hidden when they are received on client computers. Use this setting to deploy software updates to computers without any display notifications or notification area icons. Also, end users will
not be able to open the Available Software Updates dialog box to manually install updates. By default, this setting is not enabled. http://technet.microsoft.com/en-us/library/bb632393.aspx
EDIT: Also if you set an deadline for the advertisement you may see this error msg. You can adjust this by changing eather the advertisement (when you create it "display notifications") or if you want to supress all the notificatins you can just change
the default agent settings. -
SCCM 2012 Client Communication Issue with SCCM 2007
My Clients was installed SCCM 2007 client version but somehow those clients reporting to SCCM 2012 Server
Note : My SCCM 2007 Server still active mode . and the SCCM 2007 client IP boundaries was not added into SCCM 2012 server
But still communicating to SCCM 2012 , what is the root cause ?
Best Regard's KrishnaEither, during the client installation the client was manually assigned to the ConfigMgr 2012 site (by specifying the site code), or during the client installation the client was auto assigned to the ConfigMgr 2012 site (that can only happen when there
is an overlap in the boundaries and that doesn't have to be the same type of boundary).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Lenovo X1 Carbon PXe boot errors with SCCM 2007
I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1. I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
Now, I have the the following drivers in the boot.wim file:
x86 -
1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
2. PCI bus
3. Intel ICHR/DO/DH SATA AHCI Controller
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
x64 -
1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
2. PCI Bus
3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
All other hardware works fine. Any suggestions greatly welcomed.
Cheers - Mark.Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac. -
Adobe Flash 11.3.300.257 Install issue with SCCM
Hello,
I've been using SCCM (Currently 2007 R3) to install Flash at my orginization for several years. Always setup the same way and always worked. Until now.
I create a distribution, set the install to be `msiexec /i install_flash_player_11_active_x_32bit.msi /qn`, create an advertisement, assign it to a collection, and wait.
On my two test boxes (One Windows 7 fully patches and one Windows XP fully patched) I get the same error.
Windows Installer per-user elevation of this program ("010004B5" - "Install Flash") failed for advertisement "01022398".This program was started. Please check the status of this program to determine whether or not it was completed sucessfully Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations. Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.
The program does not run and Flash is not installed.
I know windows installer is fine so It has to be the msi.
Anybody else having this issue?
Thanks,
-eddyHi Cris,
I modified my install to be `msiexec /i install_flash_player_11_active_x_32bit.msi /qn /L+* "C:\foo\flash.log"` and gave it another run.
The good news is that it made the flash.log. The bad news is that it is empty. I'm going to try again with the x and v extra logging.
I'll let you know.
Thanks,
-eddy -
Install CS5 with existing serial number using CS6 link in adobe
I purchased a student version of CS5 so downloaded a trial and which I activated iwth my serial number. I need to reinstall it on my computer, but all the adobe links have changed the trial version to CS6. If I install CS6 trial, then activate with my CS5 serial number, will I get CS5?
CS5 and CS6 are completely different products. Try this:
Direct Download Links for Adobe Software
Mylenium -
Installing cs5 with laptop 1366x768 resolution
will the install work out? doI need a higher res monitor for the install?
once I do get it installed will that res be ok for editing without an external monitor?
Mikehttp://www.adobe.com/products/premiere/systemreqs/
1280x900 display with OpenGL 2.0–compatible graphics card -
Problems with Adobe Premiere Elements 10 silent installation with SCCM 2007
Hi, i have some issues when i try to install Premiere Elements 10 from Config Manager.
I have followed these instructions:
http://www.appdeploy.com/packages/detail.asp?id=2331
If i try this commandoline:
setup.exe" /L1033 /S /V“SERIALNUMBER=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx COUNTRY=xxx /qn" it works when i run this locally, but not from Config manager, i get an exit code 1203.
Can someone tell me what i can change in the MSI, so i can use the MSI installer?Well, if i use this commandoline: oem.exe /UL1033 /V"SERIALNUMBER=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx"
i get this error:
program for advertisement "XXXXXX" failed ("xxxxxx" - "Per-system unattended"). A failure exit code of 255 was returned.
User context: NT-MYNDIGHET\SYSTEM
Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 255 is considered a failure.
Solution: For more information on the exit code, refer to the documentation for the program you are distributing. -
Installing Unity 7 with Exchange 2007
I need to install Unity 7 with Exchange 2007
The DVDs that I have received from Cisco contains Unity 2003 Message store.
How I can Install Unity 7 with Exchange 2007 and I have 2003 on Unity server.
Any body can advise me?
and is there any documnet contains the requirements for installation( what I should do on Exchange server)Here are the questions I need you to answer:
1) If you plan on integrating with Exchange 2007, my assumption is that you are planning on a Unified Messaging deployment and you will be integrating with your CORPORATE (i.e., existing) Active Directory and Exchange 2007 environment. Is that correct? If not, and you are installing a standalone Unity messaging environment then my advice is to use Exchange 2003 as this will provide better ease of use in a standalone environment for you (I'll get to this point in more detail as I answer your questions).
2) Do you need to configure OAB for Outlook 2003 and Earlier Clients even if all of your users have Outlook 2007? Yes. I believe the actual setting in E2K7 may not read exactly as it is written here but the premise is the same which is why the statement "regardless of which versions of Outlook you are using" is included in the installation notes.
3) What is the difference between Unity with Exchange 2003 vs. Exchange 2007?
- With Exchange 2007, Unity cannot create mailboxes directly in Exchange due to permission restrictions. All users and mailboxes must exist before you create a Unity subscriber. Going back to #1, if you are doing a standalone environment then Exchange 2003 integration is easier from an adminstration perspective. Unity can create AD users and mailboxes for you with Exchange 2003 but not with Exchange 2007.
- Expanding on your second question, even with Exchange 2007 the Exchange 2003 System Manager is installed on the Cisco Unity server because it includes the Microsoft messaging API (MAPI) that Unity uses to communicate with Exchange for addressing, sending, and retrieving messages. When using Exchange 2007 as the partner Exchange server for Cisco Unity, offline address books for “Outlook 2003 and earlier clients” should be configured regardless of which version of Outlook is being used or Cisco Unity will not function properly.
- If you are running a mixed environment of 2003 and 2007 Exchange servers, the Unity partner server must be an Exchange 2007 server.
- When you install Unity with Exchange 2007, you must run a script on the Exchange 2007 server during the installation. This is a Power Shell script that creates the primary system accounts (3 of them) that Unity needs to operate because again, it cannot create mailboxes in an integration with Exchange 2007.
That's all the primary points.
Hailey
Please rate helpful posts! -
AMT 3.2.10 Clients with SCCM 2012 on Windows 2012
Hey
I have a couple of HP dc7800 computers with Intel's AMT/vPro that I'd like to provision with SCCM 2012. The installed firmware version is 3.2.10 which is a supported version according to the documentation [1]. Provisioning of newer clients (5.2.x upwards)
is successful, so I can rule out all the usual suspects like the provisioning certificate from GoDaddy, our internal CA, DHCP options, etc. Provisioning with SCCM 2007 of both 3.2.x and 5.x AMT devices is also still successful.
The amtopmgr.log repeatedly shows the following entries:
Provision target is indicated with SMS resource id. (MachineId = 16777325 WS45.mydomain.ch)
Found valid basic machine property for machine id = 16777325.
Warning: Currently we don't support mutual auth. Change to TLS server auth mode.
The provision mode for device WS45.mydomain.ch is 1.
The IP addresses of the host WS45.mydomain.ch are x.x.x.x.
Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.
Attempting to establish connection with target device using SOAP.
Create provisionHelper with (Hash: 74B7792EDBD64EBB01E2E3A0B27FAFA04C2D3BCB)
Set credential on provisionHelper...
Try to use provisioning account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioning account #0.
Try to use default factory account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using default factory account.
Try to use provisioned account (random generated password) to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioned account (random generated password).
Error: Device internal error. This may be caused by: 1. blabla...
Error: Can NOT establish connection with target device. (MachineId = 16777325)
After some investigation with Wireshark, I've found out that SCCM tries connect with TLSv1 to the AMT device. The response from the device is immediately an SSL alert (internal error). Using OpenSSL, I could connect to the device if I explicitly told it
to use SSLv3. This leads me to believe that the 3.2.x firmware cannot handle TLSv1 correctly and SCCM never tries to connect with SSLv3 after a failure.
So the question is: How can I get SCCM 2012 to provision these devices?
Regards,
Ingo
[1]
http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigOOBSince no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ
Maybe you are looking for
-
Question about URL iView parameters
Hi experts. I have this issue: I have several iviews in DEV instance, URL iViews that points to backend applicationes. The URL parameters in DEV instance, point to DEV instance of backend applications. But when a will need to transport these iview to
-
SQL Loader - Load multiple files in UNIX
HI all, I'm looking for a bit of help with using SQL LOADER to load multiple files into one table. I've had a look on the forums but still struggling with this one. What I want to do is basically upload everything thats in /home/ib. I know you can us
-
How to Jump (Drill-through) between WebI query (also in Crystal Report)
Hi BO experts, I read that we can achieve drill-down in Crystal Report and WebI. But I have requirements here to jump (like RRI or Report to Report Interface) in BEx Analyzer and to pass some values (as parameter), i need to achieve: 1. jump between
-
Status for loading end date when GR
Hi! We are using shipment for imports. I have set the indicator 'Cumulate 'finish loading' status from inbound deliv. sts 'gds rcpt completed' for the shipment type. But on receipting the inbound delivery, the status is still not set in the shipment
-
Hi, All of you... I want to Know ... Why & where the Inline views are used? Regards, Ar