Automating Software Updates

The monthly process of preparing and deploying software updates is familiar territory for every ConfigMgr administrator. But, monthly software update management is not only about deployment. Maintenance of the software update environment is a critical activity needed to foster ongoing predictable and healthy operation. The amount of monthly time invested in deployment and maintenance will…

11

Configuring multiple Software Update Points in a ConfigMgr 2012 Primary Site – What to expect

I worked through the process of configuring a second Software Update Point (SUP) on my lab Primary site to see how it all works.  It was different than what I expected but is very easy and straight forward to implement. First things first – the installation requirements.  Each SUP requires it’s own WSUS instance.  Note…

3

Modifying a Report to Merge Software Update Deployments with Updates Delivered Through Standard Software Distribution.

A common question I continue to hear is how to create a report that will give the results of all updates deployed to a system, whether that update is delivered through the traditional software updates mechanism or through standard software distribution, such as a package.  This is an important question since in the world of…

0

Using System Center Update Publisher 2007 with Verisign Certificates

Using System Center Update Publisher with Verisign Certificates The System Center Update Publisher (SCUP) allows for third party or custom updates to be published in the WSUS catalog for consumption by ConfigMgr or other systems that use WSUS as a back end. Configuring SCUP to work with WSUS requires the use of certificates to ‘sign’…

1

System Center Updates Publisher 2007 and WSUS Self-Signed Cert Option

What exactly do you need to do to get your environment ready to use the System Center Updates Publisher (SCUP) with the WSUS Self-Signed Cert (WSSC) option? There are a few key steps. First, you have to configure SCUP to sign patches with the WSSC. To do that, select the settings option from the console…

1

Software Updates–INTERNALS! (MMS 2011 session)–part III

In this final installment of this software updates series we will review the software update synchronization process.  There are a couple of variations of the sync process but, as you might expect, all involve a WSUS server – known as a software update point in ConfigMgr– at each primary (and in some cases secondary) site…

0

Software Updates–INTERNALS! (MMS 2011 session)–part II

In part II of this discussion we will review CI’s and SDM packages.  Our discussion is focused on software updates but the concepts we will discuss also apply to DCM, NAP and OSD – all components that are built on the CI and SDM objects. First, some definitions. CI – A CI is short for…

1

Software Updates–INTERNALS! (MMS 2011 session)–part I

Several folks have asked that I transform my MMS 2011 presentation on the internals of software updates into a blog post.  Happy to oblige! The topic at hand is focused on software updating – in my MMS presentation I discussed the WSUS (SUP) sync process, SDM and CI’s, what they are and how they are…

3

SCCM state messaging–in depth

State messaging is a new mechanism in SCCM which reflects point in time conditions on the client.  Status messages, by contrast, work to help administrators track the flow of data through various SCCM components.  There is even a status message viewer built right into the console so these messages can be viewed and tracked.  There…

11

SCCM Patching and OpsMgr Maintenance Mode

Customers using OpsMgr for monitoring and SCCM for patching commonly select the option in SCCM to put MOM/OpsMgr agents in maintenance mode during patching – or even with standard software distribution. This option works great if running MOM 2005 but does not operate as you might think with OpsMgr 2007.  When you set this option…

1