We have been using MDT 2010 LTI to deploy Win7 for the past year. Recently we implemented SCCM for sw distribution, updates, etc. I am now researching integrating the two. We have one site with 2000+ computers and one SCCM server (which also serves up some legacy GP-distributed software). I rather not use the SCCM server to host MDT deployment shares, to keep the load on it reasonable. In this case do I install MDT on the SCCM server, run the integration script, but use deployment shares on a separate server? Does this separate server that hosts the deployment shares need any MDT software, or is it merely a file share? Thanks!

merely fileshares... MDT integration will add XML and binaries to the SCCM installation share, to add extra wizards and menus. You need to integrate on the site servers you work on via RDP, and the clients you work on via the SCCM console... But why not use the OSD feature of SCCM, if not I don't really see any benefit of integrating!Michael Petersen http://blog.coretech.dk/mip/

I plan to use SCCM's OSD, I want to take advantage of the MDT integration benefits. With SCCM + MDT, is there still the concept of deployment shares? In some of the walk-throughs, I see no mention of deployment shares. Thanks

No, Deployment Shares are for LiteTouch only.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Close Jason - You still create a deployment share to create/manage the MDT database, even when having ConfigMgr :) Or you use Maik's superior MDT Web Frontend for the DB... / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Yeah, I should have provided more detail, so here goes :-) It's not that you don't have one at all. It's that it's not really used during actual ZeroTouch deployments; a.k.a. MDT integrated with ConfigMgr. Like Johan said, the MDT workbench requires you to create one if you also want to use the workbench to manage the MDT DB but you don't have to actually make the share available during a deployment because that is all handled by ConfigMgr using ConfigMgr Packages that live on ConfigMgr DPs and thus not used. And there are other ways to create and maintain the DB like Maik's awesome tool (just like Johan said).Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys