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.

Similar Messages

Commit changes at deadline or during a maintenance window (requires restarts)?

What happens in an application deployment if I uncheck "Commit changes at deadline or during a maintenance window (requires restarts)"? If I have an application deployed to a collection with a maintenance window with a scheduled to be available
now with an installation deadline of one week, what would happed? What about if the application was deployed to a collection that did not have a maintenance window and there were no maintenance windows defined in any other collection the member clients
were in?

This is for Embdedded devices, like ThinClients.
That means write filter commits either at deadline or during a maintenance window.
Your application still installs as you schedule it, available now and install week from now. If you have maintenance window and selected to not install or reboot outside of maintenance window, then everything happens within maintenance window. If you don't
check that box for write filter, then your app or setting you have just pushed does not get saved when device is rebooted.
Same scenario with no maintenance windows. If you don't have maintenance window then your app downloads and installs as you schedule the dates. Write filter would not commit these changes and everything would go away after reboot.

Opening multiple document in single instance (window)

Someone here mentioned this: "Acrobat 9 no longer supports opening multiple documents in the same window."
This is disappointing.. does anyone know the workaround / hack?
Running Acrobat 9 Standard.
Thanks,
Devin

Unfortunately yes you're correct. The cause was due to no MDI support, which Adobe removed starting at v9.
Link: http://blogs.adobe.com/acrobat/2008/09/mdi_vs_sdi_in_acrobat.html
If I find a workaround worth mentioning, I'll post it here later.
Thanks.

Multiple tasklist on single maintenance item

Hi gurus,
How can I attach multiple task list to a maintenance Item.
- I want to attach a general task list and a equipment/functional location tasklist to a equipment/functional locations in a maintenance Items
- Is there any way to attach permit to maintenance task list / plan ??
regards
saby

Hello,
You need to create the two maintenance item for the assignment of equipment task list & General Task List and assign it to One maintenance plan.Or You can Use The Object List Tab in aintenance Item Where you can assign the more than one Equipment for One maintenace Item having the Equipment Task List or general Task List.
Maintenace Object List-->You can assign several technical objects to a maintenance item. The maintenance operations that you define for a maintenance item, using the link to a maintenance task list, are due for all the technical objects assigned.
Use of Permit in Task List & Plan not possible as per my knowledge.
Regards,
Rakesh

User receives meeting confirmation during Database Maintenance Window

Hello
I am facing an unusual behaviour which drives me crazy.
A user (it’s unfortunately an important one) receives every night at 02:07 meeting confirmations in his “deleted items” folder.
During this time the Exchange Database Maintenance is scheduled. But I have no idea why this should generate such mails.
I think somehow this maintenance Task sends out a meeting request which is automatically approved by the recipient and the confirmation is sent back to my users deleted item folder.
Someone got an idea what is causing this?

Hi,
From your description, I would like to verify the following things for troubleshooting:
1. Is this meeting a recurring meeting?
2. I recommend you use message tracking to check who sent these specific emails.
Here is an article about message tracking for your reference.
Message Tracking
http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

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

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.

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.

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

Maintenance Windows Set to Use UTC Time Actually Using Local Time on Client

Hey All -
When patching servers last month, we ran into an issue on a couple of collections. This month, it's occurring on all of them so far.
The Issue
We have about 40 collections for various server groups. Each has a single maintenance window set for roughly a 4 hour window using UTC time.
When advertising a task sequence (or something else) to run only inside of the window, it fails. Examining the execmgr.log shows the error: "CExecutionRequest::The program may never run because of Service Window restrictions."
If I open SCCM Client Center, connect to one of the systems, and view Service Windows, I see that they are set, but were set using the hours I set but as if I did not choose UTC when I did. We are in CST which is a 5-06 hour difference therefore it
fails to deploy.
Only Fix So Far
The only fix found so far is to delete the maintenance window and re-create it using the exact same settings. After this is done and policy refreshes, Client Center shows the windows correctly.
The problem with the above fix is that at some point, they seemingly are being corrupted again as some which were fixed last month seem to must be re-created again this month.
Screenshots / Logs
Maintenance Window
8:00PM in our timezone should make it start at 2:00PM CST
SCCM Client Center Viewing Window of System in Collection Same Window Above Was Applied to
Any ideas or suggestions? Thanks!
Ben K.

Hi,
Please review the blog explaining about maintenance windows
and hopefully it will help you.
Business Hours vs. Maintenance Windows with System Center 2012 Configuration Manager
http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Maintenance window modify time

hi
i need to modify the default stat collection so it doesnt run during default maintenance window, can i achieve by chaning default maintenance window ?

Please note that you must disable the probram to disable the window before you make any changes.
Try steps mentioned in below link and it should work.
http://docs.oracle.com/cd/E11882_01/server.112/e25494/tasks004.htm
Regards
http://www.oracleracexpert.com
ORA-12547: TNS:lost contact
http://www.oracleracexpert.com/2011/10/ora-12547-tnslost-contact.html
Repair Block corruptions using Data Recovery Advisor in 11g
http://www.oracleracexpert.com/2011/09/repair-block-corruptions-using-data.html

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

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.

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.

How To Export Windows Forms Multiple DataGridViews in single PDF using iTextSharp, C#

Hi,
I am using VS2010 For my windows application dash board is required for that i am using 6 datagridview to display in form and i want to export all datagridviews to one single pdf please help me out.
How To Export Windows Forms Multiple DataGridViews in single PDF using iTextSharp, C#
Thanks in advance

Hi friend,
Actually iText is a third party library to create PDF originally written for java. iTextSharp is the C# adaptation of that library.
Question regarding iText are better asked on the iText forum, but this is Microsoft Forum:
http://itextpdf.com/support
But I am found a similar thread, it may help you.
http://www.codeproject.com/Questions/442171/How-to-convert-datagridview-to-pdf-in-csharp
Have a nice day!
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Multiple Deployments During Single Maintenance Window

Similar Messages

Maybe you are looking for