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
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.
Part 4 concludes this series and explains how to configure vCenter to connect to your Zentyal appliance.