CM12 SP1 CU1 - CM12 R2 - Maintenance Windows

Hi guys, I'm getting slowly ready to upgrade production to R2 and I just want to double check that I understand this right since I missed to observe this during my lab tests.
I currently have a lot of MWs set in 2012 SP1. All of them are now set with past dates.
If I was to upgrade today, they will convert to All Deployments maintenance windows, is that correct?
As a result of that, systems that are pending reboot because of software update installation
(software updates are allowed to install but not reboot outside of MW as per deployment settings) will not reboot.
Also, I found this in documentation but it is not clear to me.
http://technet.microsoft.com/en-us/library/gg712696.aspx#BKMK_MaintenanceWindow
It talks about software updates installation when general and software update maintenance windows are configured.
What about reboots?
If I have general and software updates maintenance windows configured: General for 24 hours and Software Updates for 4 hours on the same date what happens to:
a) Software Updates deployment with settings to install outside MW but reboot within MW?
I guess that it will install on the deadline I've scheduled outside of Software Updates MW but will reboot when Software Updates MW starts, is that correct?
Plan for a Software Updates Maintenance Window
Starting in System Center 2012 R2 Configuration Manager, you can add a maintenance window dedicated for software updates installation. This lets you configure a general maintenance window and a
different maintenance window for software updates. When a general maintenance window and software updates maintenance window are both configured, clients install software updates only during the software updates maintenance window. For more information about
maintenance windows, see How to Use Maintenance Windows in Configuration Manager.

Your current maintenance windows will convert to all deployment maintenance windows.  You must configure your software update ones separately.  Your systems will not reboot until the maintenance window opens up, that is if you did not configure
reboots outside of maintenance windows.
Your software updates will install at any time because you allowed it outside of maintenance windows.  Your software updates that are pending reboots will stay pending until the maintenance window opens and allows the reboot. 
It looks like you are spot on. 
Best, Jacob I'm a PC.

Similar Messages

  • SCCM 2012 R2 sp1 cu1 ccmsetup.exe still 5.00.7958.1000

    I downloaded sccm 2012 r2 sp1 cu1.  I applied the server update to our Primary server.  I also pushed out the client update (5.00.7958.1203) to all of our servers.  But I have noticed that any new servers are still showing client version as
    5.00.7958.1000.  I checked the version of ccmsetup.exe on our Sccm primary server and it is showing 5.00.7958.1000.  I would have thought when I applied the sccm 2012 r2 sp1 cu1 server update to the primary server it would have updated the ccmsetup.exe
    to version 5.00.7958.1203.  I know with time the client on new boxes will be updated with the client update push I have running on all windows server collection, but why not just have the most current version from the start.  I searched for
    an updated copy of ccmset.exe on the primary server, but never found it.  I checked MS site for the most current version of sccm 2012 client install, but could find that either.  Any help would be greatly appreciated,
    Mark

    Nope. CU1 is simple an update that must be layered on top of the R2 client. You can do this using either SCUP or a program deployment using the package/program that was created during the CU setup.
    For reference:
    http://technet.microsoft.com/en-us/library/jj553405.aspx
    As a side note, this is something on most folks top 10 list of things they want changed but don't count on anything anytime soon.
    Jason | http://blog.configmgrftw.com

  • 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 - 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

  • OSD with SP1 CU1 captured Win7 failed to deploy after R2 CU1 Update

    Hi guys,
    quick question. We currently trying to deploy an Image as i said in the title. The Win7 has been captured with SP1 CU1 an we tried to install the R2 Client during OSD TS. This steps seems is the last that is executed in the TS after that, the TS Fails
    with error: "Failed to create instance for IMTCTokenHandler interface, hr=0x8007005". Any suggestions ??
    Thanks guys....

    In our case it is something related to the WinPE. If we use the version 5.0 (6.3.9600.16384) shipped with R2 the task sequence continues normally. If we change it back to the version 4.0 (6.2.9200.16384) the TS dies with the error from above. Here are some
    more detailed log entries:
    <![LOG[==============================[ OSDSetupHook.exe ]==============================]LOG]!><time="22:03:17.580-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="osdsetuphook.cpp:186">
    <![LOG[Logging successfully initialized to C:\_SMSTaskSequence\Logs]LOG]!><time="22:03:17.612-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="osdsetuphook.cpp:187">
    <![LOG[Executing task sequence]LOG]!><time="22:03:17.612-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="osdsetuphook.cpp:279">
    <![LOG[Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".]LOG]!><time="22:03:17.627-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="basesetuphook.cpp:366">
    <![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="22:03:17.627-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="environmentscope.cpp:659">
    <![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="22:03:17.627-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="environmentscope.cpp:659">
    <![LOG[Saving existing desktop wallpaper settings.]LOG]!><time="22:03:18.299-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="wallpaperselector.cpp:36">
    <![LOG[Setting desktop wallpaper.]LOG]!><time="22:03:18.315-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="wallpaperselector.cpp:57">
    <![LOG[Debug shell is enabled]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="basesetuphook.cpp:1440">
    <![LOG[Spawning system message loop thread.]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="debugwindow.cpp:143">
    <![LOG[Waiting for system message loop to initialize.]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="debugwindow.cpp:152">
    <![LOG[Signaling initialized event.]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2912" file="debugwindow.cpp:182">
    <![LOG[Successfully enabled debug command shell support.]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="debugwindow.cpp:156">
    <![LOG[Configuring local administrator account]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="basesetuphook.cpp:1462">
    <![LOG[Enabling local administrator account]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="basesetuphook.cpp:1219">
    <![LOG[Entering system message loop.]LOG]!><time="22:03:18.424-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2912" file="debugwindow.cpp:187">
    <![LOG[Re-assign all drive letters...]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="diskutils.cpp:1941">
    <![LOG[Partition without driver letter: ]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="diskutils.cpp:1948">
    <![LOG[Partition with driver letter: 0-1;0-2]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="diskutils.cpp:1949">
    <![LOG[Active partition is 0-1. New OS partition info: 0-2.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="diskutils.cpp:1950">
    <![LOG[sPartitionNoDriveLetter.length() > 0, HRESULT=00000000 (e:\nts_sccm_release\sms\framework\tscore\diskutils.cpp,1951)]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="diskutils.cpp:1951">
    <![LOG[The drive information which has no drive letter can not be found. No need to re-assign driver letters.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="diskutils.cpp:1951">
    <![LOG[Installing SMS client]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="basesetuphook.cpp:1474">
    <![LOG[Setting variable to indicate client installation attempted]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:934">
    <![LOG[Clearing existing client configuration.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="installclient.cpp:291">
    <![LOG[Cleaning existing client certificates from SMS certificate store]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:138">
    <![LOG[Restoring SMS client identity.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="installclient.cpp:321">
    <![LOG[The client certificates were not found in the environment. New certificates will be generated.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="installclient.cpp:355">
    <![LOG[Successfully restored the client identity.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="installclient.cpp:359">
    <![LOG[Using CRL: ]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="installclient.cpp:952">
    <![LOG[Unable to read SMS client cert from environment. Not restoring SMS client cert.]LOG]!><time="22:03:18.440-120" date="05-03-2014" component="OSDSetupHook" context="" type="2" thread="2448" file="installclient.cpp:962">
    <![LOG[Succeeded loading resource DLL 'C:\WINDOWS\system32\_SMSOSDSetup\1033\TSRES.DLL']LOG]!><time="22:03:18.503-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="util.cpp:963">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="22:03:18.534-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="commandline.cpp:228">
    <![LOG[Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE]LOG]!><time="22:03:18.534-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="commandline.cpp:731">
    <![LOG[Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE]LOG]!><time="22:03:18.534-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 3052 ]==========]LOG]!><time="22:03:18.659-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3060" file="winmain.cpp:330">
    <![LOG[Command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE]LOG]!><time="22:03:18.659-120" date="05-03-2014" component="TsProgressUI" context="" type="0" thread="3060" file="winmain.cpp:332">
    <![LOG[Registering COM classes]LOG]!><time="22:03:18.659-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3060" file="winmain.cpp:187">
    <![LOG[sbModulePath = C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe]LOG]!><time="22:03:18.659-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3060" file="tsprogressuiclass.cpp:625">
    <![LOG[Unregistering class objects]LOG]!><time="22:03:18.690-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3060" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="22:03:18.690-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3060" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="22:03:18.690-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="commandline.cpp:1123">
    <![LOG[Successfully registered TS Progress UI.]LOG]!><time="22:03:18.690-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="utils.cpp:2279">
    <![LOG[Executing C:\_SMSTaskSequence\OSD\ABC003AE\ccmsetup.exe /useronly /source:C:\_SMSTaskSequence\OSD\ABC003AE /config:MobileClient.TCF /status:524]LOG]!><time="22:03:18.940-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448"
    file="installclient.cpp:1084">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="22:03:18.940-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="commandline.cpp:228">
    <![LOG[Set command line: "C:\_SMSTaskSequence\OSD\ABC003AE\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\ABC003AE /config:MobileClient.TCF /status:524]LOG]!><time="22:03:18.940-120" date="05-03-2014" component="OSDSetupHook" context="" type="0"
    thread="2448" file="commandline.cpp:731">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\ABC003AE\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\ABC003AE /config:MobileClient.TCF /status:524]LOG]!><time="22:03:18.940-120" date="05-03-2014" component="OSDSetupHook" context=""
    type="1" thread="2448" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 0]LOG]!><time="22:04:18.052-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="commandline.cpp:1123">
    <![LOG[Install succeeded. Blocking other instances of ccmsetup.]LOG]!><time="22:04:18.052-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:1097">
    <![LOG[Installed Client]LOG]!><time="22:04:18.052-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:1155">
    <![LOG[Start to cleanup TS policy]LOG]!><time="22:04:18.052-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:3055">
    <![LOG[TS Deleted 0 instances]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:3098">
    <![LOG[TS Policy cleanup done]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:3099">
    <![LOG[End TS policy cleanup]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:3103">
    <![LOG[Setting variable to indicate a client installation was done]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:1166">
    <![LOG[Registering the task sequence with the execution manager in the newly installed operating system.]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="installclient.cpp:1170">
    <![LOG[Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE.]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="2" thread="2448"
    file="utils.cpp:4522">
    <![LOG[Saving the new active request handle for the task sequence: {3980D086-B57D-41B4-AE8E-E25161557E62}]LOG]!><time="22:04:18.068-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="utils.cpp:4535">
    <![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG]!><time="22:04:18.099-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4552">
    <![LOG[Waiting for ccmexec process to start]LOG]!><time="22:04:18.099-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4553">
    <![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG]!><time="22:04:23.226-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4552">
    <![LOG[Waiting for ccmexec process to start]LOG]!><time="22:04:23.226-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4553">
    <![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG]!><time="22:04:28.259-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4552">
    <![LOG[Waiting for ccmexec process to start]LOG]!><time="22:04:28.259-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4553">
    <![LOG[CoCreateInstance succeeded]LOG]!><time="22:04:34.917-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="utils.cpp:4564">
    <![LOG[Succesfully registered the tasksequence with the execution manager]LOG]!><time="22:04:35.324-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="utils.cpp:4597">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="22:04:36.339-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="commandline.cpp:228">
    <![LOG[Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="22:04:36.339-120" date="05-03-2014" component="OSDSetupHook" context="" type="0" thread="2448" file="commandline.cpp:731">
    <![LOG[Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="22:04:36.339-120" date="05-03-2014" component="OSDSetupHook" context="" type="1" thread="2448" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 3260 ]==========]LOG]!><time="22:04:36.527-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3552" file="winmain.cpp:330">
    <![LOG[Unregistering COM classes]LOG]!><time="22:04:36.590-120" date="05-03-2014" component="TsProgressUI" context="" type="1" thread="3552" file="winmain.cpp:204">

  • SCCM 2012 R2 - Maintenance Windows + Installation deadline ASAP + Deadline Randomization

    There are a ton of questions out there regarding MWs and deadlines etc, but I haven't found any yet with my specific question:
    If I:
    Use an ADR that sets the software available time and installation
    deadline both to ASAP 
    AND
    put my machines into maintenance windows
    AND
    enabled deadline randomization (disabled by default in SP1 and R2)
    Will the deadline randomization take place during the maintenance window?
    I know the default setting for the randomization is 0-120 minutes so if I match that and make my MW 2 hours, can I expect all the machines in that MW to patch ONLY during the MW but at a random time during those 2 hrs?

    I tried for a couple days and could not get any of my 3 test machines to patch during the maintenance window with deadline randomization enabled.
    Yesterday I disabled it and over the night, 2 of my 3 machines patched during the MW.
    It doesn't appear to like the proposed setup - I would have anticipated them patching during the MW but during a random time between 0-120 min from when the MW started

  • SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends

    Hi
    Configmgr 2007 sp2
    Client versions : 4.00.6487.2000
    On many of our servers (2003 SP2, 2008 R2 SP1) the SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends. The log gets full in
    less then a second then another log opens and so on!
    Here is an example of a small part of the log file:
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 06:00:00 6988 (0x1B4C)
    Thanks for any help!
    Daniel

    Yes, I know this is an old post, but I’m trying to clean them up.
    This is not normal, I would check the health of the server and I would also use WMIdiag to see if WMI is healthy.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Maintenance Window & User Experience setting

    Hello,
    We're having a lot of issues regulating our Windows Updates, mind you I consider myself novice to intermediate when it comes to SCCM has I have been managing the SCCM software and update deployments for a year or so now at work.
    My question is the following:
    I have Software (Windows) Updates scheduled to be pushed to every workstation on the network on the First Monday morning of every month.
    All of them have an ASAP availability and installation Window so when comes 00:00:01 AM the patches are installed.
    My issue are the multiple reboots in case of update dependencies and or faulty update patches that won't go through until another reboot. Some time it could extend for days, so for the time being the reboots are not enforced.
    I would like to activate the reboots and from my understanding if a maintenance window is say set Monday 1AM to 6AM, all the updates with a deadline will be applied.
    Now i'm wondering two things: First, in the deployment properties in the "Write filter handling for Windows..." under "User Experience" section there is a checkbox that sites "Commit changes
    at deadline or during a maintenance window (requires restarts)". Does this mean that updates will be applied ASAP OR IF a maintenance window is defined it will overrule the deadline as soon as the deadline is over and apply the updates during
    the window and this has nothing to do with Business Hours set on the end-user client Software Center?
    Secondly, with ConfigMgr 2012 SP1 in "Assets and Compliance"
    when I right click the properties of computer group to set the actual maintenance window there's a check box
    "Apply this schedule only to task sequences",  I'm sure the answer is clear, but what exactly does it refer to, like imaging a computer through PXE boot... or?
    thanks!
    Eric

    UPDATE:
    I think I found the answer to my issue....
    In the deployment section under "Deadline Behaviour"
    "When the installation deadline is reached, allow the following activities
    to be performed outside of the maintenance window:"
                - Software updates installation
                - System
    restart (if necessary)
    Those options were checked...... so the reboot ensued anyhow. >;(
    thanks for all your help guys, much appreciated! 
    Eric

  • 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 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

  • 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. 

Maybe you are looking for

  • Exchange 2007 - ValidPorts key data keep reverting

    Randomly on my exchange server (Exchange 2007 SP3 with Rollup 14 on Server 2008 R2, fully patched), the validports registry value data revert from the data I entered to the "default" data. The "default" values I'm describing are machinename:ports and

  • Download attachment speed in mail

    Hi all, I am experiencing something very annoying for quite a while. Whenever I receive emails with attachments it takes forever to download them. i.e I receive an 8megs email and am waiting forever. really 8megs...15minutes on a fast connection! Now

  • Oracle 8i 2003 server error

    oracle 8i startup is 100% ok on windows 2000 but oracle 8i gives service startup failure on windows 2003 advanced server [please help me regarding this problem ... thanx]

  • Image size is too big after "Smart Build Grid"

    The Smart Build Grid feature is awesome. Unfortunately, I have one issue with it- it sometimes zooms the images too much when using the grid feature. Specifically, I have a 4 x 3 matrix of rectangular images. With each Zoom from the grid, Keynote zoo

  • SharedObject.flush / Security.showSettings issue

    First time poster, so hopefully I'm following all the appropriate protocols... Hi!  I'm having a weird problem, and I'm sure the fix is easy, but it's not easy till I know it... I'm compiling in CS4, testing in IE (and stand-alone).  The code I have