After installing MDT 2008, you can then integrate it with ConfigMgr by running the Configure ConfigMgr Integration wizard.
In doing this, I uncovered an issue where if the ConfigMgr SMS Provider is NOT installed on the site server, the wizard will error-out. A hint to the root cause of the problem has a RED rectangle around it in the screen-capture below:
The problem is that the wizard is searching the site server’s WMI repository for the SMS Provider namespace (e.g. root\sms\site_<sitecode>). The screen-capture below gives some examples of the SMS Provider namespace.
In my ConfigMgr site, the SMS Provider is located/installed on the remote SQL Server. There are a few apps I’ve worked with that “integrate” with ConfigMgr (and SMS), but assume that the SMS Provider is also installed locally on the site server. There may be valid reasons why this practice is done, but as we saw in the first screen-capture, it doesn’t work all the time.
By default when you start the Configure ConfigMgr Integration wizard (if MDT was installed on the site server as most do), the wizard will automatically detect the Site server name and Site code. If you installed MDT somewhere other than the site server, the Site server name and Site code textboxes will be blank and you would have to type them in.
We saw above what happens when the site server name is typed in the textbox and the SMS Provider is not installed on the site server.
So how do you get around this issue?
WORKAROUND: So in my situation with the SMS Provider NOT being installed on the site server, but on the remote SQL Server, I would type the remote SQL Server’s name (e.g. NMSQL02). If you installed the SMS Provider on a site system server other than the remote SQL Server, then type-in that server’s name. The site code would be site code for the site where MDT is being installed.
Most admins install the SMS Provider locally on the site server, and would not encounter this issue. However in large site installations where you often see the site database hosted on a remote SQL Server, you are more likely to encounter this issue.
Troy L. Martin | Senior Consultant | 1E |
troy.martin@1e.com | www.1e.com
Read the complete post at http://www.1e.com/1EBlogs/post/2009/07/08/MDT-2008-Error-occurred-integrating-with-ConfigMgr.aspx