Yes, thanks for the correction. You would want MDT 2013...I don't know why I said MDT 2012.
-Phil From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Tuesday, March 18, 2014 12:51 PM To: mssms@lists.myitforum.com; mdt...@lists.myitforum.com Subject: [MDT-OSD] RE: MDT and SCCM 2012 integration Given its ConfigMgr 2012 R2, I believe MDT 2013 is required (althought 2012 U1 may work, just not supported) From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Schwan, Phil Sent: Tuesday, March 18, 2014 12:34 PM To: mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: MDT and SCCM 2012 integration 1. Running the "Configure ConfigMgr Integration" (as an administrator) will install the extensions, but you will likely want to run through the "Create MDT Task Sequence" wizard at least one time to create the MDT Toolkit and an MDT Settings package. Keep in mind this is not something you just do on the site server; you have to run that integration on any machine running the ConfigMgr console that you will be using to manage MDT-integrated Task Sequences. 2. They will be separate (but can be on the same SQL server if desired). 3. Yes, you will want MDT 2012 U1 for integration. Keep in mind though that the MDT you use for CM integration does not have to be the same version as what you're currently using to generate the core image. All you're doing with MDT integration is providing templates and tools to augment the ConfigMgr OSD Task Sequences; the content you have in your current MDT 2010 environment (or any other) is not directly visible or applicable in ConfigMgr. You don't even have to launch the Deployment Workbench, create a deployment share or create an MDT database to do the integration. Even the MDT Toolkit package is simply using the MDT install as content source files for a ConfigMgr package, just the same as any other package. The MDT database is referenced by means of the CustomSettings.ini file in the MDT Settings package; the same method can be (and often is) used to connect to additional data sources for use by the ConfigMgr Task Sequence. 4. See previous comment. MDT integration with ConfigMgr does not preclude or replace independent MDT functionality. Hope that helps! -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com]<mailto:[mailto:listsad...@lists.myitforum.com]> On Behalf Of Beardsley, James Sent: Tuesday, March 18, 2014 12:14 PM To: mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [MDT-OSD] MDT and SCCM 2012 integration First off: Our imaging process is done in a separate department so I have little experience with MDT/OSD. They do the imaging, I do the application deployment. That's the way it was set up years ago and its been working fine but obviously, there are better ways to do it... and that's what we're trying to improve on. On that note, currently, our MDT (2010) environment is completely separate from SCCM. Over the next few weeks, our imaging team and I are looking to integrate that in with SCCM 2012 (R2). We've already got a server running MDT 2010 and its set up exactly the way we want it with all of the images and the Deployment Share created. We want to keep all of the images, TS's, drivers, etc that they (the imaging team) have configured over time. Questions: 1. I've found a couple of blogs about this and it seems too easy. Is it as simple as just running the "Configure ConfigMgr Integration" on the MDT server? 2. Is it recommended to keep the MDT and SCCM databases separate? Or would it be beneficial for all of that to be in one database? Being that our MDT environment is already configured, I'm assuming keeping the databases separate is the right choice. 3. Right now, we have MDT 2010. Is it required or should we upgrade that to 2012/2013 before doing this integration? (Note: We don't need the ability to do UDI. All of our imaging is done in one location by our imaging team and then the hardware is shipped to the new user) 4. Once the two environments are integrated, is all of the administration done in the SCCM 2012 console? Or is the Deployment Workbench still needed? Thanks in advance for your help. ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
