It is only the MDT part that is not functional with XP though right? I can still deploy XP with SCCM 2012R2 standard OSD, just not with an MDT integrated task sequence, and use the MDT integrated task sequence for newer OSes only?
From: [email protected] [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Tuesday, October 22, 2013 11:51 AM To: [email protected] Subject: [MDT-OSD] RE: MDT2012 and SCCMR2 Todd - ConfigMgr 2012 SP1 with CU3 can deploy everything from XP to 8.1. The default WinPE 4 boot image (from site installed Windows 8 ADK) supports Vista/7/8, and then import a WinPE 3.1 boot image (from separately installed Win7 AIK) for XP and import a WinPE 5 boot image (from separately installed Win8.1 ADK) for 8.1. Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Tuesday, October 22, 2013 7:24 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: MDT2012 and SCCMR2 Unless you move your xp osd to stand-alone MDT. Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 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 Miller, Todd Sent: Tuesday, October 22, 2013 10:18 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: MDT2012 and SCCMR2 I ask because I need to support XP deployments for the next year or two- not exclusively or frequently, but I will need to be able to deploy and redeploy XP where hardware doesn't work with 7 and is cost prohibitive to replace. Since MDT2013 doesn't support XP and since 2012u1 doesn't work on SCCM 2012R2, I am stuck at SCCM 2012 sp1 - right? Also, no way to have a system that can deploy both Windows 8.1 and XP. Perhaps stand up a separate LTI infrastructure for XP apart from SCCM? The bummer there would be duplicating and maintaining sync with all the SCCM packages. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Monday, October 21, 2013 4:33 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: MDT2012 and SCCMR2 No, for a few reasons - primarily MDT 2012 Update 1 does not support the Windows 8.1 ADK (required by ConfigMgr 2012 R2) and there is revised logic in MDT 2013 for the multiple network access accounts. Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, October 21, 2013 1:33 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] MDT2012 and SCCMR2 MDT2013 lists integration with SCCM 2012 R2 as a new feature. Does that mean that MDT2012 is not compatible with R2? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
<<inline: image001.jpg>>
