ConfigMgr 2012 : WSUS, ConfigMgr 2007

ConfigMgr Software Updates - definition of the coloured icons

Rob Marshall - MVP — Wed, 12 May 2010 08:43:00 GMT

If I don't use the feature often I tend to forget the colour coding, we all know what the green means, most of us know what grey means, but what are the other colours for?

Normal Icon

The green icon represents a normal software update.

Description:

Software updates that have been synchronized available for deployment.

Operational Concerns:

There are no operational concerns.

Expired Icon

The grey icon represents an expired software update. Expired software updates can also be identified by viewing the Expired column for the software update when it displays in the Configuration Manager console.

Description:

Expired software updates were previously deployable to client computers, but once a software update is expired, new deployments can no longer be created for the updates. Existing deployments that contain an expired update continues to work.

Operational Concerns:

Expired software updates should be replaced when possible. Expired software updates that have been deployed continue to work and will continue to be tracked for software update compliance. Expired software updates are considered "not required" for reporting purposes.

Superseded Icon

The yellow icon represents a software update that has been superseded by another update. Superseded updates can also be identified by viewing the Superseded column for the software update when it displays in the Configuration Manager console.

Description:

Superseded software updates have been replaced with newer versions of the update, but are still deployable. For example, a software update that has been included in a service pack or update rollup would be superseded.

Operational Concerns:

When possible, you should deploy the superseding software update to client computers instead of the update that was superseded. When selecting a superseded software update in the Configuration Manager console, the Superseded tab displays that provides a list of the software updates that supersede the selected update.

Invalid Icon

The red icon represents an invalid software update.

Description:

Invalid software updates are deployed but for some reason, the content (update file) is not available. There are 2 main ways this could happen – first is that updates get deployed successfully but sometime later someone deletes the update binary from a package; second is one a child site, where the deployment created at a parent site has been replicated successfully, but for some reason, the deployment packages have not been replicated to a distribution point for the child site

Operational Concerns:

The invalid software update needs to be redeployed. When content is missing for an update in a deployment created at a parent site, the software update needs to replicated or re-downloaded on child sites.

Metadata-Only Icon

The blue icon represents a metadata-only software update.

Description:

Metadata-only software updates are available in the Configuration Manager console for reporting and cannot be deployed or downloaded because an update file is not associated with the software updates metadata.

Operational Concerns:

Metadata-only software updates are available for reporting purposes and are not intended to be used in software update deployments.

Locked Software Update Icons

The software updates metadata is synchronized at the highest site in the Configuration Manager hierarchy that has an active software update point, which is usually the central site. The properties for the software updates can be modified at the central site, but at child sites the properties are locked. This is indicated by a lock displayed on the software update icon.

Lovingly ripped from: http://technet.microsoft.com/en-us/library/bb632404.aspx

Microsoft Survey: ConfigMgr and WSUS pain points

Rob Marshall - MVP — Tue, 11 May 2010 08:32:00 GMT

Time to get some feedback to MS on the WSUS and Configmgr integration.

Check out the survey here, takes literally one minute, no login required and the feedback is seen by the product group, who, as you know, roll the dice on the features and any updates they get.

Survey: What are your top pain points for the use of ConfigMgr and WSUS?

If you love taking surveys, and who doesn't, then you'll definitely want to stop by MyITForum and give ours a shot. And if you're thinking "Wow, I love surveys, but who has the time?" then don't worry, ours is only a single question. It doesn't get much easier than that. So if you'd like to send us some feedback on what your top pain points are with regards to System Center Configuration Manager 2007 and WSUS then head on over to the following link and let us hear from you:

This is a MS survey, hosted over on myITforum. Check it out here http://www.myitforum.com/absolutenm/templates/?a=17048&z=120

I've already fed back a request ...

ConfigMgr: SUP\WSUS communications failure

Rob Marshall - MVP — Tue, 14 Oct 2008 11:16:00 GMT

Came across an SMS Admin today with an interesting problem. He has WSUS\SUP + all the other gubbings all on the one box, nothing really out of the norm and yet he gets Status Message ID 6701 followed by 6703 exactly 5 minutes later (the timeout value) in his WSYNCMGR log when attempting to get WSUS to SYNC with Microsoft Updates. Really he should be seeing 6701 followed by 6704 (recalling from memory here!) and 6701 means that the Sync is initialising and 6704 that it is in progress.

Odd thing is, if you remove the FQDN for the Site server (role wizard) the problem disappears. I could have left it like that, but didn't want too as it's etched in stone that supplying an FQDN for the Site server is good working practice. Well, it is.

Anyway, I discovered that if you add the Site servers FQDN to the Site servers Internet Explorer Trust Sites then add the FQDN back in to the Site server, it all slots in to place and performs the Sync successfully.

Now am not too sure of the root cause here, this in my eyes is a work-around and as its not a documented step I'm assuming not that many of you are actually experiencing this issue. If you've seen this, getting this, this fixed it for you then let me know!

On the subject of SUP\WSUS i've seen some real funny (well not so funny, maybe strange is a better word!) things happening, nearly all of which has been related to a non-standard "environment". And then i've seen SUP\WSUS go on (install), sync and bring down updates without any hiccups.

If you are experiencing SUP\WSUS issues then go back to step 1, analyse your environment and try to determine what is putting SUP\WSUS nose out of joint, as the product does work, first time, even if you follow the instructions verbatim