That I cannot answer but have seen nothing indicating that this is the case. The 2012 R2 documentation simply lists it as deprecated. You should probably open an advisory case with Microsoft or communicate with your TAM (if you have one).
J From: [email protected] [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: Sunday, June 7, 2015 5:57 PM To: [email protected] Subject: RE: [mssms] 802.1x and SCCM 2012 R2 With NAP going away, is there RADIUS server function being moved into another role/feature? I would hope is not being killed off as well... — Sent from Mailbox<https://www.dropbox.com/mailbox> On Sun, Jun 7, 2015 at 3:59 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: As a side note, you know that Microsoft NAP is deprecated in Windows Server 2012 R2 and probably won’t be in Windows Server 2016, right? J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Hill Sent: Thursday, June 4, 2015 5:25 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] 802.1x and SCCM 2012 R2 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
