Maintenance Windows for restart requires app deployment

I want to push out the application that does require the restart to work correctly. How do I make sure to set the maintenance windows so it won't install on the customer computers during office hours? It needs to be start install out of office hours and
do the reboot. How? thanks

More info:
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.

Similar Messages

"Waiting for maintenance window" for pre-approved application installed from software catalog

My understanding is that if a user installs an application from the software catalog that does not require admin approval, it should install right away. A user selected an application yesterday which had a prerequisite that needed to be installed (.NET),
it was installed but the published application never was; it's stuck in the "Waiting for maintenance window" category. I manually reboot the PC a few times thinking that would help, but no go. The deployment's checkboxes for "Software install"
and "System Restart" are grayed out so I can't check them, though it's my understanding they don't apply anyway in this situation.
Anyone have any ideas? Also just for my own knowledge, what would cause the Software Install and System Restart checkboxes to be grayed out so they can't be checked?
-Keith
-Keith Elkin

Available deployments are not affected by maintenance windows or business hours. Examine AppEnforce.log and maintenancecoordinator.log. The Monitoring node might also be useful.
Torsten Meringer | http://www.mssccmfaq.de

Is it possible to have Multiple Browser Windows for a Faces App

I have just read from another thread
http://forum.java.sun.com/thread.jsp?forum=427&thread=308725
that states:
..the RI only keeps state for one URL at a time (in the words of the spec: "if the JSF implementation has saved state information for a tree identifier /foo in the user�s session, but receives a request with URI /faces/bar, the saved state information will be thrown away.").
That means that if you hit the /faces/ servlet with anything (e.g. /faces/css/mainX.css) after it has rendered your .jsp page, all the state necessary to process your form will be lost.
This must mean that I cant have more than one browser window with a faces
app at a time, I think that it is necessary to provide the funcionality.
My application is showing database tables and allows the user to edit them, but to restrict the user to one window doesnt seem feasable.
If you cant have more than 1 window then command_hyperlinks have serious drawbacks in that the user could be tempted to right click and open another window, then the application would not
work when changing from one window to another.
I have an idea but I cant see how to get it to work.
a hidden page-thread id that identifies which browser window/tab the user is on and that identifies a page-thread map that stores values such as the component tree and other things like list iterators, the problem is that if the user "clones" the window you would need to clone the map and change the hidden page id.
Does javascript know a window id that it could send?
Any bright ideas.
How do uSoft manage this?
Is http the right protocol????
As I understand faces apps should be run in a browser window with no back/forward buttons and without any command-hyperlinks to /faces/... so that the user can never break the program, is this correct?
Andy

I have just read from another thread
http://forum.java.sun.com/thread.jsp?forum=427&thread=3
8725
that states:
..the RI only keeps state for one URL at a time (in
the words of the spec: "if the JSF implementation has
saved state information for a tree identifier /foo in
the user�s session, but receives a request with URI
/faces/bar, the saved state information will be
thrown away.").
This used to be the case until EA4 because it has been fixed. Future release will also support necessary API that gives you control over what to save or what not to.
-Jayashri

Firefox Crashes Windows 7 - Restart Required!

All of a sudden today I am unable to run firefox's latest version without my entire system crashing! If I attempt to open Firefox, the window comes up for a split second and then everything freezes up and won't respond to anything (mouse movement, cntrl+alt+del). I have uninstalled and reinstalled Firefox twice now but nothing has helped.
What are the next steps to diagnosing my problem?

Your crashreport is 
https://crash-stats.mozilla.com/report/index/bp-b0f9c7e1-dcde-4d6e-bd4c-a6e0a2111027 
Firefox 7.0.1 Crash Report [@ mozcomp.dll@0xab51 ] 
NEW Startup crash in mozcomp.dll with Oracle Enterprise, F5 Networks, Passlogix V-GO, IBM Tivoli Access Manager SSO 
See related Bug [https://bugzilla.mozilla.org/show_bug.cgi?id=680927 680927] for more info 
The likely problem is use of certain Oracle etc software, the developer Oracle being aware of the problem and working on a fix. Meanwhile there is a registry hack as a potential workaround, or the simpler workaround of downgrading temporarily to firefox 3.6.23.

How to capacity plan for a new app deployment?

I am currently developing a new iphone app and was wondering if there are any white papers and or tools, models to help predict server capacity and how to be able to quickly scale to demand.

roaminggnome wrote:
This is a user support forum. It seems as if you should be posting to the developer forum.
I think someone woke up on the wrong side of the forum this morning.

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?

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

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?

Apply automatic maintenance windowing

Hi all,
We have added SCOM 2012 R2 to our work environment a couple months ago and are currently working on narrowing down the alerts that we are receiving and noticed some returning errors that show up because of scheduled tasks.
The thing is that we have two domain controllers that restart every monday morning on every week. Because of this, two critical alerts show up saying that the Domain Controller Has Stopped. This however is normal because of the scheduled reboot.
I was wondering if it would be possible to apply an automatic maintenance window for a specific server for a specific time.
Because excluding this alert is not an option because then having an unsuspected shutdown for example will not give us an alert.
I hope to hear from you soon.
Thanks in advance,
Bram

Thanks
for info
Regards
Enis,

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.

Maintenance Windows - Start Date

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

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

Software Updates maintenance window

Hi
If I set a maintenance window for SU for a certain day of the month just after the deadline - Lets say they are available a week before.. will user be able to run the updates independently themselves before the MW date?
Cheers

To add a little bit of explanation, maintenance windows only restrict when clients can enforce deadlines and have nothing to do with user activity.
Jason | http://blog.configmgrftw.com | @jasonsandys

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 for restart requires app deployment

Similar Messages

Maybe you are looking for