Last week I updated my SCOM environment to CU4 following the Steps in Kevin Holman's "and my experiences" article. Approving and updating the Agents and a reboot: One Domain Controller (VMWare) in our environment goes "Tango Uniform" shortly after the agents coming back up. The domain controller is pingable but many domain services are unavaliable. The DC's console is blacked out through terminal services;Through VCenter the console is Greyed out. You cannot log into the domain controller. The only solution is to power off and disable the System Center Management services. The SCOM console; while this is going on is reporting: Could not determine the FSMO role holder: AD Replication Partner Op Master Consistency : Unable to determine domain naming Op Master on domain controller 'srvmdc02'. Failed to ping or bind to the Infrastructure Master FSMO role holder:AD Op Master Response : Failed to bind to Infrastructure Op Master 'srvmdc.domain.com' (10.192.6.100). DC has failed to synchronize its naming context with replication partners:Failed DC FQDN:Failed NamingContext DN - SRVMDC02.domain.com:CN=Schema,CN=Configuration,DC=domain,DC=com Failed Accessing Windows Event Log:The Windows Event Log Provider was unable to open the Microsoft-Windows-Dhcp-Server/FilterNotifications event log on computer 'SRVMDC02.domain.com' for reading. The provider will retry opening the log every 30 seconds. Thread in directory is waiting for remote procedure call:A thread in Active Directory is waiting for the completion of a RPC made to the following domain controller. Domain controller: af1f05d9-d1cb-4880-a1b7-1c9969740201._msdcs.domain.com As you can see things get pretty ugly by this point. Our voicemail system loses connection with exchange because it cannot quuery the Global Catalog that is has a connection with; our instant messaging server stops working; We cannot creat new mailboxes.... The Sky starts falling... Hells breaks loose.. etc My first thought is to remove the Agent and re-install it. however we are in a Quarter end freeze at the moment. Anyone Seen this?

i can't really make a connection from AD problems to scom. The alerts just seem to be normal when a DC is not functional. But if you think it's because of a cu4 update i'd definitely make create a case with MS.Rob Korving http://jama00.wordpress.com/

I will open a case. Just thought I would post it here to see if anyone has experienced this before.