Interesting thread, definitely one I'll file away. :) As the program manager for both OSD and MDT now, let me echo Jason's comment: MDT is still in development, we continue to invest in it, and will continue to do so. For all three scenarios: LTI, ZTI and UDI. (And when I say scenario, I mean the high-level ways in which you deploy an OS, not specifically the technology that drives that today.) This product has grown wildly over the past eight+ years, very much because of the strength of this and the larger deployment community. But, sometimes that growth is not always apparent, something that works well on a slide or as a demo at TechEd or a great blog post, but there is still growth, and there will continue to be growth.
So all great feedback, please keep it coming! Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, July 26, 2013 5:40 AM To: [email protected] Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) What? You don't want to do all your customizations in c++? I agree though, very powerful, was actually using it for a while as our LTI solution until we had our PowerShell frontend working. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Friday, July 26, 2013 8:33 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) +1 to that statement! From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Marcum, John Sent: Thursday, July 25, 2013 4:41 PM To: '[email protected]' Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) What would be GREAT is if they would write some improvements for UDI. It has so much potential yet so many flaws!!! ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, July 25, 2013 3:18 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) It is still in development to my knowledge - just without Michael (which is maybe not the best thing is the world although I'm sure Michael may be sick of MDT by now :)). The ConfigMgr team has stated that both LiteTouch and ZeroTouch will continue to be supported and developed. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Todd Hemsell Sent: Thursday, July 25, 2013 3:09 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD vs. MDT -- Let the debate begin (again) CM & MDT is the best IMHO. MDT fixes issues you never even knew you had. Tiss a horrid shame you are not still improving on it. My hatred for MS over that move burns with the fury of 10,000 suns. Happy for you personally though :-) On Thu, Jul 25, 2013 at 2:22 PM, Michael Niehaus <[email protected]<mailto:[email protected]>> wrote: I'd reply back with a longer reply if I weren't so tired. So you'll get the abridged version: Every customer has different requirements. For most, using MDT Lite Touch for image creation is easiest (although a lot of that is tied to many of the "waste of time" customizations made to the images being created). You can then use either MDT or ConfigMgr to deploy. For many customers, there are scenarios where both could make sense. There is no "one size fits all" answer. I see customers with 500 seats using ConfigMgr completely; I see customers with 400,000 seats using only MDT. If you want to use ConfigMgr for everything in every scenario, feel free. If you want to use MDT with ConfigMgr to help make that easier, feel free. (If you don't, I'll try not to hold it against you :)) If you want to use MDT without ConfigMgr, feel free. Just never ask me about doing something in ConfigMgr that MDT already does... Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Todd Hemsell Sent: Thursday, July 25, 2013 12:06 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD vs. MDT -- Let the debate begin (again) amen brutha! On Thu, Jul 25, 2013 at 1:04 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: Eww yuck (IMO). This requires duplication of effort, duplication of configuration, and duplication of resources. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Spinelli, Robert J Sent: Thursday, July 25, 2013 12:55 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) Thanks, that's a great point. Thank you. Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Thursday, July 25, 2013 12:57 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) No matter what, I would always use a stand-alone mdt share for my golden image creation. It just makes things easier. Christopher Catlett Consultant | Detroit Office 248-876-9738 |Fax 877.406.9647 Sogeti USA 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Spinelli, Robert J Sent: Thursday, July 25, 2013 12:53 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) This is what we're leaning toward, 1st pass OSD and if that doesn't do it for use then bring MDT into the mix. I would rather use one product to keep it simple, but might not be able to do that. Thank you. Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Thursday, July 25, 2013 12:45 PM To: '[email protected]<mailto:[email protected]>'; '[email protected]<mailto:[email protected]>' Subject: RE: [mssms] OSD vs. MDT -- Let the debate begin (again) If I have ConfigMgr, I rather use that to do my OS deployments and I can integrate MDT and still have access to MDT variables ,etc. Sent with Good (www.good.com<http://www.good.com>) -----Original Message----- From: Spinelli, Robert J [[email protected]<mailto:[email protected]>] Sent: Thursday, July 25, 2013 11:33 AM Central Standard Time To: [email protected]<mailto:[email protected]> Subject: [mssms] OSD vs. MDT -- Let the debate begin (again) Now that SCCM 2012 R2 is introducing some new variables and new task sequence steps (ex: Set Dynamic Variables) would you go with OSD over MDT? One of the main reasons we were going to go with MDT was because of the issue of not being able to build a machine in an untrusted forest: http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-iithere-can-be-only-oneor/ This has been resolved in R2 with the ability to use multiple network accounts, so were now leaning back toward using OSD. I was hoping for some input as OSD/MDT has always been my weakest skill. Thank you. Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | [email protected]<mailto:[email protected]> This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company. 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.
