It’s happening during the day (business hours). He was sitting at the computer watching the updates download and install. Deployment does not ignore maintenance windows.
Thanks, Mike From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of DonPick Sent: Thursday, June 29, 2017 2:54 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] RE: Confusion with maintenance windows ‘but is installing during the weekday’...... Is that daytime or at night? I can see some ‘business hours’-related windows in your logfile (Type=6), so is that your trouble? And, are your deployments set to ignore maintenance windows if deadlines are set anyway? There are some right-click tools which make it easier to see the MW data. But finally, what is the end-user seeing (and when), and how does that correlate with the actual actions logfiles (did the user allow an action?)(was it a past-due scenario?) Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Mike Murray <mailto:mmur...@csuchico.edu> Sent: Friday, 30 June 2017 5:44 AM To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Confusion with maintenance windows Bump de bump bump From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray Sent: Wednesday, June 28, 2017 1:47 PM To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> Subject: [mssms] Confusion with maintenance windows CM2012 – I have a client that does not seem to be respecting its maintenance windows. I’m including as much info as I can find. It should only install updates every Saturday & Sunday between 2:50a-5:40a, but is installing during the weekday. The ConfigMgr report shows it has the right windows, but the log seems to indicate something else. Report of maintenance windows on client: ServiceWindowManager.log: Refreshing Service Windows..... ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=7cb56688-692f-4fae-b398-0e3ff4413adb, ScheduleString=02C159C0381A200002C159C0381B200002C159C0381C200002C159C0381D200002C159C0381E2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) CServiceWindow::CServiceWindow: Failed to initialize ServiceWindowSchedule instance from schedule string (02C159C0381A200002C159C0381B200002C159C0381C200002C159C0381D200002C159C0381E2000) ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) This is a one shot Service Window that has already finished. ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 00, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=90a5f436-364c-48c7-8dc7-c5014abcbea8, ScheduleString=00084AC028592000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/02/17 00:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 1, hours: 05, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID={72F43DB4-182D-4E02-AFCC-9C023A6315AD}, ScheduleString=C8541B72101F2000, Type=1 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/01/17 02:50:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 02, mins: 50, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=45dca355-3249-4845-b8aa-72d0e604548e, ScheduleString=02C24AC0381C2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 06/28/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID={7F965112-0A7D-46E3-96EA-4FF90370202C}, ScheduleString=C8541B7210192000, Type=1 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/02/17 02:50:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 02, mins: 50, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=87e4759c-2884-45e6-9261-c33ba53f596c, ScheduleString=02C24AC0381D2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 06/29/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=36da6950-3d1e-4027-be0e-7b16a4daee7e, ScheduleString=02C24AC0101E2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 06/30/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 02, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=028bfbc0-7120-4081-a268-0e664a92ac4a, ScheduleString=00074AC0005F2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/01/17 00:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 1, hours: 00, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=49fd80be-ac4b-4877-974d-ecd09958926d, ScheduleString=02C24AC0381B2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/04/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Populating instance of ServiceWindow with ID=ad27b0ca-8c74-43c7-8200-1f601880bd75, ScheduleString=02C24AC0381A2000, Type=6 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) StartTime is 07/03/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Checking to see which Service Windows should be Active..... ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Checking Service Windows to find Next Event..... ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Next Event Time is at 06/28/17 22:00:00. Service Window with ID:45dca355-3249-4845-b8aa-72d0e604548e. Is the next event the beginning of the window? Yes ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Inactive Service Windows List has 10 windows ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 7cb56688-692f-4fae-b398-0e3ff4413adb having Starttime=01/01/38 00:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 90a5f436-364c-48c7-8dc7-c5014abcbea8 having Starttime=07/02/17 00:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 1 days, 05 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = {72F43DB4-182D-4E02-AFCC-9C023A6315AD} having Starttime=07/01/17 02:50:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 02 hours, 50 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=06/28/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = {7F965112-0A7D-46E3-96EA-4FF90370202C} having Starttime=07/02/17 02:50:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 02 hours, 50 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 87e4759c-2884-45e6-9261-c33ba53f596c having Starttime=06/29/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=06/30/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 028bfbc0-7120-4081-a268-0e664a92ac4a having Starttime=07/01/17 00:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 1 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = 49fd80be-ac4b-4877-974d-ecd09958926d having Starttime=07/04/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Service Window with ID = ad27b0ca-8c74-43c7-8200-1f601880bd75 having Starttime=07/03/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Active Service Windows List has 0 windows ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Scheduling the Timer Task ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Scheduled the timer to fire on 06/28/17 22:00:00 ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) ServiceWindowManager 6/28/2017 12:41:54 PM 4172 (0x104C) Best Regards, Mike Murray Desktop Engineer/IT Consultant - IT Support Services California State University, Chico 530.898.4357 mmur...@csuchico.edu <mailto:mmur...@csuchico.edu> Remember, Chico State will NEVER ask you for your password via email! For more information about recognizing phishing scam emails go to: <http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml> http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml
smime.p7s
Description: S/MIME cryptographic signature
