It may sound silly, but this MP requires a bit of configuration to work properly. Let’s go for the steps:
0. Make sure your SCSM server is added to SCOM. See details here. Make sure the servers have the Agent Proxy enabled.
1. Download it from here: http://www.microsoft.com/en-ca/download/details.aspx?id=41136
2.Read the whole guide!
3.Import Library MP
4.Configure Run As Account
As per the deployment guide, this profile needs to be populated:
This profile is used to access the Service Manager databases and the staging and configuration DWStagingAndConfig databases.
Let’s add a run as account for this purpose:
Guide says the account has the requirements below:
I think I could go with my SCSM Service account for that.
UPDATE: after I’ve configured it all, I had to actually add specific rights to registry keys, as the guide states and make my run as account a sysadmin in both SQL instances (MS and DW server).
I like it more secure:
Make sure you distribute it to all the servers:
If you want, you can create an specific account for that. Just make sure you follow the guide to configure the right permissions.
Also, make sure all firewall requirements are there, since this is an Agentless Management pack…yes, I know. It seems that even though the SCOM agents have no issues running on the servers, MS didn’t bother to change the MP:
Any firewall and routing are configured to support monitoring of the Service Manager management server from the designated proxy system. Access to the Service Manager and data warehouse databases must be possible because it is required by the proxy agent in one of the monitoring scenarios.
· The Windows Management Instrumentation (WMI) service is running on the proxy agent and on all Service Manager management servers that you want to monitor.
· The proxy system is able to establish a remote WMI connection to all Service Manager management servers. By default, this is possible if the service account that is used for proxy monitoring has administrative privileges on the Service Manager management servers.
· The account that is used for the Database Run As Profile also has these same privileges; therefore, it can access registry keys remotely from the proxy agents.
After a few minutes, it seems that I have data coming in:
(By the way, you won’t find any views yet, since they have been defined in the Monitoring MP, so, go for the Discovered Inventory view.)
And look at that! It seems I’ve been neglecting my DW server:
Let’s try starting the Service!
Service is up, but it seems I will get some grief for a while:
But it will all be good in the end!
Hope this helps!