Solved

Software Update Scan Cycle - SCCM 2012

Posted on 2013-05-14
2
4,889 Views
Last Modified: 2013-05-15
I have deployed Microsoft updates using automatic deployment rules in SCCM 2012 SP1.  To my surprise, my 1000+ clients are not detecting the updates (including Endpoint Protection definition updates) unless I manually trigger a Software Updates Scan Cycle on the client.  Is there any way to customize the interval for the scan from the SCCM server console?  I desperately need this, as my clients are not getting definition updates for days at a time.
0
Comment
Question by:marrj
2 Comments
 
LVL 1

Author Comment

by:marrj
ID: 39165121
http://technet.microsoft.com/en-us/library/bb694299.aspx

I found this article that describes the process in 2007.  This location does not appear to exist in 2012.
0
 
LVL 17

Accepted Solution

by:
Mike T earned 500 total points
ID: 39167020
Hi,

It still exists but is well hidden in the client settings GUI.

Client update settings

from the excellent walkthrough on TechNet

Sage advice from the System center unleashed book:
"Software Updates

The Software Update section of client settings controls updates behavior. It is enabled by default, but there are several schedule options within the section that should be adjusted.

The software update scan schedule defaults to every seven days, but should be adjusted to every one days. This allows much more timely information to be collected, such as what updates have been applied. This is reflected in reports, which will be current as of the previous day.

The scheduled deployment reevaluation schedule defaults to every seven days and should be left as is. The schedule determines how often the agent checks to see if it is still in compliance with previous deployments, which might result in updates being deployed.

The next setting controls what the agent does when a particular software update deployment deadline is reached, should the agent also opportunistically install any other pending software update deployments. And it allows how far in advance to look for pending software update deployments. Because update deployments frequently result in reboots, it makes sense to deploy future updates at the same time.

The setting defaults to False, so it is recommended to change that to True and the next setting to seven days. This ensures that any updates with mandatory deadlines scheduled up to a week in advance will be deployed at the same time."

 
Mike
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
The System Center Operations Manager 2012, known as SCOM, is a part of the Microsoft system center product that provides the user with infrastructure monitoring and application performance monitoring. SCOM monitors:   Windows or UNIX/LinuxNetwo…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question