Introduction
This article will present the 6 steps on how to configure WMI on the Windows Server to be able to communicate with the NMIS9 application to be monitored as a node.
STEP 1 - Enabled these services to start automatically on services.msc (server, remote registry, and Windows Management Instrumentation).
Right-click on the Windows symbol then click on the run option.
Image Modified
The run window will pop-up then type service.msc.
Check if the Server service is status running and the startup type is automatic.
Image Added
Check if the Remote Registry service is status running and the startup type is automatic.
Image Added
Check if the Windows Management Instrumentation service is status running and the startup type is automatic.
Image Added
OBSERVATION: If these services are not running. You need to right-click on the service and then click on Start.
Image Added
After you click Start it will Load the service.
Image Added
If the Startup type is not selected Automatic you can right-click and then Properties.
Image Added
On the Startup Type, this is a drop-down. Select Automatic.
Image Added
STEP 2 - Enabled Distributed COM - DCOM for Windows Server
Right-click on the Windows symbol then click on the run option. The run window will pop-up then type dcomcnfg.
Image Added
Go to My Computer then right-click select Properties.
Image Added
On My Computer Properties go to the Default Properties tab, Check the box Enable Distributed COM on this computer, on the Default Authentication Level: Connect, and on Default Impersonation Level: Identity. After your selected, all these options, click on the OK button for the changes to take effect.
Image Added
STEP 3 - Configuring DCOM communication for Windows Server
Sames steps as Step 2, But now you will select the Default Protocols tab. It needs to be listed as Connection-oriented TCP/IP.
Image Added
If it is not list it. Click on the Add button then selected the Connection-oriented TCP/IP option.
Image Added
STEP 4 - Configuring User Accounts for DCOM on Windows Server
Sames steps as Step 2, But now you will select the COM tab.
On the Access Permission part, select the Edit Default button.
Image Added
On the user's permission configure the Local Access and Remote Access to Allow.
Image Added
On the Launch and Activation Permissions part, select the Edit Default button.
Image Added
On the user's permission configure the Local Launch, Remote Launch, Local Activation, and Remote Activation to Allow.
Image Added
STEP 5 - Configuring Firewall on Windows Server
Right-click on the Windows symbol then click on the run option. The run window will pop-up then type wf.msc.
OBSERVATION: The firewall is located between your NMIS9 application and the Windows Server. So, you need to configure the firewall as an exception to permit DCOM communications.
Image Added
We need to create one Inbound Rule to allow communication between the Windows Server and the NMIS9 application. So, right-click on Inbound Rules and then the New Rule option.
Image Added
Select Custom and click the Next button.
Image Added
Select All programs, and click the Next button.
Image Added
On the Protocol Type drop-down list, select TCP, and the Next button.
Image Added
On Which remote IP Addresses does this rule apply, select these IP Addresses, and click on Add button. On the IP Address, on the pop-up window select this IP address or subnet. Then, click the OK button and the Next button.
Image Added
Select Allow the connection, and click the Next button.
Image Added
Select one or more rules that the new rule applied, and click the Next button. If no objection selects all of them.
Image Added
Now give the rule a name and click on the Finish button.
Image Added
That will be the result of the WMI_Inbound_rule.
Image Added
OBSERVATION: NOT REQUIRED. If you would like to test the WMI from a remote site for instance from the NMIS9 Server using the Windows application wbemtest.
You will need to create one similar Outbound Rule on the Firewall.
Image Added
STEP 6 - Configuring WMI User Access for Windows Server
Right-click on the Windows symbol then click on the run option. The run window will pop-up then type wmimgmt.msc.
Image Added
Right-click on WMI Control(Local) then the Properties option.
Image Added
On the WMI Control (Local) Properties select the Security tab, click on the CIMV2 folder then click the Security button.
Image Added
Select the User that will give access to (Administrator) then Execute Methods, Provider Write, Enable Account, and Remote Enable to Allow.
Image Added
{"serverDuration": 549, "requestCorrelationId": "842de67cac204ade80ea78d0ac1ba0df"}