MDT. One location for gold images, you can set it n forget it when you automate things. Script/software can be changed/replaced very easy. My primary reason 'debugging' so much easier! On Jul 25, 2013 10:00 AM, <[email protected]> wrote:
> 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**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Spinelli, Robert J > *Sent:* Thursday, July 25, 2013 12:53 PM > *To:* [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]**** > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Dzikowski, Michael > *Sent:* Thursday, July 25, 2013 12:45 PM > *To:* '[email protected]'; '[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) > > > -----Original Message----- > *From: *Spinelli, Robert J [[email protected]] > *Sent: *Thursday, July 25, 2013 11:33 AM Central Standard Time > *To: *[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]**** > > **** > > 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. **** > > ** ** > >
