I need to deploy PowerShell 3.0 using sccm 2012 r2 on all Windows 7 SP1 computers in a company. I use below program:
wusa PowerShell3.msu /passive /quiet /norestart
Deployment properties is set to: do not allow for software installation and restart outside maintenance window
To have fully operational PowerShell 3.0 it need computer restart after installation. Most of our users do not log off or restart computers the whole weeks - they just lock them. It is possible that they have some documents, etc. opened and do not saved so we cannot just restart computers at night. There is no maintenance windows set up for any of our collections in SCCM. All SCCM clients have business hours setup as default from 5:00 to 22:00
I tested this deployment on some course room computers and it looks like all of them were restarted at 5:00 AM next day after scheduled deployment. I think it can be connected with GPO for Windows updates, as PowerShell 3.0 is in fact Windows Update. In GPO there is a setting
The question is what
is the best practice when deploying software which needs computer restart and how to investigate which setting caused the computers reboot at 5:00 AM