Wednesday, May 14, 2008 9:08 AM
Is there any kind of best practice at the moment for deploying XP SP3 with SCCM?
I've noticed that it's available to me via the SUP, but at the same time there is nothing stopping me from downloaded SP3 and creating a package/distribution.
What would be the benefits of using SUP over normal package/distribution?
Wednesday, May 14, 2008 12:41 PM
I would use the SUP just because it's easier but I suppose it's a matter of personal preference.
As far as I know Microsoft has not officially said that the ConfigMgr client is supported on SP3 so you may not want to jump in there yet.
Wednesday, May 14, 2008 1:11 PM
Thanks for getting back to me.
Do any employees of microsoft care to comment?
Wednesday, May 14, 2008 11:25 PMOwner
We did announce earlier today that we are now officially supporting Windows XP SP3 as a client operating system for Configuration Manager 2007 RTM. We'll have updated Supported Configurations docs on the web soon (don't ask when, I was told 'soon').
As to how to deploy it, your choice - software distribution or software updates. Personally, something that is easy to package, I'd do with software distribution, as I can make it silent, and run at a specific time. But the software update route should be fine as well, that's what it is there for :-)
Thursday, May 15, 2008 7:50 AM
Thanks for your comments wally.
I guess that software distribution does have advantages over using software updates to deploy SP3, notably the ability to make use of command line switches of the setup.