Maintenance Window Confusion

Hi there, 
Having some maintenance window confusion. 
According to MS a single maintenance window must not exceed 24hrs - http://technet.microsoft.com/en-us/library/hh508762.aspx
And according to the same document, 2 maintenance windows which overlap, are treated as 1 in terms of duration.
My question is, if you have 2 MW's which are 18 hours long each (so not exceeding 24hrs on thier own) which are overlapping by an hour, is this still still considered as one 35 hour MW? 
Reason being we want a MW to run from 8pm on Friday night till 5am Sunday morning, what's the correct way to go about this? 
Thanks
Jake

a single maintenance window entry cannot be longer than 24 hours, but you can define multiple MW on the same collection. Also if the system is part of different collections with multiple maintenance windows that overlap, they become cumulative.
Have you tried adding a maintenance window for each day? E.g.
- 8pm friday - 8pm saturday
- 8pm saturday - 5am sunday
I didn't try this, but it should work... I use 2x12hour maintenance windows (2 different days) on the same collection.

Similar Messages

  • Maintenance Windows - When a client belongs to more than one collection

    Hi,
    I am a little confused with maintenance windows as I have never had to use them before. I have client that belongs to Collection A with no maintenance window, and Collection B with a maintenance window.   I typically push out apps during
    the day (after they have been tested) so I never use maintenance windows.  I am deploying an application to Collection A (no MW), but it shows in the status that it is waiting for a maintenance window. I assumes it's in this state due to me creating Collection
    B with a maintenance window because I need to push something out this weekend and can only perform this from 10pm to 2am.  If you are deploying an app to a collection, shouldn't look at the maintenance window for THAT collection, instead of
    looking at all the NW for collections a client is added to?  Is there anyway around this?
    Thanks!

    Maintenance Windows are applied to and enforced by the client agent itself. The client enforces the MWs on any and all activity it performs regardless of collection targeting. In fact, clients don't know anything about collections at all. 
    Jason | http://blog.configmgrftw.com

  • Maintenance Windows - Start Date

    Hi. I'm setting up some maintenance windows for a quarterly patching activity - but I'm a bit confused about exactly how that works.
    I want to set the recurrence pattern for every 3 months - and for the 3rd Saturday of each month. No problem.
    But I don't understand how to use the 'effective Date' setting and how this affects when the first one will be?
    So - for instance - if i want to have the first window in my quarterly schedule to be the 3rd Saturday in October - what do i set the effective date to be? The 18th October? Or something else?

    The effective date is when the MW will become effective from on that collection. So if you take a look at the image below I have set the MW to become effective from today but the MW will be open from 01:00 - 04:00 on the 3rd Sat every 3 months for Software
    Updates only.
    Cheers
    Paul | sccmentor.wordpress.com

  • Application (WMF 3.0) won't install during maintenance window, but will install when there is no maintenance window

    Hi All,
    I'm just getting into the Application model in SCCM 2012 R2 and I like what I see so far, but i'm running into an issue.  When i set up an Application for WMF 3.0 with a prerequisite of .Net 4.0 and deploy it to a set of test systems that do not have
    any maintenance windows applied to it, it works great.  If it doesn't have .Net 4.0 it installs both that and WMF 3.0 and reboots.  If it already has .Net 4.0, it will skip that and just install WMF 3.0 and reboot. 
    However, if i deploy it to systems that have a maintenance window applied, the application recognizes that it needs .Net and WMF 3.0 or just WMF 3.0, but it never actually runs. 
    Here is the applicable entry from the appintenteval.log, and i've bolded the line where it shows that WMF 3.0 is not installed
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Title = WMF 3.0, Direct seleted dependencies = ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 title=.Net
    4.0,     AppIntentEval    4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 :- Current State = Installed, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = .Net 4.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/Application_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/RequiredApplication_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy  
     AppIntentEval    4/24/2014 8:20:19 AM    1768 (0x06E8)
    and here are the entries from the AppDiscovery.log that are relevant:
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558" AND Revision = 7)"    AppDiscovery  
     4/24/2014 8:20:19 AM    2776 (0x0AD8)
        Performing detection of app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.    AppDiscovery    4/24/2014 8:20:19
    AM    2776 (0x0AD8)
    +++ Discovered application [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, Revision: 7]    AppDiscovery    4/24/2014 8:20:19 AM    2776 (0x0AD8)
    +++ Detected app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.    AppDiscovery    4/24/2014 8:20:19 AM  
     2776 (0x0AD8)
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66" AND Revision = 12)"    AppDiscovery  
     4/24/2014 8:20:19 AM    2508 (0x09CC)
        Performing detection of app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.    AppDiscovery    4/24/2014 8:20:19
    AM    2508 (0x09CC)
    +++ Application not discovered. [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, Revision: 12]    AppDiscovery    4/24/2014 8:20:19 AM    2508
    (0x09CC)
    +++ Did not detect app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.    AppDiscovery    4/24/2014 8:20:19 AM  
     2508 (0x09CC)
       ActionType - Install will use Content Id: Content_c6b448d0-7b59-4796-bb29-3f7fbfa6e70d + Content Version: 1 for AppDT "WMF 3.0" [ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66],
    Revision - 12    AppDiscovery    4/24/2014 8:20:20 AM    2508 (0x09CC)
    I have a 2 hour maintenance window applied to this system.  From the serviceWindowManager.log:
    OnIsServiceWindowAvailable called with: Runtime:7200, Type:2    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
            Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14
    08:20:00    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
                Duration is 0 days, 02 hours, 00 mins, 00 secs    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    FindBiggestMergedTimeWindow called with TimeStart=04/24/14 08:20:21 and TimeEnd=04/24/14 10:20:00    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
            Biggest Chainable Service Window for Type=1 not found    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    I'm not sure what else to try next and appreciate any help anyone can offer.

    Thanks.  I checked that setting and i have it set to false, so i don't think that's it. 
    I've done a little more experimenting.  I've changed my maintenance window back to 30 minutes.  Prior to the MW opening, i'll run an application evaluation deployment cycle on the system.  It will show the system as required WMF 3.0 but since
    the MW isn't open, it won't install at the time. 
    When the MW opens, i'll watch the ServiceWindowManager.log and it sees that it's a 30 minute MW and that the run time is 15 minutes but it still says the program can't run:
    ActiveServiceWindow has 1800 seconds left    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:6  
     ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
            Biggest Active Service Window for Type=6 not found    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    Program cannot Run! Setting *canProgramRun to FALSE    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:2    ServiceWindowManager    4/24/2014 2:22:32 PM    816 (0x0330)
    If however, i kick off another application evaluation deployment cycle on the system during the open MW, the deployment kicks off right away and finishes. 
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:22:32 PM    2940 (0x0B7C)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:3    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
            Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14 14:20:00    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
                Duration is 0 days, 00 hours, 30 mins, 00 secs    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    ActiveServiceWindow has 1571 seconds left    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    This is not the behavior i would expect.  I would think that if the client knows it has a pending application deployment that is required, when the MW opened up, it would start the install immediately or close to the beginning of the MW.  It shouldn't
    need to have an application evaluation deployment cycle kicked off during the MW. 

  • Maintenance Window not honoured?

    Hi Folks,
    The more I read through these forums on how the Maintenance Window works the more I feel my deployment was set-up correctly. However, I had a number of workstations unexpectedly install Win7 SP1 and restart during business hours (which are defined as
    06:00 to 23:00 with a Configuration Baseline).
    My SP1 deployment is set-up as follows:
    Set as Install, Required, pre-deploy software to user's primary device (checked),
    Advertised at 08:30 with a deadline of 23:30 the same day (last Friday) 
    User Experience is 'Show All Notifications', and has 'Software Installation' and 'System Restart (if required to complete the installation)' unchecked.
    No restart flags specified on SP1 command line, just using /quiet and /nodialog
    Should Config Manager enforce specific behaviour regardless of the applications intended behaviour set to 'No specific action'
    However, a small number of users turned their workstations off when leaving last Friday. When they came in today (Monday morning) the installation was triggered straightway.
    Checking the logs at one of those affected I can see that the Maintenance Window is detected but for some reason is not honoured. I can't see any mention of the user triggering the restart either.
    Am I missing something?
    Thanks,
    Mic

    Business hours and maintenance windows are two different things. Business hours will not prevent the installation from happening when the deadline is reached. For a very good read about this see:
    http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCCM 2012 R2: easy way to disable/enable MULTIPLE maintenance windows at once?

    I have been racking my brain on this one for a while.
    Scenario: you have an ADR set up that is deploying updates once a month. You have multiple collections set up that each have their own special maintenance window (example: 1st weekend - sat - 8-9pm)
    Then, one week you are asked to not deploy updates for the upcoming weekend. Well, the ADR already ran and the machines for "1st weekend" are just waiting for the maintenance window to open. Now, at this point you can obviously go into EACH collection
    associated with "1st weekend" and disable the maintenance window. But if you are asked to do this often and/or you have multiple collections with maintenance windows this could be a hassle.
    Is there a way to easily enable and disable multiple maintenance windows at a time?
    GUI: I have not found a way to select multiple collections and disable all MWs
    PowerShell-module: set-CMMaintenanceWindow doesn't appear to have ability to modify "IsEnabled" property of MWs
    PowerShell-WMI: Can't find in WMI where to modify "Isenabled" Property
    Please see my other thread
    regarding PowerShell
    What other creative options are there? Disable a service via PowerShell on members of "1st Weekend" collections? Which service? Should I be looking in SQL? Where? Other options in GUI?
    I may end up getting stuck doing this manually but I want to make sure I am not overlooking something first... it's such a simple task - just seems like there should be an easy way to accomplish this.
    (And please, for the sake of my question, lets not get into the semantics of whether or not the ADR technically DEPLOYS the updates or not.)

    I didn't even think about that.... so having one MW that is disabled or having no MW at all would allow the client to install at will? I guess I was thinking that if it had a MW but it was disabled it just wouldn't update.
    The MWs on the collections are all different.
    Perhaps I need to re-assess my approach...
    The original plan was to have one ADR (patch tuesday) update 1 SUG (which is deployed to all machines) each month. Machines would then install based off MWs.
    Now I'm thinking it might be best to have 2 ADRS:
    ADR1- updates existing SUG which is already deployed to Dev/Test machines.
    ADR2- creates new SUG - which I then manually deploy to Prod collections. 
    This would automate the deployment to Non-Prod machines but it would give me the power to withhold updates to Prod machines for the month if needed.

  • Maintenance windows applies only to task sequences doesn't work

    Problem:
    SCCM 2012 R2 CU4
    Task sequence deployment run outside maintenance windows when the maintenance windows is set to apply only to task sequences.
    When the maintenance windows is set to apply to All deployments, the task sequence deployment run inside maintenance windows as expected.
    The maintenance task defined was as:
    Name: Maintenance Windows of Collection Coll_A
    Time: 10:30am to 06:00am
    Date: 20th March 2015
    Apply this schedule to: Task Sequences
    The task sequence defined was as:
    Deployed to Collection Coll_A
    Time: Run as soon as possible
    The task sequence run at 9:48am on a workstation that is member of Coll_A.
    There aren't other maintenances windows on others collections.
    Below the workstation's serviceWindowsManager.log:
    https://onedrive.live.com/redir?resid=BFBF530F33D996FD!123&authkey=!AI0dFPZ89XCL7xs&ithint=file%2clog

    When was the client added to the collection? Was it able to retrieve those MW policies before it received the TS?
    Torsten Meringer | http://www.mssccmfaq.de
    1_the client was added at the 9:30am.
    2_Yes it is.
    I have done another test and the result is the same:
    _ first setting up the maintenance windows in Coll_A,
    _ then insert the client in Coll_A and force a machine policy evaluation
    _then deploy the task sequence in collection Coll_A

  • Maintenance Window Question

    Hello Experts,
    i'm sorry if its been already answered, I have a question on MW.
    CollectionA---> has a MW set between 6PM - 6AM ( Monday - Sunday) ( which is set to ->This Schedule Applies to all deployments)
    CollectionA---> has another MW 8PM-10PM ( Sat-Sunday) ( which is set to ->This schedule applies to Software deployments)
    Since there is an overlap, what would happen when Software updates are pushed, Will it run on Sat or sun at 8PM or at 6PM.
    Thank you.

    Hi,
    It depends on the Deadline you set for the updates to install, as you have a maintenance windows that allows all deployments each night, software updates will run then. If you schedule them to start at saturday morning it will start at 6 PM SAT as that
    maintenance windows has the eraliest start time and apply to all deployments.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Multiple Deployments During Single Maintenance Window

    I have a maintenance window that runs from 10PM to 4AM daily. I have three deployments with deadlines during that time. I'm also using the default restart times of 90 minutes and then 15. One of them runs at 11PM, the next at 1AM, and the last at 3AM. Two
    are software updates. 
    So if the first runs at 11PM and the updates install (they had already downloaded prior to the deadline) successfully. They each have a max runtime of 5 minutes. Now a user is still logged in from earlier that day. The 90 minute restart countdown starts.
    Will the second deployment still run at 1AM if the first one hasn't completed its restart yet?

    I'm not 100% sure, but I think it will need the restart first.

  • Maintenance Windows - I need another pair of eyes

    Hello Everyone,
    I am looking for a second pair of eyes to ensure I have this process down 100%. The goal is a scheduled client computer reboot following the May patch install.
    Assign a 12 hour maintenance window on my client computer collection.
    Enforce a 10 hour reboot cycle (initial notification).
    Enforce a non-dismissible notification at the 3 hour mark.
    I am running some final tests today. Below is my maintenance window:
    This is the reboot behavior I assigned:
    My first test this morning resulted in the computer say it was going to reboot in 90 minutes! I double checked the computer only had the single maintenance window applied and the client settings were assigned and set properly. I'm concerned there may be
    some hidden maximum value on the restart settings.

    Ensure that you don't have any applications/updates that are set to install and reboot outside of maintenance windows.
    If my answer helped you, check out my blog:
    DeployHappiness. Subscribe by
    RSS or
    email. 

  • Archive download-sw: Can it be run before a maintenance window

    I need to perform an IOS update on a stack of two 3750X switches and have an after hours maintenance window, but would like to do as much as possible before the window to reduce downtime. I plan on running the archive download-sw command to pull the new IOS version from a tftp server but I am not sure if this itself will cause any downtime. Am I able to run this command beforehand and then wait until the maintenance window to issue the reload command with out causing any downtime?
    Thanks in advance for any help

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    As Reza has already described, yes you can.  However, do be aware that copying images onto flash will increase the CPU (not normally a problem, but you might see the CLI get very slow.  Often loading a new image requires removing the running image, first.  If that's needed, if for any reason the stack reloads during the copying process, the stack may not boot normally.  Also, after the stack is configured for the new software (again if old software had to be removed), any premature reload will boot into it.  If you do have sufficient flash space for both old and new, you can keep or set boot var pointing to the old code.
    Using the bin IOS images saves some space on flash and the image copying goes a bit faster, especially if you can open multiple telnet sessions and copy to multiple stack members concurrently.
    When Reza mentions using a USB, you can, but you can also do what he describes using a TFTP or FTP server.
    Some IOS upgrades' first boot take much, much longer to boot (as they also upgrade firmware).

  • SCCM 2012 R2 - Maintenance Windows - a few questions

    Let's say I configure a maintenance windows (MW) for the 2nd saturday of every month from 6p-10p and I have 100 servers in this maintenance window,
    are they all going to try and patch and reboot at the same time?
    (Assuming they are all online)
    This brings up concerns when trying to plan maintenance windows for our servers - especially when we are 80%+ virtualized. I can't find anything that states the sequence of events that happen when a machine goes to install patches based on a MW.
    Do they wait on a heartbeat? Do they typically kick off right at the front of the MW? Does SCCM spread the installs out?
    We currently use WSUS (working on migrating to SCCM) and in WSUS we have a ton of groups based on the hour so we spread out the machines being patched. I am trying to avoid having so many different options and times and instead just using MWs.
    Another issue we are going to run into is certain machines need to be patched/rebooted in a certain order and with others we just cant have them all down at the same time (e.g. domain controllers). I supposed I could create 2-3 phases per patch weekend to
    spread those machines out - is that the best option? (for instance; on the 2nd Saturday we have MW Phase 1 from 6p-8, MW Phase 2 from 8-10, and MW Phase 3 from 10-midnight)

    Let's say I configure a maintenance windows (MW) for the 2nd saturday of every month from 6p-10p and I have 100 servers in this maintenance window,
    are they all going to try and patch and reboot at the same time?
    (Assuming they are all online)
    This brings up concerns when trying to plan maintenance windows for our servers - especially when we are 80%+ virtualized. I can't find anything that states the sequence of events that happen when a machine goes to install patches based on a MW.
    Do they wait on a heartbeat? Do they typically kick off right at the front of the MW? Does SCCM spread the installs out?
    We currently use WSUS (working on migrating to SCCM) and in WSUS we have a ton of groups based on the hour so we spread out the machines being patched. I am trying to avoid having so many different options and times and instead just using MWs.
    Another issue we are going to run into is certain machines need to be patched/rebooted in a certain order and with others we just cant have them all down at the same time (e.g. domain controllers). I supposed I could create 2-3 phases per patch weekend to
    spread those machines out - is that the best option? (for instance; on the 2nd Saturday we have MW Phase 1 from 6p-8, MW Phase 2 from 8-10, and MW Phase 3 from 10-midnight)
    Hi,
    I often help customers with this scenario that you are facing. I'll try to answer your questions as clearly as possible.
    A) Yes, if you have 100 servers in one MW during 6p-10p, they will start at 6p if they have recieved the policy before that. What you can do is to activate the Deadline randomization that was introduced in ConfigMgr 2012 SP1. You can read more on that here
    http://technet.microsoft.com/en-us/library/gg682067.aspx
    B) ConfigMgr does not wait for a heartbeat or anything like that. You need to manage to logic to move your workload from hosts before you take them down for a reboot. VMM could help you with this IIRC. Or at least SCSM SMA and PowerShell. The sequence is
    basically that they install the patches, if a reboot is required, it will reboot at the end of the patches.
    C) Yes you need to create different MWs and place those servers in the MW order that they need to be rebooted. Be careful tough. If you have ServerA, ServerB and ServerC that need to reboot in that order. You place them in MWs in that order. You might end
    up getting patches to some or all of those servers from a Patch Tuesday but perhaps only ServerB will need a reboot so only ServerB will reboot and thus put you in a place you don't want to be. To solve this, create a re-running package/program deployment
    that reboots ALL servers that are sensitive each and EVERY MW.
    Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

  • Deadline VS Maintenance Window

    I have configured the device collection for maintenance at 12am-6am everyday.I recently deployed windows update as required and deadline at 5pm. My understanding is that after 5pm, the update will wait till the next maintenance windows before it's installed.
    However, the updates keeps installing at 5pm or whatever deadline i configure.
    Am i having a wrong assumption or is my SCCM not configured correctly?

    That is proper assumption only if under User Experience tab on software deployment you have
    not selected any check boxes under Deadline behavior.

  • Deadline, Business Hours vs. Maintenance Windows

    I read the blog about Business Hours vs. Maintenance Windows, but I still have two questions
    http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
    Event 1: Application A
    No Maintenance Windows &  No Wake on LAN;
    Business hours is 5am to 10pm;
    User start laptop at 8AM and close at 5PM every day;
    Deadline is 11PM, Thursday;
    Available is 9Am, Monday, User clicks "Install Later".
    So when A will be installed?
    Event 2: Application B
    Maintenance Windows is 1AM to 4AM , NO Wake on LAN, B has not been configured that install when out of Maintenance Windows;
    Business hours is 5am to 10pm;
    User start laptop at 8AM and close at 5PM every day;
    Deadline is 11PM, Thursday;
    Available is 9Am, Monday, User clicks "Install Later".
    User never start laptop in Maintenance Windows time, so if it mean that B will never be installed?

    To add a couple of clarifying points to the article linked:
    - Business hours are meaningless after a deployment's deadline and are only used before the deadline.
    - Business hours are only relevant if a user has explicitly stated for a deployment to be enforced outside of their business hours.
    - The intent of business hours is to allow users to schedule enforcement of a required deployment before a deadline but outside of their work hours so it never interrupts them.
    The article does say all of this, just not as directly.
    For Event 2 (application b), this is why using maintenance windows usually doesn't work well for workstations. Why would the business hours be set for 5AM to 10PM though? That really makes no sense based on my third point above. Of course in this case, if
    the system is totally off, it doesn't really matter anyway.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Windows Media Player keeping Automatic Maintenance window/Windows Updates from doing auto-restart

    I have a system that is connected to a domain, and it runs a video playlist in Windows Media Player for digital signage upon bootup (and auto-login).  WMP is set to loop the videos over and over again, but it also is preventing automatic updates from
    installing and/or auto-restarting at 3:00AM in the morning (and yes, the system power management is set to keep the computer on all the time).
    How can I fix this?
    I have a GPO set up to install updates and restart automatically (option 4).  I tried the GPO option to use the Windows 8 maintenance window to install updates, and also tried turning that option off and just using a 3:00AM restart period.  Neither
    option seems to work, so it looks like Windows Media Player is preventing an auto-restart to finish the update installation.  Is there any way around this, so that Windows Media Player doesn't stop Windows Updates from doing its job?  I don't care
    if that means the video stops playing because it just starts up again on the next bootup.
    I looked at the WMP GPO's and the only option that sounds like it's related is the option to turn on or off the auto-updating of media info for WMP, but it has nothing to do with what I'm trying to accomplish.  If I missed something, let me know. 
    If there is some other way to accomplish this, such as associating and launching the playlist file with the Xbox Videos app, I would be fine with that, but I need it to loop the playlist continually (I also use the Shuffle option
    in WMP - ***see note below for another question).  I still want the system to automatically install updates and reboot on a regular schedule despite the video playing in the foreground.
    ***Side question: is there any way to turn Repeat and Shuffle options on in WMP without having to load the GUI (for scripting a playlist)?
    Just FYI: this system is actually using Windows Embedded 8.1 Industry Enterprise (from a MAPS account), but it isn't customized aside from not having the standard WinRT apps from a stock Win 8.1 install loaded - it is a stock install from the ISO. 
    From what I understand, it is the same as Windows 8.1 Enterprise, except that it is only licensed to be used as an "appliance" machine for a single role - which it is.  So I'm assuming that there are no actual differences from a "regular"
    Windows 8.1 SKU that would cause this issue.  If I am completely mistaken about this, please notify me on it.  The reason I'm making this statement is in case there are any differences in Embedded 8.1 Industry Enterprise that I am not aware of. 
    Otherwise, I welcome any assistance that would target a "regular" version of 8.1 Enterprise.  NOTE:  Someone said to post this into the Windows Embedded forum, but the only one that exists is the one for POSready - and this is HARDLY the
    POSready version of Windows Embedded that I'm using.

    Hi,
    Did you use the policy Local Computer Policy\Administrative Templates\Windows Components\Windows Update\Always automatically restart at the scheduled time?
    I noticed an description "restart with logged on users for scheduled automatic updates installations" policy is enabled, then this policy has no effect." it means if system installed some updates which unneeds restart computer, this policy would has no effect.
    In my opinion, your problem should not caused by WMP setting. please check your installed updates whether they need restart computer.
    In addition, Power Managment in Control Panel also can prevent the schedule task running.
    Control Panel\System and Security\Power Options\Edit Plan Settings\Change advanced power settings\Sleep\Allow wake timers
    Please make sure this option is enable.
    Roger Lu
    TechNet Community Support

Maybe you are looking for