Share via


Task Sequence Deployment - Waiting on service window?

Question

Thursday, February 23, 2017 7:03 PM

Hello, I'm deploying a required task sequence to a collection that does not have a maintenance window configured.  Assignment schedule is configured for As Soon As Possible.  The ServiceWindowManager.log shows this:

OnIsServiceWindowAvailable called with: Runtime:21600, Type:5    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
        Biggest Active Service Window for Type=1 not found    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
Program cannot Run! Setting *canProgramRun to FALSE    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
WillProgramRun called with: Runtime:21600, Type:5    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
No Service Windows of this type exist.    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)
There exists an All Programs window for this duration. The Program will run eventually.    ServiceWindowManager    2/23/2017 1:24:33 PM    2216 (0x08A8)

The particular machine in question is a member of mulitple collections.  One collection does have a maintenance window, but I'm not deploying the task sequence to that collection, I'm deploying it to the collection without a maintenance window.  The maintenance windows are collection specific right?  They don't follow the machine around to different collections do they?

All replies (2)

Thursday, February 23, 2017 7:12 PM âś…Answered

The particular machine in question is a member of mulitple collections.  One collection does have a maintenance window, but I'm not deploying the task sequence to that collection, I'm deploying it to the collection without a maintenance window.  The maintenance windows are collection specific right?  They don't follow the machine around to different collections do they?

Maintenance Windows are not 'collection per deployment' -specific, they are computer specific. If a computer belongs to a collection that has maintenance window defined and it belongs to another collection that has a deployment setted, the maintenance window collection's settings will still be enforced.

More information: https://technet.microsoft.com/fi-fi/library/hh508762.aspx


Thursday, February 23, 2017 7:33 PM

That explains it then.  Thank you.  I wasn't aware that maintenance windows were bound to the machine regardless of what other collections they were members of.