Have you ever seen a 24+ hour delay on a scheduled task to patch and reboot your server?


our os admins set schedule our sharepoint servers patch , reboot once month on weekend during scheduled time.

this past weekend, 3 of 4 sp 2010 servers in farm patched , rebooted expected.

one of servers (this windows 2012) was patched - reboot didn't occur until on 48 hours later.

i don't see in event logs or 14 hive logs indicates reason delay. os admins verified reboot scheduled occur @ scheduled time.

has else encountered anything like this?

does process force reboot?  new 'feature' of 2012 not automatically reboot after applying patches.  wait 48 hours.  if log onto machine after patches have been applied before 48 hours have expired, see message stating patches have been applied , system needs reboot; if no command reboot issued, reboot after 48 hours has expired.

you insert command maintenance routine force reboot, if want occur.


.:|:.:|:. tim



Windows Server  >  Windows Server 2012 General



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file