2012 R2 would be WinPE 5.0. If you need to use older versions of WinPE you can import those but if you have to add any drivers or anything to it you have to do that outside of the console manually and then re-distribute.
I'll let others handle the 802.1X specific questions. You could always configure a switch to be an exception and just use that for bare-metal. Devices should get their Cert through Group Policy afterwards, correct, to authenticate on the domain and rest of network? *-----------------------------------------------* *Adam Juelich* Pulaski Community School District <http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Thu, Jun 4, 2015 at 5:24 PM, James Hill <[email protected]> wrote: > We are preparing to deploy 802.1x in conjunction with Microsoft NAP and > Cisco switches. Everything is working well so far in our test environment > and we are now looking at how to handle OSD and baremetal OSD with SCCM > 2012 R2. > > > > Is there a more recent guide than > http://myitforum.com/cs2/blogs/lakey81/archive/2011/07/06/configuring-802-1x-network-authentication-for-winpe-3-0-and-configmgr-deployments.aspx > ? > > > > I’m of the understanding that from WinPE 4 onwards no patch was necessary > and that instead we need to add the optional component WinPE-Dot3Svc to the > boot image. > > > > Is the rest of the guide accurate? > > > > How are others handling PXE in an 802.1x environment? > > > > James > > > > > >
