Hi I am looking into setting up Software Update Point Based Installation. We already have clients out on 1300 servers and 1400 workstations. But to ensure that all machines get the client Software Update Point Based Installation is looking like a good solution. I however do have some questions: 1. If I enable Software Update Point Based Installation what will happen to the machines that already have the client? Will it re install? Will it detect that the machine already has the client installed? 2. Will the client installation force a reboot? It does not do this when you push install it, but I want to be sure. 3. Are there any other dangers with doing this? I do not want to enable this and suddenly have to reboot 2700 machines... Any and all advice would me much appreciated. Thanks :)

1. This will install the ConfigMgr 2007 client on computers that do not already have the client installed, or upgrade existing ConfigMgr 2007 clients. In addition, if a client is uninstalled for any reason, the client will be reinstalled at the next Windows Update Agent scan. 2. Windows XP with NO BITS 2.5, it will be installed automatically during the ConfigMgr setup routine. This may triger the reboot of the clients automatically, then start the ConfigMgr installation. 3. Look at 2# More details - http://dynamicit.wordpress.com/2008/10/29/configmgr-2007-client-deployment-software-update-point-based-installation/Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Thank you for the reply. Two more question; is there any way to limit the upgrade and installation of the client to happen in designated maintenance windows? And is there any way to limit this to certain collections?

I don't think those scenarios are possible.Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

If you are using WSUS to deploy the agent, then there is no such thing as collections. You could use multiple GPOs on various OUs to control deployment and your collections in ConfigMgr could in turn be based on these OUs but not vice-versa. Using these same GPOs, there are many different settings to control how clients pull updates (including the ConfigMgr Agent) from WSUS: http://technet.microsoft.com/en-us/library/cc720539(WS.10).aspx (there are actually more options than this link has as it is an older page specific to WSUS 2.0 with Windows 2000 info but it is still valid). Using these settings you could influence rollout greatly, but there are no specific maintenance window like settings.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys