SCCM 2012 SP1 Maintenance -- Random Environments Rebooting Early

Question

Background on my deployment process for SCCM 2012 SP1:  I run a Powershell script that sends out a package and configures settings exactly the same for the particular environment set. 
The deployment script will call one or several environments at a time, as applicable. 
It will take each environment, affix the settings, push the package to be deployed (based on OS) during the specified maintenance window, and repeat. It is a very consistent process.
Last week, I deployed to A-CLOUD (name changed for simplicity purposes), among others. 
A-CLOUD went through the same process as the others in the script (see end of paragraph), in which the appropriate settings were checked. 
The environment was supposed to update and reboot on Saturday, July 12. 
However, A-CLOUD (only) updated and bounced as soon as I sent out the package on Wednesday, July 9. 
Also in the same deployment script was B-CLOUD, C-CLOUD, D-CLOUD, and E-CLOUD, which all updated and rebooted as planned on July 12.
I received an alert that A-CLOUD was rebooted by Configuration Manager.  I checked the reboot logs in Task Scheduler to compare A-CLOUD with C-CLOUD days later to compare a faulty reboot with one that ran correctly
(both of these environments are on the same site).  There was no difference in the log files. 
This issue occurs at least one a month and I have only noticed ONE pattern, Server 2008R2 -- however, it is not always the same environment that will reboot early each month, same week, same day, etc.  It seems to be
random.
Any ideas?

Answer 1

This is way too generic to be answered. What ConfigMgr object type are you deploying (package? application?)? How is the reboot initiated? How are the deployment settings etc.?
Torsten Meringer | http://www.mssccmfaq.de