Remotely Determine the SMS Provider Using WBEMTest

In this blog post, I will show you the steps to use in order to locate the SMS provider manually. From time to time, one of the questions we hear is: How can I determine what my SMS_provider path/name is? This is important to know because if you do any System Center Configuration Manager 2012 / 2007 or even SMS 2003 automation with VBS or PowerShell (PoSH), you need to know what the provider path/name is for each site. This information can be queried within the SYDI-SCCM script to determine what the full provider path is on a site server. I don’t need to tell you that knowing how to remotely determine this information is very useful when it comes to troubleshooting.

How to Remotely Determine the SMS Provider Using WBEMTest - Windows Management Instrumentation Tester

Click on the Connect… button.

Namespace

In the Namespace text box type \\<servername>\root\sms. In my example, the server is called cm12-cm4.

Next, click Connect.

How to Remotely Determine the SMS Provider Using WBEMTest - Enum Classes

Click on the Enum Classes… button.

Locate Namespace

Locate __NAMESPACE and double-click on it.

Instances

Click on Instances.

Query Result - SMS Provider Name

Here we see that the SMS provider name is site_CM4. This tells us that our full SMS provider path is \\cm12-cm4\root\sms\site_CM4. Now we can use this information to query our site server for all sorts of details.

If you have any questions about the steps in this blog post, please contact me @GarthMJ. Or, you can leave a note in the comment section below.

Remotely Determine the SMS Provider Using WBEMTest
Comments
pingbacks / trackbacks

Leave a Comment

Gaelic Glen Show
Share via
Copy link