Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote -4 down vote favorite

Install and configure a Windows Server 2012 domain controller on Virtualbox (4.2.6). Can someone give me advice, or provide links to documentation / tutorials, on how to do this,

I've been trying for hours with no joy.

I'm a noobie at this and would really appreciate any and all help given.

share|improve this question
2  
Domain controller? On VirtualBox? Don't. – Michael Hampton Jan 8 at 14:23
If this is for some sort of testing then just install 2012 and promote it (make sure you don't have it on your public network). But yeah, Don't do this for production... there be dragons. – Nate Jan 8 at 14:34
I'm trying to install and configure a Windows Server 2012 domain controller on Virtualbox and would like help in configuring Dns services once the virtual server has been promoted to a domain controller – LondonGuy Jan 8 at 16:13

closed as not a real question by MDMarra, Dave M, Chris S♦ Jan 8 at 16:07

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.

1 Answer

up vote 0 down vote

NOTE: I'm assuming you are doing this for testing purposes in an isolated environment.

Here's a pretty basic walkthrough: http://www.learnmsexchange.com/windows-servers/windows-server-2012/586-how-to-install-windows-server-2012-on-oracle-vm-virtualbox-manager

There's even youtube videos out there.

If you are wanting the domain controller role after installation, just install that role on the VM. You can use this as that walkthrough: http://social.technet.microsoft.com/wiki/contents/articles/12370.step-by-step-guide-for-setting-up-windows-server-2012-domain-controller.aspx

If you get stuck at that point, ask a new question relevant to what you are needing help on.

share|improve this answer
Thank for the quick reply. Yep, the whole thing is totally isolated on a non networked laptop (i5, 8gb, win7 ultimate). I've installed the server, installed the rolls, and promoted to AD. I've got in a real mess re: Dns configuration eg forward/reverse lookup: Srv records etc. A big problem is that I don't know which has vbox virtual network mode to use eg host only/bridged or internal network. – LondonGuy Jan 8 at 14:53
Well, it's up to you if you want to accept my answer based on your original question and start a new question in regards to your actual issue. the Vbox mode would depend on what you are wanting to accomplish (ie. what machines you want the VM to communicate with) – TheCleaner Jan 8 at 14:59
Sorry but I didn't mean to dismiss your reply - quite the opposite. I would really appreciate help with configuring DNS once the server has been promoted to a domain controller. I running the vm using using vbox's "internal network setting. The domain name is serverlab.local : fixed ip = 10.0.0.1; subnet = 255. 0.0.0; and preferred DNS = 127.0.0.1 – LondonGuy Jan 8 at 15:18
Internal network setting will allow the VM communicate with other VMs only. You have to use "bridged" if you want it to communicate through your host adapter to the internet, other physical machines, etc. Without knowing what you are trying to accomplish it is hard to give you advice. Things like using ".local" isn't best practice anymore either. Install DNS after your make it a domain controller and do NOTHING to it. Just let it sit there for 15 minutes. It will create its own SRV records, etc. – TheCleaner Jan 8 at 15:23
Thanks TC. My aim is to set up a dc and 2 virtual win7 clients. Internal network is good for me as I don't need Internet connectivity at the moment. I will be creating other vm's on the host. Interesting point ".local" - any reason why this is the case? (the domain at my work place is a "local" – LondonGuy Jan 8 at 15:39
show 1 more comment

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