Yes, you need to be on R2 SP1 CU1. https://www.systemcenterdudes.com/managing-windows-10-with-sccm-2012/
*-----------------------------------------------* *Adam Juelich* Pulaski Community School District <http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Fri, Jun 10, 2016 at 4:10 PM, Juelich, Adam <[email protected] > wrote: > I'm not talking about Windows Server. I'm talking about the version of > ConfigMgr. I believe you need to be on 2012 R2 SP1 in order to deploy and > manage Windows 10 (sans Servicing). > > > > *-----------------------------------------------* > > *Adam Juelich* > > Pulaski Community School District <http://www.pulaskischools.org> > > Client Management Specialist > > 920-822-6075 > > > On Fri, Jun 10, 2016 at 3:30 PM, Fast, David D. < > [email protected]> wrote: > >> Server 2012+ is not required for deploying Windows 10 in a wipe-and-load >> scenario, which is what we will be doing initially. >> >> >> >> Using the RTM version of Windows 10 ADK. >> >> >> >> David >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Juelich, Adam >> *Sent:* Friday, June 10, 2016 2:54 PM >> *To:* [email protected] >> *Subject:* Re: [mssms] WinPE10 NIC driver for Dell E5470 >> >> >> >> Don't you have to be on 2012 R2 SP1 in order to deploy Windows 10? Are >> you using the Windows 10 ADK (RTM or 1511)? >> >> >> >> >> *-----------------------------------------------* >> >> *Adam Juelich* >> >> Pulaski Community School District <http://www.pulaskischools.org> >> >> Client Management Specialist >> >> 920-822-6075 >> >> >> >> On Fri, Jun 10, 2016 at 1:34 PM, Fast, David D. < >> [email protected]> wrote: >> >> >> >> I am trying to configure Windows 10 deployment via SCCM 2012 R2 CU2 using >> Task Sequence Boot Media; the boot media is working for all of our >> production use system models except for the Dell Latitude E5470 – I cannot >> get the WinPE10 network connection working. >> >> >> >> The server hosting SCCM is Windows Server 2008 R2 Enterprise SP1- while >> researching this issue, I came across a Microsoft support article that >> states >> >> Some drivers are signed by a newer signing method that's not recognized >> or natively supported by Windows Server 2008 R2. Therefore, these drivers >> cannot be imported into System Center Configuration Manager (ConfigMgr >> 2007, ConfigMgr 2012, or ConfigMgr 2012 R2) if the site server is Windows >> Server 2008 R2. To resolve the problem, install one or both of the >> following hotfixes on the site server that's experiencing the problem >> >> https://support.microsoft.com/en-us/kb/3025419 >> >> >> >> Can anyone confirm whether this information is still valid, or if the >> hotfix code was subsequently included in a later update (for server OS or >> for SCCM)? >> >> >> >> Thanks, >> >> >> >> David >> ------------------------------ >> >> The information transmitted is intended only for the person or entity to >> which it is addressed and may contain confidential and/or privileged >> material. Any review, retransmission, dissemination or other use of, or >> taking of any action in reliance upon this information by persons or >> entities other than the intended recipient is prohibited. If you received >> this in error, please contact the sender and delete the material from any >> computer. >> >> >> >> >> >> >> ------------------------------ >> >> *The Pulaski Community School District does not discriminate on the basis >> of any characteristic protected under State or Federal law.* >> >> >> >> > -- ------------------------------ The Pulaski Community School District does not discriminate on the basis of any characteristic protected under State or Federal law.
