Using eBox As Windows Primary Domain Controller

Want to support HowtoForge? Become a subscriber!
 
Submitted by jagz (Contact Author) (Forums) on Wed, 2009-11-25 18:51. :: Samba | Storage

Using eBox As Windows Primary Domain Controller

eBox Platform is an open source small business server that allows you to manage all your services like firewall, DHCP, DNS, VPN, proxy, IDS, mail, file and printer sharing, VoIP, IM and much more. These functionalities are tightly integrated, automating most tasks, avoiding mistakes and saving time for system administrators.

This tutorial shows you step by step how to use eBox as Windows Primary Domain Controller. At the end of it you will be using eBox Platform 1.2 for users and shared resources management on your Windows domain.

 

1. Installing the eBox server

The system installation can be done in two different ways:

  • Using the eBox Platform Installer (recommended).
  • Using an existing Ubuntu LTS Server Edition installation..

In the second case, you need to add eBox Platform PPA repositories to your sources.list and install the packages you are interested in.

Nevertheless, in the first case eBox Platform installation and deployment is easier as all the dependencies are in a single CD and in addition, some pre- configuration is made during the installation process. For this reason we will take this approach on this tutorial.

 eBox Platform installer

The eBox Platform installer is based on the Ubuntu installer and therefore those who are already familiar with it will find the installation process very similar. We will not cover here the Ubuntu system installation, but you can check the official installation documentation

When the base system installation ends, the system will reboot and the eBox installation process will begin. Then will first ask you which software components are going to be installed. There are two methods for selecting the functionalities you want to deploy on your system, we will choose the 'simple' method.

Selection of the installation method

After choosing the 'simple' method, you will get a list of software profiles. In this case we will choose only the 'Office' profile which contains all the software components needed for the PDC. This selection is not final and if you need more functionalities on the future you can install and remove packages according to your needs.

Selection of the profiles

Once you have selected the components to install, a progress bar will show you the installation process status.

Installing eBox Platform

When the installation finish, you will be requested to enter a password to access the eBox Platform web interface.

Enter password to access the web interface

You need to confirm the password.

Confirm password to access the web interface

The installer will try to pre-configure some basic configuration parameters. First, it will ask you if any of your network interfaces are external (not within the local network), i.e. used to connect to the Internet. Strict policies for all incoming traffic through external network interfaces will be applied. Depending on the role the server plays, i.e. placed inside your local network, there might be no external interfaces at all.

Selection of the external interface

Then it will ask you for your default mail virtual domain name. As we will not be using the email server on this tutorial you can enter here any name you like.

Set default mail virtual domain name

Once you have answered these questions, each module you installed will be pre- configured.

Preconfiguring eBox packages

After this process is completed, a message will inform you on how to connect to the web interface of eBox Platform.

eBox ready to use message


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by Brian C (not registered) on Sun, 2010-09-05 07:59.
In windows in order to be a domain controller you have to enable DNS, why would that not be true with ebox, just a thought? I will try this the way you have written it I am sure it was working for you before you wrote this, I was just wondering. Maybe this was just for a one server application with some sort of router for DHCP also. Dunno, any way thanks for the tutorial not trying to nit pick just trying to figure out the network environment for this setup is all.
Submitted by Anonymous (not registered) on Thu, 2011-10-20 03:35.
DNS is required for Active Directory. ebox sets up an NT style domain controller which did not require the DNS setup.