---
title: Troubleshooting WMI
slug: troubleshooting-wmi
createdAt: 2025-06-11T20:26:21.329Z
---

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

1. In the **Object Editor for \_Parameters** window, click **Save Object**. 
2. In the **Execute Method** window, click **Execute**. 
3. A confirmation message should display indicating that the method executed successfully. 
4. 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.

1. Open a command prompt and run:
    wbemtest 
2. When the Windows Management Instrumentation Tester opens, click **Connect**. 
3. In the **Namespace** field, enter:
   &#x20;\\\\\<targetClientName>\root\ccm
   &#x20;Then click **Connect**.&#x20;
4. After connecting successfully, click **Execute Method**.&#x20;
5. In the **Get Object Path** window, enter:
   &#x20;sms\_client
   &#x20;and click **OK**.&#x20;
6. In the **Execute Method** window, enter **TriggerSchedule** in the **Method** field and click **Edit In Parameters**.&#x20;
7. In the **Object Editor for \_Parameters**, double-click **sScheduleID**.&#x20;
8. Click **Save Property**.&#x20;
9. Enter the following value:
   &#x20;&#x7B;00000000-0000-0000-0000-000000000021}
   &#x20;This GUID initiates the SCCM OOB auto-provisioning check.&#x20;
10. In the **Property Editor**, set the value to **Not NULL** and save your changes.&#x20;