This is a four-part series of posts explaining how to install and configure a Linux-based appliance in your vSphere lab environment to take the role as a Windows Domain Controller.
- Part 1 – Why and what
- Part 2 – Deploying the appliance
- Part 3 – Selecting the roles and configuring the appliance
- Part 4 – Creating the accounts and configuring vCenter
Update: Fernando Pimenta has been kind enough to translate this series into Portuguese. You can find the translated copies here.
Selecting the roles
Following on from part 3, log into the administrative web page with the username and password you provided whilst deploying the appliance. You’re presented with 4 standard Server Roles, each of which selects a subset of appropriate Modules, or you can individually select Modules.
I could have chosen the Infrastructure Role as the basis for this Domain Controller and tweaked it, but instead I individually selected the following Modules. The “File Sharing and Domain Services” Module is all you need to select for a Domain Controller and the other Modules are pulled in as dependencies, but I thought the other packages I picked would be useful in my lab.
- Click Install at the bottom right of the grid.
- Confirm to go ahead with the module installs (a number of other dependency packages are picked up).
Configuring the appliance
Once the packages are installed the configuration stage begins. First, you set which network interfaces are trusted. In my case I didn’t create a multi-homed VM so there was only once interface to set. This is my lab so I threw caution to wind and set it to Internal.
- Set a static IP address
- I’m not joining this to an existing domain, so kept this a Standalone server and set the domain name.
More module changes are made which can take a few minutes. Once the changes are complete a friendly Panda invites you to click onwards to the Dashboard.
Part 4 concludes this series and explains how to configure vCenter to connect to your Zentyal appliance.
5 thoughts on “A Linux-based Domain Controller for a vSphere lab – part 3”
so, let’s see – what is one of the hardest things to figure out – how to set the ip addresses – value of blacked out addresses as a clue as to what appropriate answers would be? 0 You could have used fake numbers that would give readers some idea – but you chose to just black out.
Sorry, I don’t see the point. You set the IP address to whatever you want on your network. It’s a standard a.b.c.d format. If you want a dummy value then how about 192.168.100.1? But it will only work if that’s a suitable IP address for the subnet it’s connected to.
No offense, Thomas, but if you’re not sure what to put in the IP address field, then why are you building a domain controller? If IP addressing is beyond your scope, then DCs are even further beyond it!
Very useful tutorial, this is exactly what I’ve been looking for to support a small office with multiple users on multiple PCs & Mac using NAS shares & loadbalanced XenServer VMs. (Also, great job blacking out the rather trivial IP settings which forces technically challenged users to figure out they can’t just copy and paste your settings!)
This guide was awesome, thanks for taking the time to create this.