Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Multiple SMS Providers and MDT integration error

Posted on April 19, 2013April 19, 2013 by Jörgen Nilsson

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:

Multiple_SMS_ProvWe 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.

Multiple_SMS_Prov_2
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”

  1. Bjorn Henrik Formo says:
    December 18, 2013 at 1:31 pm

    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.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
All code is provided "AS-IS" with no warranties.

Tweets by ccmexec

Recent Posts

  • Windows Servicing, Personal Teams and Success.cmd
  • Windows MDM Security Baseline – Settings Catalog
  • Configuring MS Edge Security Baseline v107 using Settings Catalog
  • Configuring Desktop App Installer using CSP and script?!
  • Customizing Taskbar and Start in Windows 11 22h2 with PowerShell

©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT