RE: OS Deployments and Maintenance Windows

Hi
I have an MDT task sequence that I am using from within SCCM 2012 R2. Its deployed to a collection for which I have specified a maintenance window. However, when I boot this test OSD client with the media I am still able to deploy the image even outside
the maintenance window.
Where can I start looking to sort this out?
Karl

If you don't want the deployment to be applicable to the device at all, then yes you have to make sure that the device is not targeted by the deployment. That can be by deleting the deployment, or by making sure the device is not member of the collection
anymore.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Software Updates, Tray Pop-ups and Maintenance Windows

I will try to keep it to the point.
End Users in Europe power down their machines every night. Patch Tuesday rolls around, we set the deadline to patch for one week
later (the following Tuesday) @ 10pm.
So they come in that following Wednesday morning, power on their system and bam, software updates are installed and reboots are forced right
there in their earlier AM which is upsetting them.
Our settings? Deployment is required, detail level is “only success and error messages”, “Display in Software Center and show all notifications”, and when the installation
deadline is reached allow the following activities to be performed outside the maintenance window: “Software Update Installation” and “System Restart”.
So before I get a whole bunch of, “disable reboots” or “notify your users” or “use WOL”. I want to discuss this on another angle.
We are getting reports that users are not seeing the notifications. As you can see it is set to all notifications. Likely they are happening and they are not seeing
them.
Main Question: Is there a way via a registry tweak or client setting that will do one of the following:
Make the tray popups more frequent
Make the tray popups last longer
Bring the main “hey things to patch screen” come up without clicking the tray popup
Anything we can do to make the notification BEFORE the deadline more in their faces would be ideal. Anyone?

This happened because patch updates reached deadline and installed forcefully and restart the machines. from
the software center and system tray. Just configure that in the deployment
Unless the site wide hide deployments option is selected,
you will get icons in the system tray. When that is selected, you do NOT get icons at all. If this is enabled, but you suppress the deployment itself, then you get the icons but not balloons.
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

Software Updates and Maintenance Windows

We are running SCCM 2012 R2 Primary Site Server.
We created the Collection for Windows Server 2012 R2 machine and Software Update group containing Software Updates for Server 2012 R2.
We set the maintenance windows on collection "11:00 AM- 2:00 PM"
We deployed the Deployment Package to collection at 11:00 AM, it downloaded the updates but didn't install any updates for 1 hour. At 2:00 PM it said that the No service window available to run updates .
Why didn't SCCM do anything for 1 hour?
Attached is the snippet from Update deployment.log
Evaluation initiated for (1) assignments.- 12:56 PM
Progress received for assignment ({D45DB820-AF28-4FAC-AAFC-7819937A412E})- 12:56 PM
Update (Site_64D995A8-C176-4B35-AFE0-724BB6793EBD/SUM_74b0949d-a84d-4599-8060-e7b982720886) added to the targeted list of deployment ({D45DB820-AF28-4FAC-AAFC-7819937A412E}) - 12:56 PM
Evaluation completed for the assignment {D45DB820-AF28-4FAC-AAFC-7819937A412E} - 12:56 PM
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT END Event- 2:00 PM
No current service window available to run updates assignment with time required = 1 - 2:00 PM
Attempting to cancel any job started at non-business hours.- 2:00 PM

How to enable client randomization? Does it need to be enable for SCCM to deploy updates?
You can download the updatedeployment.log from below link
https://onedrive.live.com/redir?resid=F3743C55DC76B1EE!1099&authkey=!AL40dKaAzl-_trc&ithint=folder%2c.log

Application Scheduling and Maintenance Windows

Hi There. I have a scenario that I want to get some clarification. I think I know how it will work but wonder if I'm understanding it correctly.
I have clients across a WAN that I want to deploy an application to but the bandwidth is limited and I can't put local DPs there. I want to prestage the content and then enforce its installation after the server side of the app has been upgraded
on Saturday.
The collection that the clients are a member has a maintenance window defined daily from 2am to 5am. I was going to deploy the app and make it available for tonight at 8pm thinking that the client would see the deployment and begin to download
it. The application deadline is set for 2 days from now on Saturday at 8pm. Am I correct in thinking that the client will install the application tonight at 2am during it's first available maintenance windows??
If so, my plan is to temporarily replace the daily 2am to 5am maintenance window with a maintenance window that starts at the deployment deadline on Saturday at 8pm. It seems to me that then the client would see the application, download it and wait
to install until 8pm on Saturday when it would be enforced. I also plan to hide the deployment so that it does not show up in software center.
Is my thinking correct?

If your objective is to prestage the content on the client cache, the only way I know that it works, is when the "available" schedule is reached, SCCM will evaluate the deployment and if applicable (meets requirement, detection rules, etc), it will automatically
download the content to the cache folder...
So, if you make it "available" today at 8pm and "required/deadline" for this Saturday 8pm, the clients will download the content after 8pm today (regardless of maintenance windows). The issue, as stated previously, is that if a user decides to go in the
software center app, they can manually trigger the install as soon as the deployment "available" date is reached (~today 8pm). You can configure the notifications...
The actual automatic install (triggered by the client agent software) will only happen on/after Saturday at 8pm; assuming that the maintenance window permits it. Be VERY careful with maintenance windows. If you have it set for 2am-5am daily, the deployment
will install on Sunday 2am-5am, as the window is closed on Saturday at 8pm (deadline)... Also the PC has to be powered on for the install to happen.
As with many things in SCCM, there is always other settings that can affect the result. E.g., you can set the deployment to install/reboot outside maintenance windows...
You may want to test this to confirm...

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

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.

Impdp and scheduler maintenance window

Environment: Oracle 11.1.0.7.0 running on HP-UX B.11.31 U ia64.
I was performing import using impdp. Before starting the import, I manaully disabled the maintenance window.
But once, import over, when I try to enable the maintenance window, when I checked, it got already enabled.
On investigating found that the timing of enable match with the import finish time.
Before performing the import using impdp, I have disabled maintenance window using;
DBMS_SCHEDULER.DISABLE(name=> mwindow,force=>TRUE);
After Import, when i checked the maintenance window using;
SELECT
w.window_name,
w.repeat_interval,
w.duration,
w.enabled
FROM dba_scheduler_windows w
the value as ENABLED = TRUE.
On querying the select * from DBA_SCHEDULER_WINDOW_LOG, the timing of LOG_DATE matches with the import impdp finish time. However on the column ADDITIONAL_INFO
has value of REASON="manually enabled"

Are you doing a system import here ?
If you are doing a system import then properties of the maintenance window will also be imported and that may include enabling the window.
Since a system export exports system-level properties as well, you might need to disable the maintenance window before doing your system export.
Hope this helps,
Ravi.

About maintenance windows and client restart settings

Scenario:
I have an application which is configured so that ConfigMgr Client will force a restart after the installation. This application is going to be deployed to a collection of computers which are also members of another collection that has maintenance window
of 3 hours configured. The default client settings for all the computers have been configured so that users are notified about possible restart for 1440 minutes (24h).
When the deployment is made:
If there are logged on users (on the desktop or locked screen), will the software just install in the 3 hour maintenance window and notify the user about the reboot for 24h after the installation?
If there are not logged on users will it install and reboot the computer?
How this kind of thing should be configured so that the computers will reboot in the maintenance window if they automatically do not with these settings (if or if not there are logged on users on the computers) ?

So I tested this:
User logged on during the MW -> Software installation starts at the maintenance window but asks for the reboot from the user so no go here
User not logged on during the MW -> Software installs and reboots straight away
Solution I'm thinking:
Client Settings Collection that includes all the Maintenance Window Collections and I shall deploy different Client settings (where the reboot time is less than the actual MW) to that collection. This could be also handled with "Install only when user is
not logged on" for the application's deployment type but then again I don't think you can do that kind of setting for software updates or do you?

Maintenance Windows and Installation Deadline

I know this has been discussed many times in the past, but I wanted to clarify in my mind what I think happens.
I have a maintenance window on a collection that is daily between 3:30am and 5:30am. I create a deployment for software updates with an available time at 2:00am. I specify the installation deadline in the deployment for 3:00am.
In the Deadline behavior (user experience) I do not have either option checked (Software updates installation and System restart). So, my MW will not be ignored.
With these settings, the needed updates will be downloaded, but not installed until the start of the maintenance window at 3:30am. (in essence, the deadline should be "before" the MW if I want them to install at the next MW).
Thanks!

I did:
<![LOG[New Service Window Policy notification received.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1" thread="996" file="servicewindowmanager.cpp:217">
<![LOG[CCM::ServiceWindowManager::CServiceWindowHandler::OnPolicyCreated - A policy change has occurred. New policy has been created.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:2044">
<![LOG[    Populating instance of ServiceWindow with ID={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA}, ScheduleString=786F1B4010100008, Type=4]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:104">
<![LOG[        StartTime is 1/16/2015 3:30:00 AM]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1"
thread="996" file="servicewindowhandler.cpp:176">
<![LOG[        Duration for the Service Window is Total days: 0, hours: 02, mins: 00, secs: 00]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:106">
<![LOG[    The Service Window={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} has started at 1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager"
context="" type="1" thread="5032" file="servicewindowhandler.cpp:1200">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:1, Type:4]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420"
file="servicewindowhandler.cpp:2258">
<![LOG[        Biggest Active Service Window has ID = {3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} having Starttime=1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015"
component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1336">
<![LOG[
Duration is 0 days, 02 hours, 00 mins, 00 secs]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1337">
<![LOG[ActiveServiceWindow has 7200 seconds left]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1248">
<![LOG[Program can run! Setting *canProgramRun to TRUE]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1249">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:900, Type:2]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
file="servicewindowhandler.cpp:2258">
<![LOG[No Restricting Service Windows exist. It can therefore run...]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
file="servicewindowhandler.cpp:1510">

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

Maintenance Windows - Best Practices

One of the features of SCCM I've looked forward to the most are Maintenance Windows. The Best Practice Recommendations (in the Help File) suggests that:
"....you should create specific collections for this purpose rather than use the default collections"
If I want to implement Maintenance Windows accross the board, do I need to configure every collection that I create? Will the client get their Maintenance Windows settings as a result of an advertisement on a collection they're in? Or will they get the settings simply by being in a configured collection?
Finally, if I create an advertisement / deployment with, say a 2-week deadline, should I avoid Maintenance Windows for this scenario? The deadline won't override any Maintenance Windows will it?

I can't tell you what to do. However, trying to answer your previous post, I said you could do that. But if you tell the advert/deployment to ignore maintenance windows, then you are not adhering to them at all, and you may get deployments outside the time frame you intended.
If you want to deploy to users, and let them deploy independently, then you don't need maintenance windows at all. But if you want maintenance windows so that assignments are deployed at the deadline, but according to windows, then you have windows defined.
If an assignment is configured to allow end user to run independently of the assignment, then IF a user does that, it ignores maintenance windows. Windows are only adhered to by scheduled tasks, not optional ones that are user driven. So don't configure the assignment to ignore windows, as then it might deploy automatically at the deadline, at a time you didn't want on some servers.
Leave windows inplace, but if users run the advertisement or patch deployment on their own, we don't adhere to windows.
I'd probably look at two templates - one for users and one for servers. The user template would not suppress so the users could deploy manually (clicking the icon). The server template would suppress notifications, and just wait for the deadline, and the appropriate window.
Does that make sense?

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

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.

Client In Multiple Collections - Some have no maintenance windows

If a client is in several collections and a few have maintenance windows is it correct that any deployments targeted to a collection the client is a member of will only run within the earliest maintenance window available regardless of deadline?
So even if it is also in a collection with no MW the deployment to that collection won't run until the MW starts even if it is after the deadline?

Maintenance Windows are not relative to deployments in way and the collection a deployment is applicable to is irrelevant.
MWs they are applied to the clients within that collection. The client then uses all MWs applied to it to restrict the execution of all/any deployments assigned to it (although there are multiple MW types for the different deployment types so that
is of course considered). The collection that the MW or deployment was targeted at is not considered (and in fact not known to client at all).
Also, no MW equates to a 24x7x365 MW.
Jason | http://blog.configmgrftw.com

RE: OS Deployments and Maintenance Windows

Similar Messages

Maybe you are looking for