When deploying or updating agents the EMWMigration.log reports issues when connecting via WMI.
What can be done?
QMM uses WMI to establish connectivity to agent hosts.
The errors could be: Cannot connect to 'SERVERNAME' using WMI.
In order for this to work the WMI service needs to be enabled and started on the affected machine. If the service is enabled and is started then granting permissions or rebooting often resolves the problem.
Possible ways to troubleshoot WMI issues or errors:
1. using Wmimgmt.msc
Go to Start - Run - and type wmimgmt.msc
When the console opens use the right mouse menu - Connect to another computer - Another computer - and type the name of the server.
After it connects use the right mouse menu again and select Properties, it should display the properties without any errors.
2. Using the attached script (please rename to VBS)
The script is performing exactly the same calls as the QMM console.
In the script body modify and replace the following values
If everything is working properly then there will be no errors and the script will show the OS of the “accessed” computer. If connection fails then the script will produce an error, similar to the error logged by the QMM console in the EMWMigration.log
3. using Wbemtest.exe(Advanced!)
Note: before continuing, please heed the warning at the link below: The word Tester in the title of this opening dialog should serve as a "warning" even to GUI gurus. Wbemtest was not designed for mere mortals or even savvy system admin scripters. It was designed as a tool for testing the functionality of the WMI COM API. The result is that: 1) wbemtest enables you to do almost anything with the WMI COM API and 2) the interface is difficult to use even for experts.
Go to Start - Run - and type Wbemtest.exe
The wbemtest.exe tool makes a WMI connect and can query the metabase at the same time. For more information on the wbemtest.exe tool, please see the following Microsoft article titled Scripting Eye for the GUI Guy | WBEM What? at the following link: