locked
DCOM Errors on Imaged PC with Forefront Client Security-Duplicate Susclientid as well. RRS feed

  • Question

  • Here goes...

    Created image with FCS /nomom and have it in production (remote site).

    PC was staged and joined to domain.

    Observations:

    1. PC isn't showing up in WSUS.

    2. PC is also not defaulting to the "unassigned" group in WSUS.  FCS is getting updated even though I didn't add it to the approved group for automatic FCS Definition Updates.

     

     Could this be a corrupt image that has a susclient id already?  An image of a system that was altready introduced to WSUS and the Custom Group in WSUS for automatic updates?

    Any idea what would be causing this DCOM Error? 

    Event Type: Error
    Event Source: DCOM
    Event Category: None
    Event ID: 10005
    Date:  1/13/2012
    Time:  8:43:12 AM
    User:  NT AUTHORITY\SYSTEM
    Computer: 00123456
    Description:
    DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service IISADMIN with arguments "" in order to run the server:
    {A9E69610-B80D-11D0-B9B9-00A0C922E750}

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Any feedback is appreciated.

    Thanks!

    Friday, January 13, 2012 4:01 PM

Answers

  • Hi,

    It seems your FCS client got update from internet. Well, you can start to troubleshoot WSUS issue by looking on GPO, using wsusclientdiag, ... and I suggest you open a thread on Technet WSUS forum http://social.technet.microsoft.com/Forums/en/winserverwsus/threads because it is not an FCS problem.


    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1
    • Marked as answer by Rick Tan Wednesday, January 18, 2012 8:35 AM
    Friday, January 13, 2012 10:51 PM

All replies

  • Hi,

    It seems your FCS client got update from internet. Well, you can start to troubleshoot WSUS issue by looking on GPO, using wsusclientdiag, ... and I suggest you open a thread on Technet WSUS forum http://social.technet.microsoft.com/Forums/en/winserverwsus/threads because it is not an FCS problem.


    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1
    • Marked as answer by Rick Tan Wednesday, January 18, 2012 8:35 AM
    Friday, January 13, 2012 10:51 PM
  • Thank you Bechir!  Will do.

    For odd reasons, I associate DCOM with MOM 2005 Agent.

    Regards-

    Andrew

     

     

    Wednesday, January 18, 2012 8:04 PM