SCCM Software Center – set “Auto install outside of business hours”

sccm-2012sccm-2012-r2

I've managed to use a Baseline Configuration to set business hours for my clients via remediation.

I'd like to do the same/similar for "Automatically install or uninstall required software and restart the computer only outside of the specified business hours" checkbox.

BACKGROUNDER

We used to install updates as soon as they came in… users don't like it so much when .NET churns their PC for an update, so I set an installation deadline of 7 days from when they are found via ADR.

The settings say "after deadline – install outside of maintenance window" I have updates that just came into my PC and are saying "What do you want to do with these"

Well, I'd LIKE these updates to install at the first available maintenance window and I think I need that little box checked, or will they install tonight, whether I do anything or not?

Best Answer

Well, I'd LIKE these updates to install at the first available maintenance window and I think I need that little box checked, or will they install tonight, whether I do anything or not?

solution http://www.myitforum.com/forums/Software-Center-Business-Hours-and-Computer-Maintenance-m244096.aspx

Related Solutions

SCCM 2012 software updates failing

As stated on the question, I had rebooted the SQL server without success.

I opened a case with MS support and the analyst recommended rebooting both SQL server and SCCM server.

I tried this and the server is now syncing correctly with Windows Update.

The original cause of the issue was that the SQL server ran out of space. I did not have this information before. The space issue was fixed and the server rebooted, however, a reboot of both servers was necessary in this case.

SCCM: Zoinks… Mystery Maintenance Windows

I Have No Idea What I'm Doing

Like most things Systems Center Configuration Manager, I'm sure there is a perfectly logical reasons for why things are the way they are but as a lowly technician I am also sure I'll never understand why.

I checked using the Policy Spy from System Center 2012 R2 Configuration Manager Toolkit and again verified that, yes I am getting the two Maintenance Windows that I expected to find except that F51051BF starts one hour earlier than it should:

CCM Service Window

If I correlate that list with all of the available Maintenance Windows I find the ServiceWindowIDs of the exact Maintenance Windows I expect to see and while the it's clipped off in the screenshot F51051BF does indeed begin at 20:00:

SELECT * FROM v_ServiceWindow
ORDER BY ServiceWindowID

Results of the above SQL Query

What about a machine that has the same Maintenance Windows that is working as expected (i.e., the Maintenance Window is starting at 20:00):

Biggest Active Service Window has ID = {F51051BF-90E8-4ED7-BA06-F74F9E74A098} having Starttime=3/5/2015 7:00:00 PM  ServiceWindowManager    3/5/2015 10:00:00 PM    68400 (0x10B30)

Wait WUT? That line was from another client's ServiceWindowManager.log and it certainly believed that 19:00 was the appropriate time to start. I checked a few others. Guess what. Not a single mention of F51051BF-90E8-4ED7-BA06-F74F9E74A098 starting at 20:00... but if I look at the what is listed in the database AND in the Configuration Manager Console the Thurs. Night Maintenance Window is listed as starting at 20:00.

Zoinks! It's not a mystery maintenance window! It's a masked maintenance window!

It looks like that for whatever reason F51051BF is configured to start at 20:00. The Configuration Manager Console reports that and so does the database but if I look at a handful of clients some go 19:00 and others at 20:00.

Two WAG (Wild Ass Guesses): 1) We have old Machine Policies hanging around from a previously implemented ConfigMgr 2007 Site. or 2) the Maintenance Window policy got changed from 19:00 to 20:00 at some point and the not every machine got the news. Whatever. I have no idea what I'm doing here.

Resolution

I created a new Maintenance Window to replace F51051BF and assigned it to the appropriate Collection. I waited an hour or two for the clients to do their policy pulls and guess what:

Service Window with ID = {D047CD9F-25E4-4EDC-95E3-44E971E234FA} having Starttime=3/19/2015 8:00:00 PM   ServiceWindowManager    3/16/2015 12:13:41 PM   15500 (0x3C8C)

Mystery solved? Not really. Problem solved? More or less...spooky huh?

Shaggy and Scooby