Monday, November 5, 2012

How to install a multiple SMS Provider in ConfigMgr 2012

In ConfigMgr the SMS Provider is installed during installation. The SMS Provider is the interface between the ConfigMgr console and the Site database. In ConfigMgr 2007 there can be only one SMS Provider installed per ConfigMgr Site. In ConfigMgr 2012 however multiple installations of the SMS Provider are supported. Just remember: It cannot be installed on a clustered SQL server database server or on the same computer as the SMS Provider for another site.

For example: ConfigMgr 2012 is installed already and the SMS Provider is installed on your Primary Site server. Now you want to install another one on your SQL server, which isn't installed on a clustered SQL server database server. Here are the steps which must be followed:

1) Open the Start Menu on the ConfigMgr server and select Microsoft System Center 2012 > Configuration Manager > Configuration Manager Setup
2) Getting Started > Select "Perform site maintenance or reset this Site" and click Next
3) Site Maintenance > Select "Modify SMS Provider configuration" and click Next
4) Manage SMS Providers > Select "Add a new SMS provider" and "Enter the FQDN of the server where the SMS Provider is to be installed" and click Next
5) Configuration > After a few minutes the SMS Provider will be installed on another server

Good news that the SMS Provider can be installed multiple times now, and isn't a Single-point-of-failure anymore! With above steps multiple SMS Providers can be installed or uninstalled. Just choose to divide ConfigMgr roles also to have a High Available ConfigMgr environment.
Good luck with your installation!


  1. Hello, I installed the SMS provider role on one of my Management Server but I cannot connect to it using the admin console from a desktop or locally from a MS.

    the error is listed below:

    Transport error; failed to connect, message: 'Provider machine not found
    Parameter name: configMgrServerPath'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nProvider machine not found
    Parameter name: configMgrServerPath\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
    at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nProvider machine not found
    Parameter name: configMgrServerPath
    \r\nSystem.ArgumentOutOfRangeException\r\nProvider machine not found
    Parameter name: configMgrServerPath\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)\r\n

    1. Mostly, such problem is caused by ConfigMgr console could not connect to the ConfigMgr site database. Please verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console" (

  2. Hello,

    Thank you for your post. I tried to install a new provider for my CAS, but when I wanted to connect to the new provider with the console I have the same issue of the comment before. I verified the rights of DCOM, all it's OK.
    Can you tell me if we need some prerequisites for installing it? I tried to install it on a Windows 2008R2SP1 with ADK. Do we need something else?
    Thank you for your response and sorry for my english.


    1. Hello, tried myself to install another provider last week also. Same error message as you guys. Seems you cannot install another provider on a second server and connect through that one to the database. Kind of useless then when you ask me.. Maybe a bug?

    2. Thank you Henk for your feedback. I'll ask MS support.


    3. Hi Zak

      did you got any solution from MS if yes please share i am facing the same issue


    4. Did you ever sort this out? I'm having the same problem.

    5. Did not tried it another time. Maybe it's fixed in an Cumulative Update already?

  3. I confirmed with Microsoft techs, this behavior is by design. The multiple SMS providers are created to provide "Load balncing" NOT fault tolerance. At my current client site, it's working as expected, console connects arbitrarily to either SMS provider.
    Hope this helps.

    1. Kapil, how did you verify that it is working as expected? I can't seem to find a log or any detail that might help us work out if the second provider is working successfully.