How to configure a Windows 2003 Server OS/DHCP/DNS/DC/MS Exchange on the same computer/Server?


I have managed to install Windows 2003 Server on my machine which will become my home server.
I have never configured DNS, DHCP or DC i have seen this being done but having 2 separate machines one acting as a DC configured with the DHCP and DNS and the other Server was setup as a File Server i think this is how it was setup.
Please i need instructions on having this kind of setup. My  local Internet provider does not provide Static IP address.

What iam planing to do is to have my computer act as a File Server, a Domain Controller, DHCP and DNS in order to have me add computers to the domain example: and have the Internet connectivity shared as i leave in a building and i have like 5 neighbours which i want them to log on to the domain and be able to share files and all other fun stuff. I want to be able to start preparing myself too to be able to install Windows 2003 Servers for anyone looking to have their own server. And also i would like to have my own exchange 2003 server that way i can host email accounts locally and owa. Email :

File Server: LD-CORPFS01
Exchange: LD-CORPEXC01

And with this information i will be able also to pass it to my coleagues and let them know how this is done since they don't speak English i will translate to them so we can become on the same page.

Thanks alot Gents...
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


You're asking several questions there, so let me pick out the issues one by one.

>> have the Internet connectivity shared

To share Internet access, you would want to use some sort of firewall device rather than route this through your main server. You could use a hardware firewall or a dedicated Microsoft Forefront Threat Management Gateway (TMG) at the gateway to your network to perform firewalling duties.

>> a Domain Controller, DHCP and DNS

This is relatively routine and it is quite normal to see these roles on the same server.

The server should be promoted as a Domain Controller using the 'dcpromo' command (from a Start > Run or a Command Prompt). The DNS role is automatically installed and configured as part of this procedure.

DHCP can easily be installed using the "Manage your Server" wizard (Server 2003) or the Server Manager "Add Roles" wizard (Server 2008 and 2008 R2).

Appropriate applets are added to the Start > Administrative Tools menu automatically when the roles are added to allow you to manage them.

>> also i would like to have my own exchange 2003 server that way i can host email accounts locally and owa

You CAN run Exchange 2003 on a Domain Controller. The configuration is supported, but by no means recommended (it is a security nightmare). If you have the money, I would suggest purchasing another Windows Server license and using some virtualisation solution to bring Exchange up in its own member server. If your hardware is relatively new, it will support a Hypervisor virtualiation system such as Hyper-V Free Server or VMWare ESXi.

Both are free products available for download from the Internet.

In either case, installing Exchange is pretty easy. Put the Exchange media in the server, open a command prompt, switch to the CD/DVD drive and execute setup /forestprep and setup /domainprep. This prepares the Active Directory schema for Exchange.

You then install Exchange by running the 'setup' command (with no switches).

To have mail routed in for mailboxes, you must configure MX records in your public DNS namespace. Exchange is then configured to accept email for those domains using Recipient Policies (in Exchange 2003).

I covered steps for Exchange 2003 above, but you might consider using a newer version, such as Exchange 2007 or 2010. These versions make it simpler, IMO, to setup, manage and configure your messaging solution, but require 64-bit hardware and a 64-bit Operating System. Exchange 2010 REQUIRES at least Server 2008 (64-bit) and also works on Server 2008 R2.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Great response by Tigermatt but I would like to add that whilst it'll all run ok from the single server (the security side you can decide on!) any problems you have with the Exchange app will make life a lot more difficult for you.
On a dedicated Exchange server, it's a lot more flexible and you can remove, install, test etc with a lot more forgiveness than if you did it on the sole domain controller.
If you look at various posts for upgarding, troubleshooting exchange issues, the people running it on a DC server have a lot more to consider and are often limited by having this scenario
Just to make you aware of limitations of having your proposed solution implemented.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.