I'm afraid I might have a little mess on my hands. About 3 years ago I configured and installed an Exchange 2003 server for a client. Everything has been working great. They have never used the Active Directory on this machine ever. Their network gets its dhcp from the cisco router and we just create users on each pc. Well the time has come that we need to start using active directory since we have people moving around the office constantly.
I have two issues:
1. When I created the AD on the exchange server i made it mycompany.com. This is the domain that the exchange server is handling mail for. This is one of our domains that we own and we have a website on it that is hosted by an outside company. Everything that I have read indicates that this is the wrong thing to do as it may cause name resolution problems when people try to go to the website from inside the network. Is it that big of a deal?
2. We just installed a new 2008 server that we will be using as a terminal and file server. The load will be small as it will be used by probably no more than 10 people at a time. Can I just install AD on this server with a different domain such as company.priv and let the other domain just be an exchange server? I built the server pretty stout to handle AD and TS so it should be able to handle the load. Is it asking for trouble to put two domains on one network even though one is never used?
So the question seems to be: Sort of start over with a new and correct domain configuration on the new server and let the old exchange server just keep doing it's exchange job OR do I try to use the exchange server as it is with the domain being the same as our external website???
Either way I need to start getting AD up and running sometime soon. Any thoughts or real world suggestions is much appreciated. I'm sure I havent explained this very well so please be patient and I'll answer as many questions as I need to.