Comments
 
posted on September 2nd 2015, at 16:29
by lunarg
If you notice that SCOM is not properly discovering services on a particular server (e.g. it does not detect the presence of Exchange), you can resolve this by clearing the cache of the agent on the server. This will trigger a new full discovery, and the agent should now be able to detect the new services:

Log on the server of which services are not discovered properly.

Stop the agent (System Center Management service): net stop HealthService



Delete the contents of the Health Service State folder, located in the installation folder of the agent.
(default location: %PROGRAMFILES%\System Center Operations Manager\Agent).

Start the agent again (System Center Management service): net start  ...
Add a new comment
 
Your name:
Your e-mail:
Your comment:
 
Basic BBcode is supported.
Captcha:
Type the letters and numbers as shown.
/get/captcha/1732407008
Not readable? Get another.
 
 
 
 
« November 2024»
SunMonTueWedThuFriSat
     12
3456789
10111213141516
17181920212223
24252627282930
 
Links
 
Quote
« Most people tend to avoid true conflict. Ironically this breeds more conflict. »