Jump to content

Recommended Posts

Posted (edited)

Has anyone managed to patch the Office Compatibility Pack with SP1, the install is 26Meg which is only 2Mb less than the full package. I'd like to patch the .msi so i can deploy it via group policy, i have extracted the O12Convsp1-en-us.msp file but can't get it to apply.

 

This is the command i'm using

 

msiexec /a e:\temp\sp1\o12conv.msi /p e:\temp\sp1\o12convsp1-en-us.msp

 

Any ideas?

 

Thanks.

Edited by cookie_monster
Posted
I just push the original version on. Windows Update/WSUS (assuming you enabled Office2k7 updates) patches it up straight away.
Posted
Has anyone managed to patch the Office Compatibility Pack with SP1, the install is 26Meg which is only 2Mb less than the full package. I'd like to patch the .msi so i can deploy it via group policy, i have extracted the O12Convsp1-en-us.msp file but can't get it to apply.

 

This is the command i'm using

 

msiexec /a e:\temp\sp1\o12conv.msi /p e:\temp\sp1\o12convsp1-en-us.msp

 

Any ideas?

 

Thanks.

 

Office 2007 doesn't work like that. When you do the initial install to a server you'll see a folder called "upates" is created. When you get any MSP files, you just stick them in there - new installs will then add those patch files at install time.

Posted (edited)

@ m2d2, i've created an admin install already (well AFAIK)

 

@ ZeroHour, i didn't think you could deploy .msp files using group policy can you explain how this is done?

 

@ Geoff, i have the update on WSUS but it's another big update for the slow computers to grind over every time we reinstall the OS.

 

@, srochford, i know about that for the full Office 2007 suite but is it the same for the convertors? I can't see an updates folder in the admin install point.

 

Cheers.

Edited by cookie_monster
Posted

Basically goto the gp where you deploy the MSI and then right click->properties.

Then goto the upgrades tab and then add the MSP there. MSP's transform the MSI at install time and the logic in the MSP replace some of the logic in the MSI.

If it was a MST then thats a transform but I think you just typo'ed there. Transforms can only be added when you are adding the MSI to the policy under the "modifications" tab.

Posted (edited)

Maybe i'm going mad but i can't see how to add the .msp if i right click the Compatibility Pack in the deployment list and select the upgrades tab it adds it in the 'package to upgrade' panel but i can't see where i can select the .msp file.

 

I use .mst files all the time so i know how they work, i am familiar with what .msp's do but as i say i didn't think you could deploy them.

Edited by cookie_monster
Posted
Anyone know what's new? I found that with the non-SP version the students can only open one Office 2007 document at a time. If they try to open a second it spits out a strange error. Same on my admin account. :confused:
Posted

Sorry your right cookie, dont know what I was thinking about lol.

What errors are you getting with the msp slipstream attempt?

 

We use WinINSTALL to deploy here so I can just add a msp to the package and it gets updated but thats of little use to you.

Posted (edited)

If only i was getting an error when i run the command a box pops up and it's runs an install and looks like it worked, the event log shows this "Product: Compatibility Pack for the 2007 Office system - Update 'Microsoft Office Compatibility Pack Service Pack 1 (SP1)' installed successfully" but the package isn't updated as far as i can tell.

 

In the log the Expected product versions don't look right i might see if there is a newer version.

 

 

MSI (c) (9C:BC) [10:24:43:334]: Final Patch Application Order:
MSI (c) (9C:BC) [10:24:43:334]: {026C2636-B788-409C-B178-A7603289EC2A} - d:\sp1\o12convsp1-en-us.msp
DEBUG: Error 2749:  Transform 9000200409000012.0.4518.1014 invalid for package C:\DOCUME~1\BCSINS~1\LOCALS~1\Temp\1ea556.msi. Expected product version == 12.0.4518.1014, found product version 12.0.6021.5000.
1: 2749 2: 9000200409000012.0.4518.1014 3: C:\DOCUME~1\BCSINS~1\LOCALS~1\Temp\1ea556.msi 4: 12.0.4518.1014 5: 12.0.6021.5000 
=== Logging started: 04/03/2008  10:24:43 ===
Action 10:24:43: ADMIN. 
Action start 10:24:43: ADMIN.
MSI (s) (E8:24) [10:24:44:100]: Final Patch Application Order:
MSI (s) (E8:24) [10:24:44:100]: {026C2636-B788-409C-B178-A7603289EC2A} - d:\sp1\o12convsp1-en-us.msp
DEBUG: Error 2749:  Transform 9000200409000012.0.4518.1014 invalid for package C:\WINDOWS\Installer\1de96a.msi. Expected product version == 12.0.4518.1014, found product version 12.0.6021.5000.
1: 2749 2: 9000200409000012.0.4518.1014 3: C:\WINDOWS\Installer\1de96a.msi 4: 12.0.4518.1014 5: 12.0.6021.5000 
=== Logging started: 04/03/2008  10:24:44 ===
Action start 10:24:44: ADMIN.
Action ended 10:24:44: ADMIN. Return value 1.
Action ended 10:24:44: ADMIN. Return value 1.
=== Logging stopped: 04/03/2008  10:24:44 ===
MSI (c) (9C:BC) [10:24:44:178]: Product: Compatibility Pack for the 2007 Office system - Update 'Microsoft Office Compatibility Pack Service Pack 1 (SP1)' installed successfully.

MSI (c) (9C:BC) [10:24:44:178]: Product: Compatibility Pack for the 2007 Office system -- Installation completed successfully.

Edited by cookie_monster
Posted

Not working for me either and I have the same version problems as you.

I think your right about pre sp1 versions being updated.

I may remove the version check but I will take a look at a updated build.

  • Thanks 1
Posted (edited)

This is interesting if it's the case then this could solve the issue.

 

I just want to post quick question to make sure I understand this correctly.

 

Installing 3.5, would give me both 2.0 SP1 and 3.0 SP1, which are full updates of 2.0 and 3.0 respectively, is that correct?

 

Glenn, yes, you are right. It works whether you have nothing, 2.0, or 3.0 installed. 1.0 and 1.1 are still separate. 2.0 through 3.5 all run on the 2.0 CLR, though 3.5 has its own set of tools while 3.0 is just extra assemblies.

 

Found it here

 

http://blogs.msdn.com/heaths/archive/2007/11/26/microsoft-net-framework-2-0-service-pack-1-and-how-to-detect-it.aspx

 

----------------------------------------------------------------------

 

Only just realised that i posted this in the wrong thread :-) anyway i'm having a similar issue with .NET 2.0 SP1 i suppose i'll be punting that out from the WSUS as well.

Edited by cookie_monster
  • 11 months later...
Posted

Has anyone managed to do this yet... I've been following this guide Microsoft KB952273 but when i run the final command I get the following message.. " The installation package could not be opened. Verify the package exists. blah blah blah.

 

I have tried this on a couple of machines, so surely i'm not that much of a numpty... Also what do i do if/when it completes?

 

Michael

Posted

Realistically using WSUS or a script is the way forward. Below is the code I use for the Logistix Office 2007 Compatibility Plus Pack. You could run this from a deployment share. It installs fairly quickly even on lower spec machines.

 

@echo off
setlocal
set PATHTOFIXES=C:\logistixonline.com\CompatibilityPlus
TITLE Installing Office 2007 Compatibility Pack 
echo.
echo Installing Office 2007 Compatibility Pack...
%PATHTOFIXES%\FileFormatConverters.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 
echo.
echo Installing Office 2007 Compatibility Pack SP1...
%PATHTOFIXES%\compatibilitypacksp1-kb940289-fullfile-en-us.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB951808
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB951808...
%PATHTOFIXES%\office2007-kb951808-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB954038
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB954038...
%PATHTOFIXES%\office2007-kb954038-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB951596
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB951596...
%PATHTOFIXES%\office2007-kb951596-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB951944
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB951944...
%PATHTOFIXES%\office2007-kb951944-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB954326
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB954326...
%PATHTOFIXES%\office2007-kb954326-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB955936
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB955936...
%PATHTOFIXES%\office2007-kb955936-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB951550
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB951550...
%PATHTOFIXES%\office2007-kb951550-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB958439
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB958439...
%PATHTOFIXES%\office2007-kb958439-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Office 2007 Compatibility Pack SP1 Hotfix KB956828
echo.
echo Installing Office 2007 Compatibility Pack SP1 Hotfix KB956828...
%PATHTOFIXES%\office2007-kb956828-fullfile-x86-glb.exe /quiet /passive /norestart
echo.
TITLE Installing Microsoft Works 6 - 9 Converter
echo.
echo Installing Microsoft Works 6 - 9 Converter...
%PATHTOFIXES%\Works632_en-US.msi /quiet /passive /norestart
echo.
PAUSE
EXIT

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...