Solved

Migrated to new Exchange 2000 server, now AD users don't automatically point to it in some cases....

Posted on 2006-07-24
6
202 Views
Last Modified: 2010-03-06
Hello,

I had an old MS Exchange 2000 server (BEFP1) which was doing a lot of other tasks as well and was starting to fail.  So I bought and setup a new Exchange 200 server (BEFP2) to offload the mail to.  I got it all configured and working and migrated all the mail accounts to it using the AD users and Computers snapin, then Exchange Tasks -> Move Mailbox feature.  All worked fine.  The problem is that this morning when people got to work some called down and said they couldn't get into Outlook.  I saw that in the Mail icon within Control Panel that the profile was still pointing to BEFP1.  I changed it to BEFP2 and all was well.  However, I am a bit concerned about this.  How can I make sure that all accounts will automatically see this new server?  Some computers logged in and saw the new server automatically and had no idea we even had a new server, by the way.  Thanks in advance!

ED7
0
Comment
Question by:electricd7
  • 2
  • 2
  • 2
6 Comments
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17168969
Hi!
Did you compare the DNS settings of the clients for which repointing automatically worked to the DNS settings of the those for which it did not?

Dean
0
 

Author Comment

by:electricd7
ID: 17169589
Yes they are the same (both pulled from a DHCP server here).

0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17169963
Is BEFP1 running when the clients which are not redirected try to log in?

Dean
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 17172013
Have you been through the correct procedure for removing the the original Exchange server?

http://support.microsoft.com/default.aspx?kbid=307917

If not, then you should.

Is the original server a domain controller?
Is the new server a domain controller?

(don't change based on those questions - the answer will depend on the next response).

Simon.
0
 

Author Comment

by:electricd7
ID: 17172133
Neither is a domain controller.  I have not yet decomissioned the original server.  I will do that now.
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17172319
You don't have to fully decommission the server. I would go through the article up to but EXCLUDING removing Exchange.

Simon.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
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

773 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