We implemented SCOM 2012 SP1 , We imported the latest Managemnet pack for monitoring Active Directory
Somehow the topology views in AD management pack always remained not monitored.
Here is what i checked :
The agents on DC's was installed from within SCOM console after discovery
We used a domain Administrator to install the agent and then the local system account as action account
the DC's started alerting and we couldn't find any errors in the event logs , however the topology views all remained not Monitored.
AD helper Object was installed on all the domain controllers as the agents were pushed from SCOM Console.
I ran hslockdown /L on the Domain controllers
Local System Account (our default Action account) was not denied permission.
Still i tried running
Hslockdown "ManagemnetGroupName" /A "NT AUTHORITY\SYSTEM"
But the topology views did not update.
-Verified Agent proxy was enabled on all DC's and MS
-All the agents are within the same forest
-Verified the AD topology discovery. It was set to disabled. Removed the override and enabled it for Discover Agents Only
Still nothing populated in the Topology Views.
Reviewed ETL Logs from the Domain controllers and RMS Emulator
- Open a command prompt on the agent and navigate to ‘\Program Files\System Center Operations manager 2007\Tools’ directory.
- Run the command StopTracing.cmd
- Browse through %Windir%\ temp\OpsMgrTrace directory, take backup of all files insight the folder and delete the contents.
- In ‘\Program Files\System Center Operations manager 2007\Tools’ command prompt type “starttracing.cmd VER (The word VER must be in caps)
- Restart the “System Center Management service. Once done wait for 10 Minutes. (Don’t keep this running for more than 10 minutes.)
- Stop the tracing using the command stoptracing.cmd
- Format the ETL files using command formattracing.cmd --- This takes a long while , have Patience
- The default location of these files is C:\WINDOWS\Logs\OpsMgrTrace.
Found that the discovery script runs on the RMS Emulator as:
"C:\Windows\System32\cscript.exe" //nologo "E:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 927\6181\ADTopologyDiscovery.vbs" 0 {588C5951-C337-0B15-9554-C80FC248AB3A} {BB59AB18-76F2-C1CA-DB89-9F31C64863A7} RMSEmulator.domain.com true "C:\Program Files\System Center Operations Manager 2007" 7.0.9538.0 "C:\Windows\system32\windowspowershell\v1.0\powershell.exe" "ManagementGroupName" false
Noticed the path being "C:\Program Files\System Center Operations Manager 2007" however in our case we installed SCOM 2012 SP1 on E:
We set the following override for OpsMgrInstallPath
"E:\Program Files\System Center 2012\Operations Manager\Server"
instead of "C:\Program Files\System Center Operations Manager 2007"
We then restarted the HealthService on management Server and waited,waited, waited , waited , waited
maybe a day or two
It shows monitored now
Hope this helps.
Somehow the topology views in AD management pack always remained not monitored.
Here is what i checked :
The agents on DC's was installed from within SCOM console after discovery
We used a domain Administrator to install the agent and then the local system account as action account
the DC's started alerting and we couldn't find any errors in the event logs , however the topology views all remained not Monitored.
AD helper Object was installed on all the domain controllers as the agents were pushed from SCOM Console.
I ran hslockdown /L on the Domain controllers
Local System Account (our default Action account) was not denied permission.
Still i tried running
Hslockdown "ManagemnetGroupName" /A "NT AUTHORITY\SYSTEM"
But the topology views did not update.
-Verified Agent proxy was enabled on all DC's and MS
-All the agents are within the same forest
-Verified the AD topology discovery. It was set to disabled. Removed the override and enabled it for Discover Agents Only
Still nothing populated in the Topology Views.
Reviewed ETL Logs from the Domain controllers and RMS Emulator
- Open a command prompt on the agent and navigate to ‘\Program Files\System Center Operations manager 2007\Tools’ directory.
- Run the command StopTracing.cmd
- Browse through %Windir%\ temp\OpsMgrTrace directory, take backup of all files insight the folder and delete the contents.
- In ‘\Program Files\System Center Operations manager 2007\Tools’ command prompt type “starttracing.cmd VER (The word VER must be in caps)
- Restart the “System Center Management service. Once done wait for 10 Minutes. (Don’t keep this running for more than 10 minutes.)
- Stop the tracing using the command stoptracing.cmd
- Format the ETL files using command formattracing.cmd --- This takes a long while , have Patience
- The default location of these files is C:\WINDOWS\Logs\OpsMgrTrace.
Found that the discovery script runs on the RMS Emulator as:
"C:\Windows\System32\cscript.exe" //nologo "E:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 927\6181\ADTopologyDiscovery.vbs" 0 {588C5951-C337-0B15-9554-C80FC248AB3A} {BB59AB18-76F2-C1CA-DB89-9F31C64863A7} RMSEmulator.domain.com true "C:\Program Files\System Center Operations Manager 2007" 7.0.9538.0 "C:\Windows\system32\windowspowershell\v1.0\powershell.exe" "ManagementGroupName" false
Noticed the path being "C:\Program Files\System Center Operations Manager 2007" however in our case we installed SCOM 2012 SP1 on E:
We set the following override for OpsMgrInstallPath
"E:\Program Files\System Center 2012\Operations Manager\Server"
instead of "C:\Program Files\System Center Operations Manager 2007"
We then restarted the HealthService on management Server and waited,waited, waited , waited , waited
maybe a day or two
It shows monitored now
Hope this helps.
Comments
Post a Comment