Exchange And WMI Testing.
Published on
9,302 Points
Step 1: Check the WMI Service
The quickest way to test the WMI service is to start the WMI Control
snap-in:
a. Start -> Run -> Open: wmimgmt.msc
b. Right Click on "WMI Control (Local)"
c. Select Properties
If the WMI service is configured properly, the control snap-in will connect
to WMI and display the properties dialog. Under the "General" tab you
should see information about the operating system and the version of WMI
Step 2: Check Security
While still in the WMI Control MMC, do the following:
a. Click on the Security tab.
b. Expand Root and highlight Root/MicrosoftExchangeV2. Click the Security
tab. A sample of "good" permissions is:
Administrators - full inherited
Everyone - Inherited
Execute method,Provider Write,Enable account
Local Service - inherited
Execute method,Provider write, Enable account
Network Service - inherited
Execute method,Provider write,Enable account
c. Expand Root\CIMV2\Applications and highlight Exchange. Click the
Security tab.Again - a sample of "good" permissions:
Administrators - full inherited
Everyone - Inherited
Execute method,Provider Write,Enable account
Local Service - inherited
Execute method,Provider write,Enable account
Network Service - inherited
Execute method,Provider write,Enable account
The above permissions are same as Windows 2000 as in Windows 2003 - EXCEPT on Windows 2000 you do not have permissions such as Local Service and Network Service.
Step 3:
To check the WMI Connectivity from your Exchange Server to another server use the following method.
a. Start -> Run -> Open: wmimgmt.msc
b. Right Click on "WMI Control (Local)"
c. Select Connect to another computer
Type in FQDN of the second Exchange Server.
Once done, please perform Step 2.
Step 4: Check Classes and Namespaces Using WBEMTEST.EXE
a. Click Start -> Run and run wbemtest.exe
b. In the WbemtestTester application click the Connect button.
c. In the Namespace field type in: root\cimv2\applications\ex
click the Connect button.
d. Click the Enum Classes... button. Do not enter a superclass name. Click
the Recursive option, and then click OK.
Note there should be 59 objects (Exchange 2003)
Click the Close button when finished.
e. In the Wbemtest Tester application click Connect again.
f. In the Namespace field type in: root\microsoftExchangeV2. Then click the
Connect button.
g. Click the Enum Classes... button. Do not enter a superclass name. Click
the Recursive option, and then click OK.
Note there should be 74 objects (Exchange 2003)
Click the Close button when finished.
The quickest way to test the WMI service is to start the WMI Control
snap-in:
a. Start -> Run -> Open: wmimgmt.msc
b. Right Click on "WMI Control (Local)"
c. Select Properties
If the WMI service is configured properly, the control snap-in will connect
to WMI and display the properties dialog. Under the "General" tab you
should see information about the operating system and the version of WMI
Step 2: Check Security
While still in the WMI Control MMC, do the following:
a. Click on the Security tab.
b. Expand Root and highlight Root/MicrosoftExchangeV2. Click the Security
tab. A sample of "good" permissions is:
Administrators - full inherited
Everyone - Inherited
Execute method,Provider Write,Enable account
Local Service - inherited
Execute method,Provider write, Enable account
Network Service - inherited
Execute method,Provider write,Enable account
c. Expand Root\CIMV2\Applications and highlight Exchange. Click the
Security tab.Again - a sample of "good" permissions:
Administrators - full inherited
Everyone - Inherited
Execute method,Provider Write,Enable account
Local Service - inherited
Execute method,Provider write,Enable account
Network Service - inherited
Execute method,Provider write,Enable account
The above permissions are same as Windows 2000 as in Windows 2003 - EXCEPT on Windows 2000 you do not have permissions such as Local Service and Network Service.
Step 3:
To check the WMI Connectivity from your Exchange Server to another server use the following method.
a. Start -> Run -> Open: wmimgmt.msc
b. Right Click on "WMI Control (Local)"
c. Select Connect to another computer
Type in FQDN of the second Exchange Server.
Once done, please perform Step 2.
Step 4: Check Classes and Namespaces Using WBEMTEST.EXE
a. Click Start -> Run and run wbemtest.exe
b. In the WbemtestTester application click the Connect button.
c. In the Namespace field type in: root\cimv2\applications\ex
click the Connect button.
d. Click the Enum Classes... button. Do not enter a superclass name. Click
the Recursive option, and then click OK.
Note there should be 59 objects (Exchange 2003)
Click the Close button when finished.
e. In the Wbemtest Tester application click Connect again.
f. In the Namespace field type in: root\microsoftExchangeV2. Then click the
Connect button.
g. Click the Enum Classes... button. Do not enter a superclass name. Click
the Recursive option, and then click OK.
Note there should be 74 objects (Exchange 2003)
Click the Close button when finished.
Ask questions about what you read
If you have a question about something within an article, you can receive help directly from the article author. Experts Exchange article authors are available to answer questions and further the discussion.