The problem: EV Management Pack (MP) v10.0.3 is unable to discover EV v10.0.3 standalone servers.
My Enviornmnet Details and setting are as follows:
SCOM 2007 R2
EV Servers: Clustered and non Clustered on Windows 2008 64Bit OS R2 Enterprise
EV Version : 10.0.3
Details:
We are migrated our EV v9.0.4 environment to EV v10.0.3 and would like to use the latest EV MP v10.0.3 for monitoring both environments during/after migration. The latest SCOM MP works fine with EV v9.0.4 infrastructure on Windows Clustered nodes. The problem is with EV v10.0.3 infrastructure on Windows 2008 R2 x64 non-clustered/standalone boxes.
We are confident with all configuration and we are absolutely sure where's a problem. I’ve spent countless time troubleshooting this weird issue.
An issue is with out of the box PowerShell SCOM discovery script, however discovery works perfectly with EV v9 on MS clusters only. The code in the PS script doesn’t contain proper control for non-clustered environment as per below screenshot.
Shortly, it checks for Clustering registry key and fails if it's missing. This key shoudn't be there on standalone servers!
Anyone from Symantec would be able to comment on that? Anyone else has got the same issue on your environments?
Thanks.
