Jump to content

pacardon

Member
  • Posts

    11
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About pacardon

pacardon's Achievements

0

Reputation

  1. Got some Microsoft support on this issue. The solution is exactly as I thought it was: 1. Install Server 2008 2. Capture to a WDS server running the latest WDS/WAIK 3. Use DISM on the image. But this ruins the point, I want to use original WIM image for software source integrity. Also makes the results much harder to reproduce.
  2. Yikes. Reminds me of Linux where cd Home and cd home are two different directories. I'll give it a try and report my results. Thanks leen2! Interesting results: 1. I can't seem to point DISM to a directory of cabs or msu files 2. DISM refuses to accept an MSU file as a package using the /PackagePath command. 3. I specifically have to tell it the cab to install. with /Add-Package /PackagePath:"C:\path\update.cab" On the bright side, at least it isn't imagex and pkgmgr... I was trying that as well and I do not like it at all. So I guess I have my answer. Just needed a nudge in the right direction. Thank you all! And giving back to the community... scripts I came up with: for /f "tokens=*" %%a in ('dir /b *.msu') do expand %%a -F:* C:\<TEMP CAB FILE FOLDER> imagex.exe /mountrw <WIM FILE> <INDEX> c:\<MOUNT FOLDER> cd /<TEMP CAB FILE FOLDER> for /f "tokens=*" %%b in ('dir /b *.xml') do start /w pkgmgr /n:"C:\cabs\%%b" /o:"C:\<MOUNT FOLDER>;c:\<MOUNT FOLDER>\windows" /l:c:\temp\insert.log (insert error checking) imagex /unmount /commit c:\<MOUNT FOLDER> Same thing with DISM: for /f "tokens=*" %%a in ('dir /b *.msu') do expand %%a -F:* C:\<TEMP CAB FILE FOLDER> dism /Mount-WIM /WimFile:<WIM FILE> <INDEX> /MountDir:C:\<MOUNT FOLDER> for /f "tokens=*" %%b in ('dir /b C:\<TEMP CAB FILE FOLDER>\*.cab') do dism /Image:c:\<MOUNT FOLDER> /Add-Package /PackagePath:C:\<TEMP CAB FILE FOLDER>\%%b (add error checking) dism /Unmount-WIM /MountDir:C:\<MOUNT FOLDER> /commit (Specifically for Vista/Server 2008 SP2 WIMs)
  3. That was the first thing I thought and that as well right after I posted: dism /Image:c:\WIM /Add-Package /PackagePath:C:\updates\Windows6.0-KB2588516-x86.msu Output: Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Error: 87 An error occurred while processing the command. For more information, review the log files. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Log scrapings from my 2008 server using dism from waik, got the same error there: 2012-03-30 10:01:44, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2012-03-30 10:01:44, Info DISM DISM.EXE: 2012-03-30 10:01:44, Info DISM DISM.EXE: Host machine information: OS Version=6.0.6002, Running architecture=x86, Number of processors=2 2012-03-30 10:01:44, Info DISM DISM.EXE: Executing command line: dism /Image:c:\tempcd /Add-Package /PackagePath:C:\update\Windows6.0-KB2588516-x86.msu 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 10:01:44, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2012-03-30 10:01:44, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2012-03-30 10:01:44, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2012-03-30 10:01:44, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2012-03-30 10:01:44, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2012-03-30 10:01:44, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager 2012-03-30 10:01:44, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager. 2012-03-30 10:01:44, Info DISM DISM Provider Store: PID=16468 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2012-03-30 10:01:45, Info CSI 00000001 Shim considered [l:266{133}]"\??\c:\tempcd\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2012-03-30 10:01:45, Info CSI 00000002 Shim considered [l:260{130}]"\??\c:\tempcd\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe" : got STATUS_SUCCESS 2012-03-30 10:01:45, Info DISM DISM.EXE: The target image version is: 6.0.6002.18005. 2012-03-30 10:01:45, Info DISM DISM.EXE: The target image is downlevel and considered supported. Looking for PkgMgr.exe. 2012-03-30 10:01:45, Info DISM DISM.EXE: Executing DISM against a downlevel image. Calling c:\tempcd\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe 2012-03-30 10:01:45, Info DISM DISM Provider Store: PID=16468 Getting Provider Compatibility Manager - CDISMProviderStore::GetProvider 2012-03-30 10:01:45, Info DISM DISM Provider Store: PID=16468 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2012-03-30 10:01:45, Info DISM Compatibility Manager: PID=16468 Processing the top level command token(add-package). - CCbsCliParser::Private_ValidateCmdLine 2012-03-30 10:01:45, Info DISM Compatibility Manager: PID=16468 PackageManager command is being executed: c:\tempcd\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe /l:"C:\Windows\Logs\DISM\dism.log.pkgmgr" /o:"c:\tempcd;c:\tempcd\Windows" /ip /m:"C:\update\Windows6.0-KB2588516-x86.msu" /s:"C:\Users\ADMINI~1\AppData\Local\Temp\FFA19293-66D8-4AAB-9339-A21C9C17479A" - CCompatManager::InternalExecuteCommand 2012-03-30 10:01:50, Info DISM Compatibility Manager: PID=16468 PackageManager return code = 0x57 - CCompatManager::InternalExecuteCommand 2012-03-30 10:01:50, Error DISM Compatibility Manager: PID=16468 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:970 - CCompatManager::ProcessPackageList(hr:0x80070057) 2012-03-30 10:01:50, Error DISM Compatibility Manager: PID=16468 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:589 - CCompatManager::CompatExecuteCmdLine(hr:0x80070057) 2012-03-30 10:01:50, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2012-03-30 10:01:50, Info DISM DISM.EXE: 2012-03-30 10:01:50, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2012-03-30 10:01:50, Info DISM DISM.EXE: 2012-03-30 10:01:50, Info DISM DISM Image Session: PID=16468 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect 2012-03-30 10:01:50, Info DISM DISM Provider Store: PID=16468 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 10:01:50, Info DISM DISM Provider Store: PID=16468 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 10:01:50, Info DISM DISM Provider Store: PID=16468 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2012-03-30 10:01:50, Info DISM DISM Provider Store: PID=16468 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 10:01:50, Info DISM DISM Provider Store: PID=16468 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
  4. Having quite the issue with applying updates to a Server 2008 WIM file. I've copied my Server 2008 install disk to a Windows 7 Machine, I've also installed WAIK on this computer. First I mounted my wim: dism /Mount-Wim /WimFile:C:\2008\Sources\install.wim /name:"Windows Longhorn SERVERSTANDARD" /MountDir:C:\WIM then I tried to apply my folder of updates: dism /Image:c:\wim /Add-Package /PackagePath:C:\updates Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Error: 2 An error occurred while processing the command. For more information, review the log files. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Output from the log file: 2012-03-30 07:57:23, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2012-03-30 07:57:23, Info DISM DISM.EXE: 2012-03-30 07:57:23, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=x86, Number of processors=2 2012-03-30 07:57:23, Info DISM DISM.EXE: Executing command line: dism /Image:c:\wim /Add-Package /PackagePath:C:\updates 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2012-03-30 07:57:23, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2012-03-30 07:57:23, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2012-03-30 07:57:23, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2012-03-30 07:57:23, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2012-03-30 07:57:23, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2012-03-30 07:57:23, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager 2012-03-30 07:57:23, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager. 2012-03-30 07:57:23, Info DISM DISM Provider Store: PID=3500 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2012-03-30 07:57:24, Info CSI 00000001 Shim considered [l:260{130}]"\??\c:\wim\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2012-03-30 07:57:24, Info CSI 00000002 Shim considered [l:254{127}]"\??\c:\wim\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe" : got STATUS_SUCCESS 2012-03-30 07:57:24, Info DISM DISM.EXE: The target image version is: 6.0.6002.18005. 2012-03-30 07:57:24, Info DISM DISM.EXE: The target image is downlevel and considered supported. Looking for PkgMgr.exe. 2012-03-30 07:57:24, Info DISM DISM.EXE: Executing DISM against a downlevel image. Calling c:\wim\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe 2012-03-30 07:57:24, Info DISM DISM Provider Store: PID=3500 Getting Provider Compatibility Manager - CDISMProviderStore::GetProvider 2012-03-30 07:57:24, Info DISM DISM Provider Store: PID=3500 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2012-03-30 07:57:24, Info DISM Compatibility Manager: PID=3500 Processing the top level command token(add-package). - CCbsCliParser::Private_ValidateCmdLine 2012-03-30 07:57:24, Info DISM Compatibility Manager: PID=3500 PackageManager command is being executed: c:\wim\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe /l:"C:\Windows\Logs\DISM\dism.log.pkgmgr" /o:"c:\wim;c:\wim\Windows" /ip /m:"C:\updates" /s:"C:\Users\ADMINI~1\AppData\Local\Temp\0618634A-3828-480D-9D3D-222AECC0FE44" - CCompatManager::InternalExecuteCommand 2012-03-30 07:57:34, Info DISM Compatibility Manager: PID=3500 PackageManager return code = 0x2 - CCompatManager::InternalExecuteCommand 2012-03-30 07:57:34, Error DISM Compatibility Manager: PID=3500 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:970 - CCompatManager::ProcessPackageList(hr:0x80070002) 2012-03-30 07:57:34, Error DISM Compatibility Manager: PID=3500 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:589 - CCompatManager::CompatExecuteCmdLine(hr:0x80070002) 2012-03-30 07:57:34, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2012-03-30 07:57:34, Info DISM DISM.EXE: 2012-03-30 07:57:34, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2012-03-30 07:57:34, Info DISM DISM.EXE: 2012-03-30 07:57:34, Info DISM DISM Image Session: PID=3500 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect 2012-03-30 07:57:34, Info DISM DISM Provider Store: PID=3500 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 07:57:34, Info DISM DISM Provider Store: PID=3500 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 07:57:34, Info DISM DISM Provider Store: PID=3500 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2012-03-30 07:57:34, Info DISM DISM Provider Store: PID=3500 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider 2012-03-30 07:57:34, Info DISM DISM Provider Store: PID=3500 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider I'm not sure why its failing, I get error code 2, but I'm not sure why. I've scoured this forum and google with no helpful results. What am I doing wrong?
  5. Ok... I read I don't know how many guides on integrating hotfixes into a Office 2003 install. You use the following command: msiexec /p <path\msp> /a <path>\pro11.msi SHORTFILENAMES=TRUE /qb Correct? I have tried I don't know how many times... but the hotfixes I integrated still appear in MBSA and Microsoft Updates as not installed after using the Admin install. Are they applied but just don't have the proper registry entries? Is there anway to run them afterward instead of integrating using a transform?
  6. Did you put the key in during your admin install? Check here for Unattended office instructions.
  7. Thanks for the tip... updating the guide. The <Path_to_patch> isn't really needed as I recommend you always execute the MSP from its folder. It is not required, but it is always easier, that way you only need to know where it is going, and not comming from because you are already there. So if the msp is in c:\acrobat\patches your command prompt will look like this when your run the command: c:\acrobat\patches> There are other guides on the Adobe Registration Stuff, you just pull .dat out of some folder and copy it back I believe. Don't know for sure.
  8. Doh! Didn't even try Winrar! I'll modify the guide!
  9. I've been through several Adobe Acrobat 7.0 Pro guides... but they never feel complete. XXSplit's Guide was close, but a little confusing. So I used his guide, a little bit of thinking to come up with this one. Which is exactly what I was looking for. Step One: From your Adobe Acrobat CD run the following command: x:\setup.exe /a Place the admin update somewhere on your harddrive. "C:\Acrobat 7" for example Step two: Download the latest updates 7.0.7 and 7.0.8 Create a folder on root c:\, call it "Acrobat Update" Extract all the MSP files from the updates to this folder using winrar. You should have three MSP files: Ac705PrP_efgj.msp Acro707.msp Acro708.msp Open a command prompt and browse to "C:\Acrobat Update" Run the following commands: msiexec /p Ac705PrP_efgj.msp /a "C:\Acrobat 7\AcroPro.msi" /qb! msiexec /p Acro707.msp /a "C:\Acrobat 7\AcroPro.msi" /qb! msiexec /p Acro708.msp /a "C:\Acrobat 7\AcroPro.msi" /qb! Now for you unattended install you need to go download Installshield Tuner and install it. When you run it, browse the the .itw on your Acrobat 7 CD, choose create new transform. The MSI file should be C:\Acrobat 7\AcroPro.msi Go through and customize, add your CD key under Install Options, and under Preferences > Eula and Online Features tab, there is a checkbox to skip the EULA. Your install command should look like this: AcroPro.msi TRANSFORMS=AcroPro.mst /qb /norestart If you don't want the progress bar and have it completely invisible: AcroPro.msi TRANSFORMS=AcroPro.mst /qn /norestart From here you can dump it onto your Custom XP DVD, stick it on network, burn a new disk, or make a 7zip installer to save space. And remember, as Adobe releases updates, just extract the MSP and run this command to keep your install updated: msiexec /p Acro7XX.msp /a "C:\Acrobat 7\AcroPro.msi" /qb! ENJOY!
  10. Do you build the msi or do you just take all the files from the /sav folder on the CD?
  11. I made a slipstream SP2 disk from a Windows XP Sp1a Corporate volume license disk using nLite. I also integated RyanVM's Hotfix Pack using nLite, the Direct Integration (no running hotfixes it's directly intigrated into the I386). I also tried to integrate Symantech Antivirus 9 into the install. For some reason, the $OEM$\$1 does not seem to be copying to the system drive. Anyone else having a similar problem?
×
×
  • Create New...