Hi, sorry if this seems an obvious question. But I can't find a straightforward answer anywhere else. I'm running SCCM SP1 (4.00.6221.1000) in mixed mode. Basically for starters, I'm wondering what version of the SCCM client my machines should be running? The latest version (4.00.6487.2000), or the version on the server that matches the server version, i.e. 4.00.6221.1000. Also, I have a small number of machines with an older version on them, 4.05931.001. I want to push out a newer version to them, and was first thinking of using a manual "Client Push Installation". But I 've also been reading about "Software Update Point Installation". What I can't see is what is the impact of ticking this option? Is it similar to other Software Updates and do I need to create package and point it at a collection? Finally, is there a recommended version of Windows Update Agent? Or should some older versions definitely be upgraded? e.g. 7.0.600.381. From reading I get them impression that the best way to upgrade it is to create a collection based on a query for older versions, and then create a Package and Ad which installs a newer version onto those machines which require it.

Hi, For SCCM, you should upgrade the site server to ConfigMgr. SP2. Once that is done, you should upgrade all clients to SP2. You can use the software distribution feature to upgrade the clients.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Thanks Kent. I'll read up on the SP2 upgrade. So you are saying that "Software Update Point Installation" uses the regular software distribution feature? There plenty of advice on how to do it, e.g. http://technet.microsoft.com/en-us/library/bb633194.aspx. But once you tick the box to enable it, what then? Also, any advice on Windows Update Agent versions, and updating them? Is the very latest always recommended?

For Software Updates (by which I mean patching), may I recommend you read through the wiki found here: http://www.myitforum.com/myitwiki/SCCMSU.ashx It's a good starting point. Windows Update Agent versions; yes, you'll want to deploy the latest version, just as a general practise. Regarding upgrading your servers (and then your clients) to SP2: there is absolutely no reason not to do so, and several reasons to go ahead. I can't think of a single reason to not update to SP2.Standardize. Simplify. Automate.

Thanks Sherry for the SCCM SP2 & Windows Update info. From reading forums, people typically deploy the WU agent as a package and advertisement? I'm currently using SCCM/SUP for Software Updates/patching, in quite a similar method to that outlined in the guide - but's its a good guide and I have flagged it for further reading. My question in this area was in relation to the "Software Update Point Client Install". I can see in plenty of documentation how this can be setup - but, I couldn't seem to find any information on how it actually works in practice. But this sentence here I found seems to give a good impression of what to expect? That the SCCM client install will be available in the SCCM console under "Software Updates", Updates Repository". "The idea behind Software update point based client installation is to publish the Sccm 2007 client as a critical update, and hence its name, is installed from the Software update point."