Book Image

Windows Server 2012 Unified Remote Access Planning and Deployment

Book Image

Windows Server 2012 Unified Remote Access Planning and Deployment

Overview of this book

DirectAccess, introduced in Windows Server 2008 R2, has been a ground breaking VPN-like connectivity solution, adopted by thousands of organizations worldwide. Allowing organizations to deploy without manually configuring every client and providing always-on connectivity has made this technology world-famous. Now, with Windows Server 2012, this has been made even easier to deploy, with a new friendly user interface, easy-start wizard and built in support tools.With Unified Remote Access, Windows server 2012 offers a unique way to provide remote access that is seamless and easier to deploy than traditional VPN solutions. With URA, the successor to DirectAccess, your users can have full network connectivity that is always-on. If you have deployed Windows Server 2012 or are planning to, this book will help you implement Unified Remote Access from concept to completion in no time!Unified Remote Access, the successor to DirectAccess, offers a new approach to remote access, as well as several deployment scenarios to best suit your organization and needs. This book will take you through the design, planning, implementation and support for URA, from start to finish."Windows Server 2012 Unified Remote Access Planning and Deployment" starts by exploring the mechanisms and infrastructure that are the backbone of URA, and then explores the various available scenarios and options. As you go through them, you will easily understand the ideal deployment for your own organization, and be ready to deploy quickly and easily. Whether you are looking into the simplest deployment, or a complex, multi-site or cloud scenario, "Windows Server 2012 Unified Remote Access Planning and Deployment" will provide all the answers and tools you will need to complete a successful deployment.
Table of Contents (17 chapters)
Windows Server 2012 Unified Remote Access Planning and Deployment
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

NAP and URA


With URA, NAP can be used to check the health of connecting clients and block them if they are not healthy. The NAP services and client are separate from URA, and so you need to design and build your NAP infrastructure independently. Unfortunately, you cannot configure the URA server itself to be your NAP server.

Once you enable NAP integration with URA, the URA server will work with your Health Registration Authority (HRA) and Health Policy Server (HPS). The NAP agent on your clients will generate a Statement of Health (SOH) and send it to the URA server. The URA server, before granting full access, will send the SOH to its designated HRA, which will work with the HPS to validate the status. Only if the HPS confirms that the client meets the requirements, will it let the client into the network. If the client doesn't meet the requirements, the HPS will tell URA that this client's a persona non-grata right now, and if you have configured it for remediation, will offer information...