So, at my company, we have three MS Exchange servers. 2 2007 servers (exchange1, and exchange3), and a 2010 server (exchange2), both Standard edition. We are going to take one of the Exchange 2007 servers down (exchange1) to rebuild and install Exchange 2010 on, since we are licensed for that. I'm in the process of moving all of the services from exchange1 to exchange3. I have set up exchange3 with the same roles as exchange1, and moved all of the mailboxes over.
My issue now, is that when I stop the Information Store service on exchange1, people can't get into their email. I'm thinking that Outlook is still going to exchange1 as the client access server, but I'm not entirely sure about that. I have tested, and after moving, the Outlook clients are told to restart, and the new server is in their account settings, but it seems like the organization as a whole is somehow dependent on the Information Store on exchange1 being up and running.
I feel like there is more to be done, but so far I cannot find a technet article or forum post anywhere describing how to do what I want to do.
For reference, here is the output of netstat running on a workstation whose Exchange mailbox has been migrated from exchange1 to exchange3:
Active Connections
Proto Local Address Foreign Address State
TCP workstation:4096 exchange3.example.com:epmap TIME_WAIT
TCP workstation:4097 exchange3.example.com:1044 TIME_WAIT
TCP workstation:4103 exchange3.example.com:epmap ESTABLISHED
TCP workstation:4104 exchange3.example.com:53428 ESTABLISHED
TCP workstation:4106 exchange3.example.com:1044 TIME_WAIT
TCP workstation:4107 exchange1.example.com:epmap ESTABLISHED
TCP workstation:4108 exchange1.example.com:6139 ESTABLISHED
TCP workstation:4110 exchange3.example.com:53428 ESTABLISHED
I wonder about public folder stores. Are your clients connecting to a public store on the Exchange1 machine? Each mailbox database has a default public folder store setting. Check out the setting on the mailbox database where you moved the mailboxes.
On that workstation hold CTLR + right click the outlook try icon when connected and choose "Connection Status..." that should tell you what the client is connected to for what service. As Evan pointed out, the clients are likely connecting to a Public Folder Database on Exchange1.
Do you have the client access role installed on Exchange3, and did you make sure that SP2 was installed on Exchange 2007 first?
Run the following command against your 2010 database, to ensure the right CAS is being used:
This is how it should work:
When you move the mailboxes, Outlook clients connecting to Exchange1 will automatically be redirected to Exchange3. In order for this to work "seamlessly", the old server needs to still be up and running. It's generally best to leave the old server up for a week or two just to make sure that all the clients are moved like this aside from the few vacationers, etc.