Jump to content


  • 0
SteFau

Odd agent behavior post patch installation

Question

Good morning everyone,

 

I am looking for help on an issue we encountered this weekend while patch our production environment, and I am hoping you guys can help by pointing me in the right direction. So, we have an SCCM 2007 SP2 R3 environment that we use to patch our Windows 2008R2 SP1 servers. Last friday evening, we scheduled the deployment of all of the February 2013 Critical Patches and Security Updates for Windows Server 2008. When I logged my SCCM server Saturday morning, I check my Overall Compliancy, and for some reason, I only have about 75 servers compliant out of 130. So next step, I choose one of the servers that are non compliant to investigate further. Start looking at the logs around 10:30PM which was my deadline for the patches. All is good, I see that they started as expected. At around 10:45PM, this is where it starts getting funky.

 

Here's an excerpt of what a few of my logs give me:

ExecMgr.log:

Execution is complete for program Software Updates Program. The exit code is 0, the execution status is Success execmgr 2/22/2013 10:43:58 PM 29864 (0x74A8)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 80004005 execmgr 2/22/2013 10:44:50 PM 8052 (0x1F74)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 80004005 execmgr 2/22/2013 10:44:50 PM 8052 (0x1F74)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 80004005 execmgr 2/22/2013 10:44:50 PM 8052 (0x1F74)
Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x80004005 execmgr 2/22/2013 10:44:50 PM 8052
(0x1F74)

CExecutionManager::Execution Manager received a SERVICEWINDOWEVENT END Event execmgr 2/22/2013 10:44:50 PM 59312 (0xE7B0)
CExecutionRequestManager::Received a Service Window Notification that it need not handle. execmgr 2/22/2013 10:44:50 PM 59312 (0xE7B0)
Software Distribution Site Settings for the client are missing from WMI. execmgr 2/23/2013 10:24:22 AM 18204 (0x471C)

 

UpdatesDeployment:

All required updates only require a reboot. UpdatesDeploymentAgent 2/22/2013 10:43:59 PM 29864 (0x74A8)
Assignment ({640C194F-CAED-4E37-8602-C091D55D33E0}) - only pending a reboot UpdatesDeploymentAgent 2/22/2013 10:43:59 PM 29864 (0x74A8)
No pending install assignment UpdatesDeploymentAgent 2/22/2013 10:43:59 PM 29864 (0x74A8)
No installations in pipeline, notify reboot. UpdatesDeploymentAgent 2/22/2013 10:43:59 PM 29864 (0x74A8)
Notify reboot with deadline = Friday, Feb 22, 2013. - 22:43:59, Ignore reboot Window = False UpdatesDeploymentAgent 2/22/2013 10:43:59 PM 29864 (0x74A8)
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT END Event UpdatesDeploymentAgent 2/22/2013 10:44:50 PM 27712 (0x6C40)
Service shutdown system task UpdatesDeploymentAgent 2/22/2013 10:44:50 PM 8052 (0x1F74)

 

This one looks normal.

RebootCoordinator.log:

Scheduled reboot from agent UpdatesDeploymentAgent RebootCoordinator 2/22/2013 10:43:59 PM 29864 (0x74A8)
System reboot request succeeded. RebootCoordinator 2/22/2013 10:44:02 PM 29864 (0x74A8)
Reboot initiated RebootCoordinator 2/22/2013 10:44:02 PM 29864 (0x74A8)

 

Ok good, my server rebooted as expected.

 

So, basically, the weird error I get is the Software Distribution Site Settings for the client are missing from WMI from my ExecMgr.log. So my next course of action is to use a third party tool Collection Commander to trigger a Software Updates on all the servers from my collection.

A BUNCH of the servers just give me a "Not Found" message when attempting this. Same thing when I tried to connect using Client Center.

At this point, I triggered an Install Client w/ Repair on the entire collection followed by a VBS Script to enforce software compliancy, and sure enough, my compliancy started to go up. This monday morning, only 6 servers are non compliant.

 

So my question to you guys is this: WHAT or WHY did almost half of my SCCM clients get corrupted after software updates installations? Where can I look for an exaplanation? I am at a loss here!

Thanks for your help and input!!!

 

Added information on February 26th:

I was lucky enough that two servers had been left out of the loop, and we patched them also last night (monday evening). Same problem. This time, I'm not fixing it, but studying them.

Findings so far:
- After rebooting, SCCM agent stopped logging, last entries in my log files are from 10:20PM last night
- This is what my agent looks like:

ZUVhd44.jpggvFaUEM.jpg

- I compared all the Hotfixes that we're installed yesterday and that are common to both servers, here's the list:

O4NhdTC.jpg

 

 

There are also some .Net updates in common, but I'd be very surprised if that had anything to do with it.

 

Any ideas as to what happened and especially why?

Share this post


Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

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

Guest
Answer this question...

×   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.