Troubleshooting
Services
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