Solved

Exchange server on 2003 Server

Posted on 2006-06-22
14
219 Views
Last Modified: 2010-03-06
Here is my situation:

I'm currently have two servers.  One I use as a main server and make it become Domain Controller, the second server I want to install exchange server on it.  The second server will be a member on the main domain.  Now I have joined the second server to the domain but I can't install Exchange at all because I don't have a active directory, how do I point it to the DC server or is there a way for me to do this?
0
Comment
Question by:mandraksl
  • 7
  • 4
  • 2
  • +1
14 Comments
 
LVL 95

Accepted Solution

by:
Lee W, MVP earned 500 total points
Comment Utility
Make the one server a domain controller - make sure DNS is setup and that the second server uses ONLY the first server as it's DNS server.  Then Exchange should install.  It is NOT recommended that you make the second server a DC IF it's going to be an Exchange Server.
0
 
LVL 6

Expert Comment

by:Michael S
Comment Utility
Run ForestPrep on the DC and DomainPrep on the member server, then install Exchange.

Then if you want to administer, you can install only ESM on the DC and the Exchange mailbox information will show up in AD.

Jay
0
 

Author Comment

by:mandraksl
Comment Utility
I did run Forestprep on the DC and when I try to do domainprep on the member, I get the error message of "Failed to contact the Schema Master server for this Active Directory forest."  

It is because the DNS setup?
0
 
LVL 95

Expert Comment

by:Lee W, MVP
Comment Utility
Possibly - like I said:
make sure DNS is setup and that the second server uses ONLY the first server as it's DNS server.

Or, better still, post the settings on both servers.
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
Have you ever changed your domain controllers round?
I worked on a question last week where the poster had changed DCs months ago but the roles hadn't moved across correctly. He had to seize the roles to get Exchange to install correctly.

You can run forest prep and domain prep on any machine. I usually do it on the domain controller simply because it makes things easier. The data ends up on the DC anyway.

Make sure that your DNS is setup correctly as already outlined - with domain controllers ONLY listed as DNS servers in the network settings.

Simon.
0
 

Author Comment

by:mandraksl
Comment Utility
Hey Guys, I think my DNS setup is wrong.  I connect the member to the DC DNS, I see it but when I run the domainprep, it still showing that error message.
0
 

Author Comment

by:mandraksl
Comment Utility
And what do you mean by changing the domain controllers round?
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 104

Expert Comment

by:Sembee
Comment Utility
Shutdown an old one?
Demoted a domain controller back to a member server?
That sort of thing.

Simon.
0
 

Author Comment

by:mandraksl
Comment Utility
I didn't change any of the domain controllers.  I gave both server under the same DNS 127.0.0.1.  and I did point the member server to the DC server but still giving me the same message.
0
 

Author Comment

by:mandraksl
Comment Utility
This is what I will do, demote the DC and restarted the installation.  I hope this will work
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
The DNS as 127.0.0.1 may be the problem.
Change it to the real IP address of the DNS service. I have seen some funny results with 127.0.0.1.

Configure the domain controllers to use themselves as primary and the other one for secondary.

Simon.
0
 

Author Comment

by:mandraksl
Comment Utility
I"m currently connected to a fake domain that I make up, could this be the reason why I can't get it to work?
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
Depends what the fake domain is.

If it is a valid domain on the internet, then that can cause problems.
If you want to make up a domain, then you should use something.local (where something can be anything you like).

Simon.
0
 

Author Comment

by:mandraksl
Comment Utility
Thank you for you help guys, I'll spit the point.  What I did wrong was the initial setup of the DC server.  I reformatted and started over and I follow the step procedure above and everything is up and running.  Thanks
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now