With the new DirectAccess feature in Windows 7 and Windows Server 2008 R2 you’ll now have the ability to allow remote users to seamlessly access enterprise shares, websites, and applications without the need to connect to virtual private network (VPN) systems. DirectAccess also gives IT managers the ability to update remote PCs anytime they are connected to the Internet, without the user being logged on to the machine. As you prepare to take advantage of DirectAccess, your first step should be about designing your infrastructure to support this access feature that provides different security options.
The Solution Accelerator team is pleased to announce the immediate availability of the Infrastructure Planning and Design (IPD) Guide for DirectAccess (Beta). This new guide provides actionable, best practices guidance that you can leverage to more quickly design your DirectAccess infrastructure right the first time.
The guide’s easy-to-follow, four-step process gives a straightforward explanation of the infrastructure required for clients to be connected from the Internet to resources on the corporate network, whether or not the organization has begun deploying IPv6.
This IPD Guide for DirectAccess covers four key steps in the design process for DirectAccess:
Also for those of you thinking of starting to deploy Windows 7, I encourage you to check out Gavriella Schuster’s post on Windows 7, MDOP 2009 R2 release and our many clients who are already deploying Windows 7.
As always, to get the latest information on Windows 7 follow our twitter feed at MSSpringboard and visit the Springboard Series on TechNet.