• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 90
  • Last Modified:

Exchange Server Migration

I currently have an exchange 2010 server running live on my domain. I started to install exchange 2010 on another server with the idea of migrating over to the new server eventually. I have installed exchange but did not setup any settings. It has been running on my network for about a week. All of a sudden my clients started to direct outlook to the new server automatically. I havent made any changes nor have I set any mailbox settings or anything. I have since stopped the services on that new exchange server. I am not sure why there are starting to point to the new server when its not even configured?
0
eli290
Asked:
eli290
  • 3
2 Solutions
 
Dash AmrSenior Specialist(PM)Commented:
In Exchange Server 2010 all messages are always routed through the Hub Transport Server. This is the case for:

    Messages routed to and from the Internet, with and without an Edge Transport Server;
    Messages routed to other Active Directory sites within the Exchange organization;
    Messages between mailboxes on the same Mailbox Server, even mailboxes within the same Mailbox Database;

Yes, you read that last one correct. If there’s one Exchange 2010 Mailbox Server with only two mailboxes on it, and the first mailbox sends a message to the second mailbox, it is routed through the Hub Transport Server.

If the Hub Transport Server is not available, the message will not be sent and the message will not leave the mailbox!

in saying that hope it explains one of the reasons of your clients trying to access New Server
0
 
eli290Author Commented:
I am still a little confused by that but I figured out the issue. My PDC had an issue with the network card and the live exchange server wasnt able to hit it. I had the PDC as the primary dns server on exchange and for some reason an old DC as the secondary DNS. So it wasnt able to resolve anything. Once I took the old server DNS out and put the new address in, then fixed the PDC and had that up and running I was able to correct the issue with a simple reboot of exchange to re-authenticate. Wasnt what I planned to do on my Friday night thats for sure but glad its fixed...
0
 
Md. MojahidCommented:
If you really don't want to use second one server then you should shutdown and also remove that server information from ADSI Edit

Go to Primary Domain Controller

2. Open ADSIEDIT

3. Right Click on ADSIEdit and Click Connect to

4. Connect to “Default Naming Context”

5. Navigate to the following objects and Delete them.

DC=Domain,DC=Com -> OU=Microsoft Exchange Security Groups

DC=Domain,DC=Com -> CN=Microsoft Exchange System Objects

6. Right Click on ADSIEdit and Click Connect to

7. Connect to “Configuration”

8. Navigate to the following objects and Delete them.

CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange

CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange Autodiscover

9. Force the Active directory Replication.

10. Exchange 2010 Manual Uninstallation is Completed
0
 
eli290Author Commented:
I am going to use that 2nd server but not at this second. I have to do some prep work. Thanks for the steps though!
0
 
eli290Author Commented:
was able to correct the issue on my own but comment was helpful knowledge and should be rewarded
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now