Solved

Can't connect to exchange after migrating sbs 2003 to sbs 2010 when stopping exchange services on source server

Posted on 2014-03-19
13
369 Views
Last Modified: 2014-03-19
After migrating public folders mailboxes and oab from sbs 2003 exchange server 2003 to sbs 2011 exchange server 2010, when I stop exchange services on the source server, the outlook clients and web clients cannot connect to exchange.
0
Comment
Question by:Racer1950
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 6
13 Comments
 

Author Comment

by:Racer1950
ID: 39941470
Yes, I followed the Microsoft document.
0
 
LVL 6

Expert Comment

by:rick81
ID: 39941471
send some emails out and check the email headers when received.
sounds like sbs2011 is using the exchange roles on sbs2003.  checking the headers will confirm.
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:Racer1950
ID: 39941479
headers show the correct server
0
 
LVL 6

Expert Comment

by:rick81
ID: 39941484
all the mailboxes migrated successfully?  they are all attached to the correct dbase and correct server?  check all the exchange services are running on sbs2011 ok.

any errors in event viewer.

i would stop the sbs2003 box and then look at event logs on sbs2011.  if its using sbs2003 for mail roles it should start throwing some errors and pin pointing what is going on.
0
 

Author Comment

by:Racer1950
ID: 39941506
I stopped each exchange 2003 service 1 at a time, each time sending and receiveing. Mail flow stayed on and outlook client stayed connected. Everything looks ok except in the 2010 management console, it still shows 2 exchange servers, 1 2003 and 1 2010 in Organizational Health after I ran a collect data.

I can't take a chance and power off the 2003 box at this time.
0
 

Author Comment

by:Racer1950
ID: 39941510
When I select manage servers from the management console organization health it only goes to the new box entry in server configuration.
0
 

Author Comment

by:Racer1950
ID: 39941512
No event errors
0
 
LVL 6

Expert Comment

by:rick81
ID: 39941514
is there a decommision process for the sbs2003.  ie uninstalling exchange2003, removing from the domain, deleting the 2003 exchange from 2010.
0
 
LVL 6

Accepted Solution

by:
rick81 earned 500 total points
ID: 39941516
sounds like the source server hasnt been demoted correctly.  follow the guide and these steps

Demote and remove the Source Server from the network
After you finish installing Windows SBS 2011 Standard and you complete the tasks in the Migration Wizard, you must perform the following tasks:
1.      Step 1: Prepare the Exchange Server 2003 organization to remove legacy Exchange servers
2.      Step 2: Uninstall Exchange Server 2003
3.      Step 3: Physically disconnect printers that are directly connected to the Source Server
4.      Step 4: Demote the Source Server
5.      Step 5: Remove the Source Server from the network
6.      Step 6: Edit the Software Updates Group Policy object on the Destination Server
7.      Step 7: Repurpose the Source Server
8.      Step 8: Restart the Destination Server
0
 

Author Comment

by:Racer1950
ID: 39941521
I haven't uninstalled exchange server 2003. I will accept your solution.
Thanks
0
 
LVL 6

Expert Comment

by:rick81
ID: 39941525
there must be some steps missing. i've found with migrations (i try to avoid them) missing one step can fail the whole migration.
0
 

Author Comment

by:Racer1950
ID: 39941528
I was spoiled by the last one I did. It went extremely well and quick. This one was with sick source server.
Thanks
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

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

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
To show how to create a transport rule 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 >> Rules tab.:  To cr…
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
Suggested Courses
Course of the Month11 days, 11 hours left to enroll

623 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