In Beta stage

Sep 16, 2009 09:38 GMT  ·  By

Dreading virtual private networks and looking for an alternative? Well, Microsoft has just the thing for companies that are looking for an alternative to VPN, and it involves Windows 7 and Windows Server 2008 R2, emphasis on the latest iteration of Windows Sever, of course. The two operating systems used in tandem are capable of making various corporate resources, from e-mail servers, to shared folders, and even intranet Web sites, accessible from outside the organization’s network via DirectAccess and not through VPN.

There are however barriers that stand in the way of DirectAccess being embraced by corporate customers and integrated seamlessly into IT environments. DirectAccess is bound to be set back by IPv6, which is a mandatory requirement. But Microsoft is doing its part to streamline the adoption of DirectAccess. Illustrative of this is the new Beta release of the Infrastructure Planning and Design Guide for DirectAccess from the Microsoft Connect site – courtesy of the Infrastructure Planning and Design (IPD).

“The IPD Guide for DirectAccess provides actionable guidance for designing a DirectAccess infrastructure. 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,” revealed a member of the Microsoft Assessment and Planning Toolkit Team.

The IPD Guide is an excellent place to start for companies looking to tap Microsoft’s set of best practices when it comes down to deploying DirectAccess. Essentially, the guidance offered includes a 4-step process that will help corporate customers plan and design a DirectAccess infrastructure. The Microsoft Assessment and Planning Toolkit Team revealed that guidance covers “aligning the project scope with the business requirements. Determining whether IPv6, Teredo, 6to4, and IP-HTTPS connectivity will be supported for Internet-based clients. Assessing the need for IPv6 transition technologies including NAT-PT and ISATAP for internal communication. Determining the number and placement of servers, the certificate services requirements, and location of CRL distribution points.”