E2K server on Domain controller?

I know that isn't the best way to go, bu we have a small business so i'm going to try anyway.
My problem is this, i'm quite a newbie to all this exchange stuff. I've installed W2K server, and SP2 already. Now I want the Computer to be in a domain, but since we are in a small company where there is none, just a workgroup of 4 pc's, I want to create a domain. Is it possible (and wise) to create a domain with this server and let it act as a DC? I know the computer has to be in a domain or else E2K will not work.

Who is Participating?

Improve company productivity with a Business Account.Sign Up

StevePalmerConnect With a Mentor Commented:
DNS and Domain names.
You will have a domain name for your Windows 2000 domain(which you can make up) and DNS which you use internally for name resolution. Internal DNS will be based on the domain name you choose.

The domain name you have for e-mail (@mycompany.com) must be registered on the internets DNS. It does not have to match the Domain name you chose for Windows 2000. When you configure Exchange you have to specify this domain name as the default for e-mail addresses otherwise you won't get replys.

Maybe an example will help.

I build a Windows 2000 server with the required services installed.
I then run dcpromo from start>run to create a domain controller. I choose the domain name company.local (I can make this anything I want basically).

DNS on the DC will then have a domain company.local showing.

I then install Exchange 2000 on to the DC. Configure it to send and recieve through the ISP etc. I want my e-mail to be to @company.co.uk. I have to change the default SMTP recipient policy in Exchange System Manager from company.local to company.co.uk so that mail going externally has the correct return address.

I don't know if I have made that clearer or as clear as mud :)
It is possible and a good decision to. Exchange must be a domain controller and will prompt you for a dns name and netbios name once you start the install process. Be ware on how you input the dns name: must be in the following format: servername.xyz

I learned this the hard way. For your workstations: you need to join the domain and you are good to go.

Having a DC does take some of the burden off of the rest of the pc's.

Once install is done: create your users and computers.
You need to do a little planning first. There are several points to keep in mind when creating a domain and installing Exchange 2000.

Win2k requires DNS. Make sure DNS is installed on the server and that in the TCP/IP properties it points to itself for DNS resolution. DNS is really important to Windows 2000.
Exchange 2000 requires that the NNTP Service (under Internet Information Services) be installed.
How does your company connect to the internet? Permanent connection or dial-up. This will affect how you configure Exchange to collect mail.
How do you receive mail at the moment? Do you use an ISP for POP mail or do you have no mail. You will need to get the ISP to set their DNS (on the www) so that mail knows how to be delivered to your domain.
Finally, what else do you want this server to do? File and Print etc. If it is a fairly normal server then it should cope with everything ok as there are only 4 PC's but be aware of overloading it or running out of disk space!

There are no problems with setting up a Domain and Exchange on the same server. I suspect the configuration issues for mail delivery and receipt will give you more of a problem!
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

ijsmanAuthor Commented:
OK, i will explain some more about the situation.

We have a company network (1 fileserver) where 4 pc's connect. We can share folders and can access files on the main server, general info or just to post stuff that everyone needs to access some time.
Now we have a new server, which we only want to use for email and calendar sharing.
We have a permanent conneciton to the net, with a LAN network. We collect mail via POP3, this works fine. I've already installed another server once and i know how to configure exchange. The isp just changes their MX records to point to our server's IP and we're good to go. we don't want ot use this server for other things like file or print.

'It is possible and a good decision to. Exchange must be a domain controller and will prompt you for
a dns name and netbios name once you start the install process. Be ware on how you input the dns name:
must be in the following format: servername.xyz

I learned this the hard way. For your workstations: you need to join the domain and you are good to

can i just make up any dns name? I think i'm mixing up dns domains and windows domains :)

if i'm right, bascially what to do is, install windows 2000, with all the needed stuff for E2K like nnts, dns etc.

then installl exchange, here i choose it to be a DC, give it a domain name (i.e. mymailserver.nl)

then after that join the workstations to this domain (or else they can't find the server??)
ijsmanAuthor Commented:
alright! that's clear now. The only thing left is this
do the users have to join the domain company.local to be able to communicate with the server?

i did a similar thinng before, and then the users were still in a seperate workgroup, they had to hard-code the server's ip in the host file to be able to access their mailbox through outlook.
I then tried to join my pc to this domain, but it couldn't locate it.

This last step isn't crucial i think, because it should work, i was just confused about the domain thing.
No. They can communicate ok with it but if they don't use the server for DNS lookups they won't be able to resolve the server name. It's easier if you join the clients PC's to the domain because they then login and all the password/username info is kept and they don't have to resubmit it to connect to shares, open Outlook etc.

If you set their IP config to use the DC for DNS then they should have no problems joining the domain. Win2k Pro and NT4.0 workstations should have no problems this way.

(To resolve internet names you can configure DNS on your server to forward requests to the ISP DNS servers. This is under the forwarders tab in DNS Manager. This may be greyed out if a root domain has been created on your DNS server. A root domain will appear as a "." in the forward lookup zones. If you delete this root domain then wait/reboot after a while you will be able to add forwarders.)
ijsmanAuthor Commented:
ok thanx!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.