Software Deployment

Download the original Compatibility pack and the SP2 patch. Unfortunately MS does not allow you to create an Admin install point and patch it with the SP2 patch. The SP 2 patch will have to be applied after install. Lame[:'(]

I just downloaded it from here.

When I ran this command:
compatibilitypacksp2-kb953331-fullfile-en-us.exe /extract:"C:\extracttemp"

I got the MSP file called "O12Convsp2-en-us.msp" and the eula.txt. Did you get that also?

Hi Guys, thanks for the replies.

You're absolutely right elgwhoppo - I hadn't tried running it from CLI ... my bad [:)]
I had just tried extracting with WinZip ... lazy me !!

However, there still isn't really any way to apply it via GPO is there ? We don't have SCCM or any other app deployment solution ... just GPO's

I guess maybe my easiest option is to use download from Microsoft Catalog into WSUS ? Will that be an update to the existing verion or a completely new install though ? I guess it would be an update seing that there's only an MSP in there ?

However, there still isn't really any way to apply it via GPO is there Patching clients directly is too much like hard work.

Take a copy of the current AIP, patch that, then create your new GPO.

Unfortunately MS does not allow you to create an Admin install point and patch it with the SP2 patch. The SP 2 patch will have to be applied after install
I understood from the above that this wasn't possible ? I've also tried this myself and it just doesn't do anything after launching the initial window

I do agree that patching is too much work, but looks like WSUS is my best option. Has anybody tried using any MSI authoring programs to push this update ?

Yeah, those that aren't stuck with GPO:
msiexec /i O12Conv.msi PATCH=O12Convsp2-en-us.msp /qn REBOOT=ReallySuppress

I can't believe companies are still using GPO...

968 objects AND counting...they install per-user, too. LOL

TBF, we do have some stuff in SCCM but per-user installs, particularly those with dependencies, have been a challenge.

I can't believe companies are still using GPO...
Yea unfortunately so. But to be fair, for some small companies I guess the budget just isn't there

That said - we have over 500 users and 20 servers. The problem is that there's a freeze on major IT changes this year until we upgrade to 2008 next year

As for why we're taking so long to upgrade to 2008 ... don't ask [:D]

Ouch. SCCM is so cheap, I don't get it.. but we're just consultants... no one listens to us. [:)]

SCCM is so cheapTBF once again, at the time the decision was made to go with GP, the company was very small and SMS (as it then was) was VERY expensive, especially when provided through a third-party FM crowd, whose idea of service is to first add a minimum 30% to the actual cost. Since then, that company was swallowed up by my current client, the third-party kicked out and the IT operation handed to the minnow company.

I had to include a path for the patch file:

msiexec /i O12Conv.msi PATCH="%CD%\O12Convsp2-en-us.msp" /qn REBOOT=ReallySuppress

David

So is there not a way to combine the msp from the SP2 compatibility pack to the msi file for the compatibility pack to form a new msi that includes both?

That's what I am working on accomplishing and can't seem to work the two together.

For people using SCCm to deploy the compatibility pack with SP2, what command line do you use?
I used msiexec /i O12Conv.msi PATCH=O12Convsp2-en-us.msp /qn REBOOT=ReallySuppress, but it errors out with code 1635, which basically means it couldnt open the patch package. I extracted the exe file of SP2 into the same folder as the compatibility pack, so the msi and msp files are situated in the same place in my sccm package.
Funny thing is if I run the command msiexec /i O12Conv.msi /qn REBOOT=ReallySuppress, without the Service pack, it runs fine.

Anyone else facing this issue?

As ever, you should be using a patched Administrative Installation Point, not patching clients. If persisting with the client route, you will need to install first using '/i' etc. then apply the patch, using '/P'. You can't install and patch at the same time, which is what your command line is attempting.