System Center Operations Manager 2007 R2 Agent - Service
While rolling out the R2 Agent to a couple thousand servers, there appears to be a couple dozen servers with an anomally. These server agents were upgraded successfully, according to the Operations Console and also report back to their management server as required as far as I can tell. However the Windows service "display name" was not changed from "Ops Mgr Health Service" to "System Center Management". From the surface, I am not aware of any differences between these 24 servers an the others. In fact I have two identical servers in the same site and same applications. But the SCOM Agent service display names are different after the agent upgrade. Is this known bug? And will it cause any other issues? Should this be fixed by the registry, or an Agent repair?
October 26th, 2010 10:19am
This could be a console caching issue. Try running the console with the /CLEARCACHE option. Also, is the verson # of the agent what you expect on these servers?Microsoft Corporation
October 27th, 2010 11:55am
Thanks for the response Dan. It turns out this issue was cause by a system outside of SCOM altogether. Another team was disabling the SCOM agent during a software deployment and they used a registry entry to disable the SCOM service. This Registry entry updated the service description.
October 27th, 2010 12:46pm