Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange server on 2003 Server

Posted on 2006-06-22
14
Medium Priority
?
266 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 96

Accepted Solution

by:
Lee W, MVP earned 2000 total points
ID: 16962066
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
ID: 16962119
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
ID: 16962290
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
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 16962369
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
ID: 16963855
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
ID: 16964311
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
ID: 16964415
And what do you mean by changing the domain controllers round?
0
 
LVL 104

Expert Comment

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

Simon.
0
 

Author Comment

by:mandraksl
ID: 16988470
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
ID: 16995766
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
ID: 16995982
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
ID: 17002644
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
ID: 17003599
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
ID: 17012128
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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

916 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