Troubleshooting WMI
2 min
After Activate adds a computer to a SCCM collection, it uses WMI to connect to the machine and instruct the SCCM agent to refresh its policy. Several factors can prevent this from working, including firewall rules, WMI security and connectivity issues.
Verifying WMI Execution from Activate
- In the Object Editor for _Parameters window, click Save Object.
- In the Execute Method window, click Execute.
- A confirmation message should display indicating that the method executed successfully.
- On the target system, open: C:\Windows\System32\CCM\Logs\oobmgt.log You should see a new GetProvisioningSetting entry confirming that the policy has been re-evaluated.
Manual WMI Command Using WBEMTest
Use WBEMTest to determine whether issues are due to infrastructure or within Activate.
- Open a command prompt and run: wbemtest
- When the Windows Management Instrumentation Tester opens, click Connect.
- In the Namespace field, enter: \\<targetClientName>\root\ccm Then click Connect.
- After connecting successfully, click Execute Method.
- In the Get Object Path window, enter: sms_client and click OK.
- In the Execute Method window, enter TriggerSchedule in the Method field and click Edit In Parameters.
- In the Object Editor for _Parameters, double-click sScheduleID.
- Click Save Property.
- Enter the following value: {00000000-0000-0000-0000-000000000021} This GUID initiates the SCCM OOB auto-provisioning check.
- In the Property Editor, set the value to Not NULL and save your changes.