Within an MTD role there is an option to define ConfigMgr Packages in the same way that Applications can be added to a role. In the MDT forum I was told that it is impossible to install a ConfigMgr package during an MDT task sequence. My question then is why is there an option to add ConfigMgr packages to a role if it isn't supported? My thought is that if the ConfigMgr client was installed at the time the packages were called to install in the TS then that would be a very handy feature in environments that use MDT for deployment and SCCM to deploy packages. Scanning the source code of ZTIPackages.WSF in the Scripts folder from MDT, it looks like this script is set up specifically to install packages -- when I try running the script in a test environment I always get "Unable to find OSDSWDEXEC.EXE, so SMS packages cannot be installed". This makes sense since I know this EXE doesn't exist in SCRIPTS, TOOLS, SERVICING or anyplace else in my MDT environment. I'm new to SCCM but I understand MDT quite well so any pointers would be greatly appreciated.

Because MDT when installed into a ConfigMgr environment it is supplemental to the capabilities of ConfigMgr OSD thus you are actualy just passing the work onto ConfigMgr. MDT itself is completely ignorant of ConfigMgr and thus when it is in stand-alone mode, does not know how to interact with ConfigMgr at all. Also note that the person who informed you of MDTs inability to perform your request is actually responsible for most of MDT including much of the actual coding and design. Thus, although technically anything is possible with enough coding and knowledge, his answer is pretty authoritative. If you want to leverage ConfigMgr, why not actually leverage it and use OSD (with MDT integrated)? This is how it was designed.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Jason, thanks for the reply. How does one leverage a role within ConfigMgr? I understand that ConfigMgr leverages MDT for certain functions, but my understanding was that ConfigMgr didn't utilized roles since that is a function of the MDT database. Thanks

MDT can sit on top of the ConfigMgr OSD functionality. Essentially, MDT will build ConfigMgr task sequences that can utilize the additional functionality found in MDT. These ConfigMgr based task sequences do many of the same things that the MDT task sequences do, including querying the MDT DB; they are just running in the context of ConfigMgr instead of stand-alone MDT and can thus take advatage of ConfigMgr specific functinality like deploying ConfigMgr packages.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Jason, I was told by a Dell consultant who designed our MTD and SCCM environments for our upcoming Windows 7 deployment and migration that if I went with SCCM that the database goes out the window. Onto the scrap heap. Our DB setup is pretty complex and I'm just trying to determine whether SCCM will do everything our current MDT arrangement will do now -- if I can still leverage the DB it would save us very much time and energy. Maybe I have it set up incorrectly. I did the Configure ConfigMgr Integration step and that was a success. I can create task sequences and create boot media etc. Should I be seeing something about the DB in the ConfigMgr console, or are you saying I would manage the DB via the MDT console the same way I always have? are you saying that I can create a TS using ConfigMgr and put in the Bootstrap.ini and CustomSettings.ini those statements that I use for MDT to connect to the DB, then when I run the Gather step it will pull in all the environment variables I have set up in my DB? I can provide my Bootstrap.ini and CustomSettings.INI if that will help understand our current setup. Thanks again for your patience and replies.

First, I won't make any editorial comments, but that statement is completely incorrect. MDT integrated with ConfigMgr can still use the DB. Here's a great article by some of the folks resposible for much of MDT: http://deployment.xtremeconsulting.com/2009/11/24/understanding-the-mdt-configuration-database-part-1/. The MDT DB will continue to be managed by the workbench as you've stated. All of the customized MDT configuration files are delivered via the MDT package(s) during the TS.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

When using MDT integration with ConfigMgr, you will see a new menu option for boot images and task sequences. Once integrated, you would not use the MDT workbench for anything but working with the Database. You could use a solution like Maik's MDT Web Frontend to work with the database, thus not having to use the workbench for any component of the MDT integration with ConfigMgr. If you want to use Lite Touch (LTI) then you would still use the MDT workbench. Here is a 3-part series i did on MDT integration with ConfigMgr, i would highly recommend you read these posts if you are interested in MDT integration with ConfigMgr. This will be a quick-start guide for integrating MDT 2010 Update 1 with ConfigMgr SP2/R2. This will be a three part series covering the Setup, Boot Images and Task Sequences. Part 1: Setup Part 2: Boot Images Part 3: Task Sequences Please let me know if you have any further questions, I have been working with MDT "integration" with SMS/ConfigMgr for over 5 years. MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx

Jason and Chris, thanks very much. I think I'm starting to get the picture now. Also got the following from another resource which looks promising: http://blogs.technet.com/b/deploymentguys/archive/2009/08/17/location-deployment-wizard-for-configmgr-2007.aspx In our current environment I have already created various tools to manipulate the database directly so I rarely use the workbench for this purpose. When I get our final config working I'll be sure and post some information. Thanks Guys!