I was just troubleshooting maintenance window issues on a few hyper-v host the other day and the only thing that I could find related to the types was this:
https://msdn.microsoft.com/en-us/library/jj155420.aspx Value Service Window Type Description 1 ALLPROGRAM_SERVICEWINDOW All Programs Service Window 2 PROGRAM_SERVICEWINDOW Program Service Window 3 REBOOTREQUIRED_SERVICEWINDOW Reboot Required Service Window 4 SOFTWAREUPDATE_SERVICEWINDOW Software Update Service Window 5 OSD_SERVICEWINDOW OSD Service Window 6 USER_DEFINED_SERVICE_WINDOW Corresponds to non-working hours. I was primarily polling through WMI on the machine looking for where the Maintenance Windows settings were stored that the client references which is what led me to the MSDN documentation. Type=1 defined maintenance windows while Type=6 defined non-business for the SCCM client. PS C:\WINDOWS\system32> Get-SCCMMaintenaceWindows -Computer '$computer' | FT ID,Type,StartTime,EndTime,Duration -AutoSize ID Type StartTime EndTime Duration -- ---- --------- ------- -------- 7cb56688-692f-4fae-b398-0e3ff4413adb 6 20380101000000.000000+000 20380101000000.000000+000 0 90a5f436-364c-48c7-8dc7-c5014abcbea8 6 20150329000000.000000+000 20150330050000.000000+000 104400 87e4759c-2884-45e6-9261-c33ba53f596c 6 20150326220000.000000+000 20150327050000.000000+000 25200 36da6950-3d1e-4027-be0e-7b16a4daee7e 6 20150327220000.000000+000 20150328000000.000000+000 7200 028bfbc0-7120-4081-a268-0e664a92ac4a 6 20150328000000.000000+000 20150329000000.000000+000 86400 ad27b0ca-8c74-43c7-8200-1f601880bd75 6 20150330220000.000000+000 20150331050000.000000+000 25200 {051D4EE8-BCA3-4CE0-B591-7069361B9E31} 1 20380101000000.000000+000 20380101000000.000000+000 0 49fd80be-ac4b-4877-974d-ecd09958926d 6 20150331220000.000000+000 20150401050000.000000+000 25200 45dca355-3249-4845-b8aa-72d0e604548e 6 20150401220000.000000+000 20150402050000.000000+000 25200 Note: [Get-SCCMMaintenanceWindows] is a custom PS cmdlet that in a module that I wrote. It's pulling information from [wmi]root\ccm\clientSDK:CCM_ServiceWindow From: [email protected] [mailto:[email protected]] On Behalf Of Joseph Rose Sent: Thursday, March 26, 2015 10:35 AM To: [email protected] Subject: [mssms] Service windows Looking to see if anyone has any information about service window types and what a type=6 is? Getting unusual behavior patching Embedded devices. I am using fwbf and using the commit check box in the patch deployment. The patches are required and the time has passed making them mandatory. But for some reason a day or two later the devices will decide to install. The first round of patches are about 53 patches. I setup a maintenance window of 24 hours daily. I have tried all different settings including no maintenance window. I looked through the Microsoft Software Updates Management document and have not found any reference to the different types based on the number. I understand the differences between maintenance hours and business hours. Checking to see which Service Windows should be Active..... ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Checking Service Windows to find Next Event..... ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Next Event Time is at 03/26/15 22:00:00. Service Window with ID:87e4759c-2884-45e6-9261-c33ba53f596c. Is the next event the beginning of the window? Yes ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Inactive Service Windows List has 9 windows ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 7cb56688-692f-4fae-b398-0e3ff4413adb having Starttime=01/01/38 00:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 90a5f436-364c-48c7-8dc7-c5014abcbea8 having Starttime=03/29/15 00:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 1 days, 05 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=04/01/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 87e4759c-2884-45e6-9261-c33ba53f596c having Starttime=03/26/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=03/27/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = {0AEBA8CD-59A1-4F26-A664-A39C4711072F} having Starttime=03/26/15 23:59:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 1 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 028bfbc0-7120-4081-a268-0e664a92ac4a having Starttime=03/28/15 00:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 1 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = 49fd80be-ac4b-4877-974d-ecd09958926d having Starttime=03/31/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Service Window with ID = ad27b0ca-8c74-43c7-8200-1f601880bd75 having Starttime=03/30/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Active Service Windows List has 0 windows ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Scheduling the Timer Task ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) Scheduled the timer to fire on 03/26/15 22:00:00 ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) ServiceWindowManager 3/26/2015 9:44:08 AM 4352 (0x1100) OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 3/26/2015 9:44:16 AM 4352 (0x1100) No Service Windows exist for this type. Will check if the program can run in the All Programs window... ServiceWindowManager 3/26/2015 9:44:16 AM 4352 (0x1100) Biggest Active Service Window for Type=1 not found ServiceWindowManager 3/26/2015 9:44:16 AM 4352 (0x1100) Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 3/26/2015 9:44:16 AM 4352 (0x1100) OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) No Service Windows exist for this type. Will check if the program can run in the All Programs window... ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) Biggest Active Service Window for Type=1 not found ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) OnIsServiceWindowAvailable called with: Runtime:900, Type:6 ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) Biggest Active Service Window for Type=6 not found ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 3/26/2015 9:44:31 AM 5824 (0x16C0) https://www.mcpvirtualbusinesscard.com/VBCServer/jrose/profile
