Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I don't know much about ActiveDirectory and here is my scenario

  1. I am connected to a "real" domain, which my company's domain.
  2. I am trying to develop an NTLM authentication solution with my webapp using Java Active Directory integration,
  3. so I figure I need to have an ActiveDirectory that I can fully control, the "virtual" one.
  4. I installed Windows 2008 Server R2 on Virtual box, running as domain controller.
  5. At this point, I thought I need to create another VM, say Windows7 VM which authenticates against that "virtual" ActiveDirectory, and where I will do my development.

Do I really need to do step 5 above? And what's the easiest way to do this? I have ActiveDirectory Lightweigth Services running on my physical box, and I think it does not help in this situation.

share|improve this question

The easiest - in terms of keeping your test AD away from the company's AD (which I recommend) - would be to do step #5, and keep those VMs on a private virtual LAN within VirtualBox. It's optional whether or not you configure VBox allow those VMs to make connections to he host (your physical box) - but the VMs should function as expected otherwise.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.