Experiences with the DirectAccess Test Lab for Windows Server 2008 R2

Experiences with the DirectAccess Test Lab for Windows Server 2008 R2

This is a stub topic.

If you have experience with configuring and using the DirectAccess test lab for Windows Server 2008 R2, please feel free to share any information that would be helpful for others to know. Examples of useful information to add to this topic are the following: 

  • Virtualized environment experiences, procedures, workarounds, and best practices (such as Hyper-V)
  • Common configuration gotchas
  • Experiences and procedures when substituting other versions of Windows for the computers of the test lab
  • Tips on troubleshooting this test lab
  • Tips on scripting in this test lab
  • Tips on application development and testing in this test lab
  • Tips on extending this test lab for larger multi-product scenarios
 
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Joe this is perfect.  I'm teaching Direct Access this semester at the college where I teach.  I have 42 students this semester.  There semester assignement is setting up Direct Access.  I will post feedback as to how it goes as the semester progresses.

    Doug Spindler

  • I am happy to have come across this - I am planning to deploy Direct Access in my organization and I will be using the test lab under a Hyper V as a proof of concept, I will definitely post my findings here

  • Is there any additional information availible for getting the Direct Access test lab working in a virtual environment, such as VMWare?  It only seems to work with real machines rather than virtualized.

  • David, The test lab instructions are designed to be independent of real machines, virtual machines, and the vritualization platform. If you are having specific problems, please post them at social.technet.microsoft.com/.../threads to see if there is a community solution.

Page 1 of 1 (4 items)