sounddoc
Posts: 41
Score: 0 Joined: 11/15/2007 Status: offline
|
There's no GPO in place to reboot at 3am, as stated earlier I now have one to suppress reboots through AU. So there's still one more piece of the puzzle that I am confused by. As jsandys above has noted, the local policy, or more accurately the local user setup of windows updates doesn't seem to be controlled by SCCM anywhere. For example, you set up AU through GP, or locally to install updates at 3am daily, etc...this is all good, but wouldn't it override any SCCM deadline / installation settings, and therefore supressed reboot settings? I believe this is what my issue was - AU was set up by the user on the machine to install at 3am daily, and reboots were not suppressed through GP. The scan cycle picked up updates from SCCM, directed them to AU which said, ok, I'll install these at 3am as my local policy says to, it did, and then rebooted because there is no part of the /local/ policy that says not to reboot, or to suppress notifications - hence the two showing up in the log i posted. Here's my delimna then: a brand new imaged machine is pestering for AU to be set up. SCCM agent is installed and has updates targeted towards it. There're no policies local, or Group assigned to the machine for AU, outside of the client agent policies...doesn't this mean the AU wizard setup exclamation point would be present indefinitely until it is either configured by the user or by GP? thanks again for all the input as well!
_____________________________
-P
|