using SCCM 2012 in a LAB - Part 6. Deploying Software Updates

[Special Ed]

When you have SCCM configured to handle WSUS, should a client machine be able to run Windows update? Or will they get this error? My clients are getting a Windows could not search for updates error when they try it manually.

[mpepprell]

Hey

 

The wizard, when downloading updates to the update package has the following unhappy results:

 

 

Error: The process is not in background processing mode.

Package:

Success: The software updates were placed in the existing package:

• Windows 7 Updates (Sept 17 2012)

Software updates downloaded from the internet

Error: Security Update for Windows 7 (KB975467)

Errors

The process is not in background processing mode.

Security Update for Windows 7 (KB979482)

Microsoft .NET Framework 3.5 SP1 Security Update for Windows 7 x86 (KB979916)

Security Update for Windows 7 (KB982665)

Security Update for Windows 7 (KB2124261)

Security Update for Windows 7 (KB2271195)

Security Update for Windows 7 (KB2347290)

Security Update for Windows 7 (KB2378111)

Security Update for Windows 7 (KB2442962)

 

[...]

 

Cumulative Security Update for Internet Explorer 8 for Windows 7 (KB2744842)

Cumulative Security Update for Internet Explorer 9 for Windows 7 (KB2744842)

 

The following services have been restarted and the downloading of updates attempted again:

 

Bits, Windows Update

 

The SCCM server does have a connection to the Internet. So, now... I am asking for help (again!)

 

Update:

 

I have done the following, as recommended here: http://bit.ly/oO2iWa

The error, however, is still occuring. I can synchronize with Microsoft Update fine, with no error. However, when downloading the updates to the update the distribution package the following occurs:

 

Error: The process is not in background processing mode

 

-- Matt

Edited September 25, 2012 by mpepprell

[Azfar]

Dear, I followed the entire topic and getting superseded error on most/all of the updates in log file. Please advice.

 

Skipped update 45a998db-0cd8-47cd-b917-ef6ab059e70c - Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 for Itanium-based Systems (KB2675157) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:05.080-300><thread=2844 (0xB1C)>

Skipped update 1581a364-a485-43de-872f-7252a661a01d - Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 for Itanium-based Systems (KB2699988) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:05.284-300><thread=2844 (0xB1C)>

Skipped update 89b634b6-b818-46b6-abbc-4a3fc2747496 - Cumulative Security Update for Internet Explorer 9 for Windows Vista for x64-based Systems (KB2675157) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:05.676-300><thread=2844 (0xB1C)>

Skipped update 637277d4-e733-4471-a5ea-799e888ee750 - Cumulative Security Update for Internet Explorer 9 for Windows Vista for x64-based Systems (KB2699988) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:05.898-300><thread=2844 (0xB1C)>

Skipped update 420e1f75-15e5-4af1-8d08-83d1f317cf02 - Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 x64 Edition (KB2699988) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:06.177-300><thread=2844 (0xB1C)>

Skipped update 506508b4-dd57-4a46-a217-118c2a148566 - Cumulative Security Update for Internet Explorer 9 for Windows 7 (KB2675157) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:06.535-300><thread=2844 (0xB1C)>

Skipped update 538d4f66-e213-4010-8c18-b4722caaaedc - Cumulative Security Update for Internet Explorer 9 for Windows 7 (KB2699988) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:06.780-300><thread=2844 (0xB1C)>

Skipped update b8bc9bd9-6ce1-405a-8f0d-b4ec0cf1926e - Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 (KB2699988) because it was superseded. $$<SMS_WSUS_SYNC_MANAGER><09-26-2012 00:21:07.059-300><thread=2844 (0xB1C)>

[Peter van der Woude]

You should always cleanup your Deployments and Deployment Packages and remove the expired and superseded updates.

[ercole77]

Hi,

 

2 questions

 

 

1) in a production environment is correct to use BULLETTIN ID=MS? In other words, are all the security patches included in MS bullettins or am i missing something ?

 

 

2) Im going to create this:

 

a) a compliance group (not deployed) with all the patches (more than 1000)

 

b ) one or more updates group deployed to all systems for past patches

 

c) ADRs for monthly patches

 

 

Compliance group must be deployed and disabled or not deployed?

 

Many thanks for your guides !

[hhancock]

use ADR (automatic deployment rules) to do your patch tuesday monthly updates. I'll do a new post on that sooner or later

 

Have you done this yet?

[hhancock]

Is there a particular log file that I can view to monitor the progress of the Windows 7 Updates deployment?

[adsl.jalawiah]

Thanks for the excellent write up. I am sure that Systems Admins around the globe will find this very useful. Please can anyone assist me with the following

 

Problem 1

Configuration Manager Trace Log Tool

 

I understand this is related to the license agreement. But when I go back to SCCM 2012 and check Software Library, Windows 7 updates, I cannot find any update that has Lincense Terms = Required. How can I sort this issue.

 

 

 

Problem 2

In end of Part 6, it is mentioned to

create a new collection called Build and Capture Windows 7 X64 and repeat the above Deployment for our Windows 7 Updates and target it to the Build and Capture Windows 7 X64 Collection as follows

How to do this.

If I go to Assets & Compliance, Device Collection and Click Create New Device Collection

It is asking for limiting collection. Which collection should I select here? Please advice.

[louwie]

 

 

Problem 2

In end of Part 6, it is mentioned to

create a new collection called Build and Capture Windows 7 X64 and repeat the above Deployment for our Windows 7 Updates and target it to the Build and Capture Windows 7 X64 Collection as follows

How to do this.

If I go to Assets & Compliance, Device Collection and Click Create New Device Collection

It is asking for limiting collection. Which collection should I select here? Please advice.

 

Same for me, please advise how to create the collection. What need to choose at "limiting collection" and what queru rule i need to use....

[anyweb]

as it's a build and capture collection it can be empty (no membership rules)

you can add computers to that collection using a direct membership rule later or by using computer association.

 

the limiting collection can be All systems or all windows 7 computers, it's up to you.