I had a situation a couple days ago when a server rebooted after a SCCM client was installed, I have no problem with the client being installed, but where my issue comes in is the reboot. In our environment we take reboots very seriously and we need to know down to the minute when a reboot occurs and how to configure exactly when it happens. This catching us by surprise will cause lots of questions and meeting etc. etc. Where in SCCM can I configure the programs that are advertised to install the program or download the install files but wait for someone to reboot it. On a side note the server that rebooted was inGPO and I read on a previous question that said that GPO will trump the SCCM configuration. Please get back to me soon, thanks!!!

How was the client installed? GPO. Generally the restart is only required if a pre-req such as a BITS update was installed. Also if you right click and install it shouldn't force the restart automatically. It should wait for the user to restart the machine. If you use the /forcerestart then it will restart as soon as the client installs. I have never had a client restart just by installing the client unless there was a reboot switch.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

The client was discovered about a week agothrough AD discovery and the clients installed on all of our other clients automatically and no reboots happened. I am not sure exactly where the /forcestart is.

Also where is the "reboot switch"

/forcerestart : http://technet.microsoft.com/en-us/library/bb680980.aspxit's one of the possible command line switches that could potentially be used when installing the configmgr client, but it is certainly not necessary. As a generalization, most ConfigMgr Admins are told to minimize the # of reboots they invoke. As to why it happened, again, per Matthew's reply above, the trigger was likely because one of the pre-requisites to successful Configuration Manager Client installation was not met. Base on previous "unexpected reboot during client install", I believe every other time has been the BITS pre-req which triggered an unexpected reboot. BITS 2.5 or higher is needed.For reference, here's an old thread about this issue; back when ConfigMgr 2007 was first available, and Carol Bailey replied (one of the Docs team, so she would know): http://social.technet.microsoft.com/Forums/en-US/configmgribcm/thread/a2de5a7e-6267-4d1e-a169-7fd4f6a64ad3Standardize. Simplify. Automate.

Re-reading the question again, I just want to clarify something.It's pretty much only the BITS pre-requisite triggering an unexpected reboot that we (as ConfigMgr admins) can't work around or control.If your question was broader, i.e., now that the ConfigMgr client is installed, can you control when and how reboots occur, then the answer to that is yes. The only situations where we couldn't control the reboot would be vendor-invoked. I.e., a particular vendor-provided piece of software that you have to deploy, requires a reboot, and the vendor provides no way to circumvent it. But we can still work around that by leveraging multiple methods: carefully timing the advertisement start and expiration, or setting up Maintenance Windows for your servers are a couple methods that come immediately to mind, although there are likely a few more methods.Standardize. Simplify. Automate.