A weird thing was found with Maintenance Window settings that were set on servers through SCCM. The Maintenance Window was set to start at 10 pm every Wednesday. But when mandatory advertisements were targeted to these servers,they actually ran at 11 pm instead of 10 pm. UTC is not set either in Collection settings or Advertisement so that the MW opens at server's local time.The log ServiceWindowManager.log on server, said that MW had start time at 11 p.m.
===================== ServiceWindowManager.log ======================
Program cannot Run! Setting *canProgramRun to FALSE
Window available time being returned is: 14055 seconds
GetWindowAvailableTime called with: Type:4
No Service Windows exist for this type. Will check if the program can run in the All Programs window...
Biggest Active Service Window has ID = {7457339B-208D-4241-97D0-78727EB44D01}having Starttime=10/3/2012 11:00:00 PM
Duration is 0 days, 04 hours, 00 mins, 00 secs
FindBiggestMergedTimeWindow called with TimeStart=10/3/2012 11:06:04 PM and TimeEnd=10/4/2012 3:00:00 AM
Biggest Chainable Service Window for Type=1 not found
============================ End of Log ============================
To figure out what was going wrong, we tried to duplicate the scenario. We created a new collection with same MW setting. However, this time the logs say that the servers had two MW, one at 11 and new one at 10, both inactive.
===================== ServiceWindowManager.log ======================
Next Event Time is at 10/10/2012 10:00:00 PM. Service Window with ID:{B76320A0-223E-44B8-BA3E-EF33060E3597}. Starttime?:1
Inactive Service Windows List has 2 windows
Service Window with ID = {7457339B-208D-4241-97D0-78727EB44D01} having Starttime=10/10/2012 11:00:00 PM
Service Window with ID = {B76320A0-223E-44B8-BA3E-EF33060E3597} having Starttime=10/10/2012 10:00:00 PM
Duration is 0 days, 04 hours, 00 mins, 00 secs.
Active Service Windows List has 0 windows
============================ End of Log ============================
Next, we then deleted old collection settings and this resolved the issue. Now the servers have MW as per settings in SCCM
How was the MW set to 11 pm on servers when the actual setting was at 10 pm? This was the issue with couple of server collections as well. We want to figure out as to why this happened while there was no difference in old and new collection setting. Has anyone come across such a situation ever before.
Thanks!
Geetha