(Please note!! All changes to your servers is done at your own risk. If you are in doubt about any changes, then please contact us, so that we can assist you).
It is critical that your data are as new and accurate as possible, and therefore it is important that the column Full update in the status webpart is green.
In the below picture, you can see and example, where 3 out of 4 servers are not green, and therefore you have a potential problem when it comes to collecting data.
Click on the red icon for each server and try to figure out what types of data that are not collected.
As you might see, then the data FactosServices are not collected within the required timeframe, and now it is important to ask the question:
- Is it only one of the WMI counters that are not collected or is it all WMI counters that are not collected.
If it is all, then there are two possibilities, either you have not setup the system correct or you might have a firewall issue. In that case, then click on this link.
If it is only ONE or few counters, then in general the WMI setup is done correct, but you are in a situation, where you need to allow the SQL Powerhouse Windows service to capture WMI remotely. This is described below.
STEP 1: Find the SID for Service account
First you must find the SID for the service account running SQL Powerhosue, and that is done by going to the server where Windows SQL powerhouse server is installed--> go to Services and find the service named: SQL Powerhouse.
Note the name of the service account, and then (on the same server) start a command console with administrative rights.
Write the following command
wmic useraccount where name='xxxx'
Replace the xxxx with the name of the service account.
(1 is the command and 2 is the SID. SID starts with S-1-5-21 in this example).
STEP 2: Change security
Now you have the SID of the service account, and then you can logon to the server that does not collect all WMI. in a command prompt with elevated security you can now write:
c:\windows\system32\sc sdshow SCMANAGER
The result looks like this
(1 is the command, 2 is the result in this example)
Copy the result to notepad, and add
where xxxx is the SID of the service account.
The first line D:(xxxx is the result from my command, and you need to grant access to the service account to allow remote procedurecalls. NOTE!! THE SID I HAVE ADDED IS JUST AN EXAMPLE.
The result that you are going to use in the next step is the last two lines (BUT FROM YOUR SYSTEM. THEY MIGHT BE DIFFERENT ON YOUR SYSTEM. THE IDEA IS: USE THE ORIGINAL STRING + THE LINE YOU HAVE ADDED).
Now i a command prompt write:
SC sdset SCMANAGER xxx
where xxx is the new string you have created (including the original string). It looks like this
You should see the word SUCCESS if you have changed security correctly.
Do that on all servers that you are monitoring, where you have problems collecting WMI data.
NOTE the word SCManager might need to be changed depending on what WMI you have problem with. Below is a schema showing what to replace the word SCManager with:
|What to collect||Replace SCManager With|
|FactOS_Services||SCMANANGER (don't change)|
STEP 3: TEST SECURITY
On the server where SQL Powerhouse Service is installed, click Run and write wbemtest.
Start the program as the SQL Powerhouse service account:
Click Connect, and in the Namespace enter the \\server\root\cimv2. click Connect.
You should now have the following Screenshot:
1=The server and namespace.
If 1 is ok, then Click 2 (Query), and write one of the following queries
|What to collect||Query|
|FactOS_Services||Select * from win32_service|
If you get a screen like the one below, and no error messages, then WMI is now working for that server. Proceed to other servers that you collect data from.
A note about clusters
All the above must be done on all nodes in a cluster.