Get on-the-go access to the latest insights featured on our Trustworthy Computing blogs.
It's important to deploy wireless technologies in such a way that they provide both security and ease of use for people that are connecting wirelessly to your network.
When you deploy wireless by using 802.1X authentication with Protected Extensible Authentication Protocol and Microsoft Challenge Handshake Authentication Protocol version 2 - which, combined, are affectionately known as PEAP-MS CHAP v2 - client computers authenticate your NPS servers by using the NPS server certificate, but people can still log on to the wireless network by typing in passwords and user names.
Note: Network Policy Server (NPS) is the Microsoft implementation of a Remote Authentication Dial-In User Service (RADIUS) server, and it is included in Windows Server 2012.
Brit Weston is a veteran writer on the Windows Server documentation team, and he has authored a new guide that shows you exactly how to configure 802.1X authentication with PEAP-MS-CHAP v2.
His guide is the Core Network Companion Guide: Deploying Password-based 802.1X Authenticated Wireless Access, and it's live on the Web at http://technet.microsoft.com/en-us/library/jj721726.aspx.
This guide is one of the series of Core Network Guides. The idea is that you first deploy your core network using the Core Network Guide ( http://technet.microsoft.com/en-us/library/hh911995.aspx ), then you deploy your server certificate using the Core Network Companion Guide: Server Certificate Deployment ( http://technet.microsoft.com/en-us/library/jj125379.aspx ), and finally you deploy wireless by using Brit's new guide.
Thanks, and if you have time - please provide ratings and feedback on these and other topics when you're visiting the Windows Server Technical Library.