Deploy XP SP3 via GP

[OverWorked]

Quick question.

 

Is it possible to deploy XP SP3 by GP, like it was with SP2?

 

I've just the read the MS pdf "overview of Windows XP Service Pack 3". The last paragraph says:-

 

You can deploy SP3 using Microsoft Systems Management Server 2003, Microsoft System Center Configuration Manager 2007, or third-party solutions. The process has not fundamentally changed.

 

No mention of GP or WSUS. Typical Microsoftese - they'll only tell you what you can do, not mentioning anything they've stopped.

 

I don't have Systems Management Server 2003 or System Center Configuration Manager 2007.

 

My WSUS isn't working at the moment -I'm going to fix it anyway - is it possible through WSUS?

 

 

Edit:-

Although there's no extract option anymore, looking through extracted folder, shows an update.msi. I'll try that.

[cookie_monster]

It can be deployed via GP but i wouldn't recommend it, fix your WSUS and deploy it that way as you will receive a progress report, if you deploy via GP you will have to check every event log to know if it was successfull.

[OverWorked]

The GP approach didn't work. I'll give up with this.

 

Product: Windows XP Service Pack 3 (1033) -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: AdminRunSetupMin, location: ...

 

I'll fix WSUS. I gave up on WSUS a while ago when I couldn't get it to stop insisting on logging off users and rebooting after a each update, but that's the subject of another thread.

[powdarrmonkey]

I'll fix WSUS. I gave up on WSUS a while ago when I couldn't get it to stop insisting on logging off users and rebooting after a each update, but that's the subject of another thread.

 

That's down to your policy settings. Run a model and see which policy is setting them, and I'll bet there's one setting the option to install immediately if a scheduled install is missed. If you've set deadlines in WSUS that can also cause this problem because the client will try its hardest to install them on the day of the deadline.

[Michael]

You could download the full XP SP3 package and put the following code in your logon script:

 

\\servername\sharename\WindowsXP-KB936929-SP3-x86-ENU.exe /quiet /passive /forcerestart

 

Please note, this would create a lot of traffic even over 10/100 ethernet, but it would work as you'd only have to logon 10 machines at a time, then sit back and relax

[OverWorked]

The problems I had before with WSUS were with version 2.

 

I've got WSUS 3.0 SP1 working perfectly, with no annoyance to the users.

 

XP SP3 + Media Player 11 + loads of other stuff deploying happily now.

 

Thanks.

[srochford]

Much better to do things like this with WSUS but if there is something which needs deploying but is not WSUSable then you could use BITS to get the file to the machine in trickle mode (so you don't mash up your network) and then run it. Put something like this in your machine startup script:

bitsadmin /addfile XPSP3 \\server\share\xpsp3.exe c:\temp\xpsp3.exe
bitsadmin /setnotifycmdline XPSP3 c:\temp\xpsp3.exe
bitsadmin /resume

What that will do is start BITS downloading the .exe file (more or less what WSUS does). It then specifies the command to run when the download is complete and finally sets the download going. Not absolutely sure of the syntax because it's a while since I've used this but it's certainly possible to do this sort of thing.

[powdarrmonkey]

Never realised BITS had a command interface. Excellent, thanks Steve.

[OverWorked]

Never realised BITS had a command interface. Excellent, thanks Steve.

 

I didn't either. Good bit of info to keep for when one needs it.

 

BITSAdmin Tool

[powdarrmonkey]

It's already on my bookmarks