Jump to content


anyweb

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

Recommended Posts

when you say "Create new Build and Capture Windows 7 X64 collection"

 

I think i am missing something. I can create a "Device" and "User" collections. where do i have to create "Build and Capture Collection"?

 

Thank you.

 

Hey,

 

Click on Assets and Compliance --> Right click Device Collections --> Click Create Device Collection.

  • Like 1

Share this post


Link to post
Share on other sites

I can't seem to get any updates deployed. They syncronization is working between my WSUS server on the CA and the WSUS server on the primary, but when i try to deploy an update I get 0x80244022 errors everywhere, especially in the WindowsUpdate.log on the client and in the WUHandler.log on the servers. In additon i am seeing a 503 error on the server logs. Below is some content of the WindowsUpdate.log on the client.

 

012-05-07 09:20:34:711 2860 11a8 COMAPI -------------

2012-05-07 09:20:34:712 2860 11a8 COMAPI WARNING: Operation failed due to earlier error, hr=80244022

2012-05-07 09:20:34:712 2860 11a8 COMAPI FATAL: Unable to complete asynchronous search. (hr=80244022)

2012-05-07 09:20:39:037 2860 11a8 COMAPI -------------

2012-05-07 09:20:39:037 2860 11a8 COMAPI -- START -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:20:39:037 2860 11a8 COMAPI ---------

2012-05-07 09:20:39:039 2860 11a8 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:20:39:039 924 1abc Agent *************

2012-05-07 09:20:39:039 924 1abc Agent ** START ** Agent: Finding updates [CallerId = CcmExec]

2012-05-07 09:20:39:039 924 1abc Agent *********

2012-05-07 09:20:39:039 924 1abc Agent * Include potentially superseded updates

2012-05-07 09:20:39:039 924 1abc Agent * Online = Yes; Ignore download priority = Yes

2012-05-07 09:20:39:039 924 1abc Agent * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"

2012-05-07 09:20:39:039 924 1abc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

2012-05-07 09:20:39:039 924 1abc Agent * Search Scope = {Machine}

2012-05-07 09:20:39:278 924 1abc PT +++++++++++ PT: Synchronizing server updates +++++++++++

2012-05-07 09:20:39:278 924 1abc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://HQSCCM01.MicroTechllc.com:8530/ClientWebService/client.asmx

2012-05-07 09:20:39:285 924 1abc PT WARNING: Cached cookie has expired or new PID is available

2012-05-07 09:20:39:286 924 1abc PT Initializing simple targeting cookie, clientId = 688b5ad1-7986-4e6c-a97a-ae0c0a10a391, target group = Windows 7, DNS name = matkinson-lpt.microtechllc.com

2012-05-07 09:20:39:286 924 1abc PT Server URL = http://HQSCCM01.MicroTechllc.com:8530/SimpleAuthWebService/SimpleAuth.asmx

2012-05-07 09:20:39:289 924 1abc PT WARNING: GetAuthorizationCookie failure, error = 0x80244022, soap client error = 10, soap error code = 0, HTTP status code = 503

2012-05-07 09:20:39:290 924 1abc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244022

2012-05-07 09:20:39:290 924 1abc PT WARNING: PopulateAuthCookies failed: 0x80244022

2012-05-07 09:20:39:290 924 1abc PT WARNING: RefreshCookie failed: 0x80244022

2012-05-07 09:20:39:290 924 1abc PT WARNING: RefreshPTState failed: 0x80244022

2012-05-07 09:20:39:290 924 1abc PT WARNING: Sync of Updates: 0x80244022

2012-05-07 09:20:39:290 924 1abc PT WARNING: SyncServerUpdatesInternal failed: 0x80244022

2012-05-07 09:20:39:290 924 1abc Agent * WARNING: Failed to synchronize, error = 0x80244022

2012-05-07 09:20:39:290 924 1abc Agent * WARNING: Exit code = 0x80244022

2012-05-07 09:20:39:290 924 1abc Agent *********

2012-05-07 09:20:39:290 924 1abc Agent ** END ** Agent: Finding updates [CallerId = CcmExec]

2012-05-07 09:20:39:291 924 1abc Agent *************

2012-05-07 09:20:39:291 924 1abc Agent WARNING: WU client failed Searching for update with error 0x80244022

2012-05-07 09:20:39:297 924 1abc Report REPORT EVENT: {15955890-C614-4895-8491-E07C4EA1B365} 2012-05-07 09:20:34:704-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244022 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244022.

2012-05-07 09:20:39:297 924 1abc Report REPORT EVENT: {7E5220B4-84D3-4762-9655-703B43E2E072} 2012-05-07 09:20:39:290-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244022 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244022.

2012-05-07 09:20:39:303 2860 1fa8 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:20:39:303 2860 1fa8 COMAPI - Updates found = 0

2012-05-07 09:20:39:303 2860 1fa8 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x80244022

2012-05-07 09:20:39:303 2860 1fa8 COMAPI ---------

2012-05-07 09:20:39:303 2860 1fa8 COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:20:39:303 2860 1fa8 COMAPI -------------

2012-05-07 09:20:39:304 2860 1fa8 COMAPI WARNING: Operation failed due to earlier error, hr=80244022

2012-05-07 09:20:39:304 2860 1fa8 COMAPI FATAL: Unable to complete asynchronous search. (hr=80244022)

2012-05-07 09:20:39:305 924 1abc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8

2012-05-07 09:20:39:305 924 1abc Report WER Report sent: 7.5.7601.17514 0x80244022 00000000-0000-0000-0000-000000000000 Scan 101 Managed

2012-05-07 09:20:39:312 924 1abc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8

2012-05-07 09:20:39:312 924 1abc Report WER Report sent: 7.5.7601.17514 0x80244022 00000000-0000-0000-0000-000000000000 Scan 101 Managed

2012-05-07 09:20:39:312 924 1abc Report CWERReporter finishing event handling. (00000000)

2012-05-07 09:23:45:391 2860 19ec COMAPI -------------

2012-05-07 09:23:45:391 2860 19ec COMAPI -- START -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:23:45:391 2860 19ec COMAPI ---------

2012-05-07 09:23:45:393 2860 19ec COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:23:45:393 924 1abc Agent *************

2012-05-07 09:23:45:393 924 1abc Agent ** START ** Agent: Finding updates [CallerId = CcmExec]

2012-05-07 09:23:45:393 924 1abc Agent *********

2012-05-07 09:23:45:393 924 1abc Agent * Include potentially superseded updates

2012-05-07 09:23:45:393 924 1abc Agent * Online = Yes; Ignore download priority = Yes

2012-05-07 09:23:45:393 924 1abc Agent * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"

2012-05-07 09:23:45:393 924 1abc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

2012-05-07 09:23:45:393 924 1abc Agent * Search Scope = {Machine}

2012-05-07 09:23:45:651 924 1abc PT +++++++++++ PT: Synchronizing server updates +++++++++++

2012-05-07 09:23:45:651 924 1abc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://HQSCCM01.MicroTechllc.com:8530/ClientWebService/client.asmx

2012-05-07 09:23:45:662 924 1abc PT WARNING: Cached cookie has expired or new PID is available

2012-05-07 09:23:45:662 924 1abc PT Initializing simple targeting cookie, clientId = 688b5ad1-7986-4e6c-a97a-ae0c0a10a391, target group = Windows 7, DNS name = matkinson-lpt.microtechllc.com

2012-05-07 09:23:45:662 924 1abc PT Server URL = http://HQSCCM01.MicroTechllc.com:8530/SimpleAuthWebService/SimpleAuth.asmx

2012-05-07 09:23:45:667 924 1abc PT WARNING: GetAuthorizationCookie failure, error = 0x80244022, soap client error = 10, soap error code = 0, HTTP status code = 503

2012-05-07 09:23:45:668 924 1abc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244022

2012-05-07 09:23:45:668 924 1abc PT WARNING: PopulateAuthCookies failed: 0x80244022

2012-05-07 09:23:45:668 924 1abc PT WARNING: RefreshCookie failed: 0x80244022

2012-05-07 09:23:45:668 924 1abc PT WARNING: RefreshPTState failed: 0x80244022

2012-05-07 09:23:45:668 924 1abc PT WARNING: Sync of Updates: 0x80244022

2012-05-07 09:23:45:668 924 1abc PT WARNING: SyncServerUpdatesInternal failed: 0x80244022

2012-05-07 09:23:45:668 924 1abc Agent * WARNING: Failed to synchronize, error = 0x80244022

2012-05-07 09:23:45:670 924 1abc Agent * WARNING: Exit code = 0x80244022

2012-05-07 09:23:45:670 924 1abc Agent *********

2012-05-07 09:23:45:670 924 1abc Agent ** END ** Agent: Finding updates [CallerId = CcmExec]

2012-05-07 09:23:45:670 924 1abc Agent *************

2012-05-07 09:23:45:670 924 1abc Agent WARNING: WU client failed Searching for update with error 0x80244022

2012-05-07 09:23:45:683 2860 19ec COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:23:45:683 2860 19ec COMAPI - Updates found = 0

2012-05-07 09:23:45:683 2860 19ec COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x80244022

2012-05-07 09:23:45:683 2860 19ec COMAPI ---------

2012-05-07 09:23:45:683 2860 19ec COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]

2012-05-07 09:23:45:683 2860 19ec COMAPI -------------

2012-05-07 09:23:45:684 2860 19ec COMAPI WARNING: Operation failed due to earlier error, hr=80244022

2012-05-07 09:23:45:684 2860 19ec COMAPI FATAL: Unable to complete asynchronous search. (hr=80244022)

2012-05-07 09:23:50:670 924 1abc Report REPORT EVENT: {DA55621E-39D6-4790-882A-DB78699F50D0} 2012-05-07 09:23:45:669-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244022 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244022.

2012-05-07 09:23:50:677 924 1abc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8

2012-05-07 09:23:50:677 924 1abc Report WER Report sent: 7.5.7601.17514 0x80244022 00000000-0000-0000-0000-000000000000 Scan 101 Managed

2012-05-07 09:23:50:677 924 1abc Report CWERReporter finishing event handling. (00000000)

2012-05-07 09:24:47:300 924 1abc PT WARNING: Cached cookie has expired or new PID is available

2012-05-07 09:24:47:301 924 1abc PT Initializing simple targeting cookie, clientId = 688b5ad1-7986-4e6c-a97a-ae0c0a10a391, target group = Windows 7, DNS name = matkinson-lpt.microtechllc.com

2012-05-07 09:24:47:301 924 1abc PT Server URL = http://HQSCCM01.MicroTechllc.com:8530/SimpleAuthWebService/SimpleAuth.asmx

2012-05-07 09:24:47:308 924 1abc PT WARNING: GetAuthorizationCookie failure, error = 0x80244022, soap client error = 10, soap error code = 0, HTTP status code = 503

2012-05-07 09:24:47:309 924 1abc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244022

2012-05-07 09:24:47:309 924 1abc PT WARNING: PopulateAuthCookies failed: 0x80244022

2012-05-07 09:24:47:309 924 1abc PT WARNING: RefreshCookie failed: 0x80244022

2012-05-07 09:24:47:309 924 1abc PT WARNING: RefreshPTState failed: 0x80244022

2012-05-07 09:24:47:309 924 1abc PT WARNING: PTError: 0x80244022

2012-05-07 09:24:47:309 924 1abc Report WARNING: Reporter failed to upload events with hr = 80244022.

2012-05-07 09:27:01:584 924 1398 AU AU received policy change subscription event

Share this post


Link to post
Share on other sites

I've been racking my brain as to why our Windows 7 Updates weren't being installed and I think I have just sorted it - I followed the above a good few times, but only now did I notice that one of your pictures appears to be of the wrong thing - I was trying to deploy the 'Windows 7 Updates' beneath the 'All Software Updates' folder, but this did nothing on clients, nothing ever got installed.

 

I ran through again this afternoon and this time I checked your written explaination - I deployed the 'Windows 7 Updates' beneath 'Software Update Groups' and it prompted me to accept or decline any software requiring me to accept a licence agreement which I don't recall from before. Alongside this, the 'Software Update Group' was previously always listed as the name of an actual update (ActiveX Killibits for me), whereas doing it now showed it correctly as 'Windows 7 Updates'.

 

Fingers crossed it will now deploy the updates correctly, it was beginning to bug me why it wasn't working! It is still downloading the updates but I will report back once things work (or not!)! This is quite possibly why no updates appeared to be installed during the PXE deployment and why none were listed in Add/Remove Programs > Show Windows Updates.

Share this post


Link to post
Share on other sites

computers that need updates which you make available to your organization are not compliant, computers that have all available updates installed are compliant,

speaking of compliance, if you want to see what updates a computer needs then you could drill through the software update compliance reports and work out what it needs, but be prepared to take your time..

Share this post


Link to post
Share on other sites

I currently use WSUS to deploy updates and have the servers and settings set with group policy. I'm starting to test the method with SCCM. What do I need to change in my group policy so that it uses my SCCM servers for updates instead of WSUS? I don't want to undo all the settings since I don't want my clients going to Microsoft for updates, nor do I want them being notified of them before I approve the updates.

 

How do I do this?

Share this post


Link to post
Share on other sites

computers that need updates which you make available to your organization are not compliant, computers that have all available updates installed are compliant,

speaking of compliance, if you want to see what updates a computer needs then you could drill through the software update compliance reports and work out what it needs, but be prepared to take your time..

 

Thanks. Is there a report that I can run that shows how many approved updates each computer needs? I.E. List each computer and the number of needed updates next to it.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.