In Configuration Manager 2012 you can have multiple SMS Providers to achieve a higher availability and load balancing. This is a really great new feature!
I ran into this little challenge yesterday, when we moved the SQL database to a SQL Cluster and installed a second SMS Provider in the site to achieve high availability. We installed the ADK as it is a documented pre-req on Technet for the SMS Provider role.
When the Admin console connected using the newly installed SMS Provider we got this error as soon as you try to edit a Task Sequence which uses the MDT integration:
We resolved this by installing the same version of MDT as we use on the Primary Site server on the server with the newly added SMS Provider role installed on it and ran the “Configure MDT Integration” utility on that server as well.
After that all the errors are gone and the newly installed SMS Provides works just fine even when editing Task Sequences with the MDT integration installed.
1 thought on “Multiple SMS Providers and MDT integration error”
Great tip, Jørgen.
It seems that running the “Configure ConfigMgr integration” with the option “Add the MDT task seqiuence…” REQUIRES that the SCCM console is installed. So if your SMS provider server does not have the console installed, you can:
1. Install MDT on the SMS provider server.
2. Configure with “Install the MDT extensions for Configuration Manager” selected (and nothing else selected)
3. On a server with the SCCM console and MDT installed, run the Configuration program again, select “Install the MDT extensions for Configuration Manager” and “Add the MDT task sequence…” – and then select the remote SMS provider as the “Site server name”.
The MDT guys are probably working with a default installation of SCCM where the Site server is also the SMS provider, therefore this confusion, perhaps.
Also I’m not sure if step 2. is needed. However, I works in my case.