Exchange 2010 Migration to Exchange 2010


I am contacting you because after a server migration Exchange 2010
we are encountering an unsolve problem.

Basicly, we had an exchange server 2010 running on Windows 2008R2, we upgraded it to Exchange 2010 on Windows 2012R2

Windows 2008R2 server is named EXCHANGE-2008R2.

Windows 2012R2 server is named EXCHANGE-2012R2.

The source server named EXCHANGE-2008R2 is running on Windows 2008 R2 SP0 (No Service Pack) and Exchange 2010 SP1

The target server named EXCHANGE-2012R2 is running on Windows 2012 R2 and Exchange 2010 SP3

Note: According to Microsoft, the SP3 is imperative to run Exchange 2010 on a Windows 2012R2 server.
Each Exchange server sees well the other server in the EMC (Exchange Management Console).
We’ve migrated:
- All user mailboxes (Including systems box)
- OAB (Offline Address Book)
- The Send and Receive connectors
- Public folders were also migrated (Replicate folders to the target server and delete replicas in the source server)

Since this migration, it is impossible to stop the source server (EXCHANGE-2008R2). Indeed, when we stopped the source server, multiple users (around 50%) instantly lose the link with the server.

When we verifing the outlook profile, we see that the exchange server is not swapped. It is always configured on the source server. On non-affected computers by this problem, in the outlook profile, the server has switched to the target server (EXCHANGE-2012R2).

Furthermore, we found in the transaction logs that the source server that contains no more users or public folder, the transaction log growes disproportionately.
After checking, it appears that the mails to the internet, start from the target server to go to the source server. The source server haven’t a Send connector to the Internet. The source server transmits messages to the target server to send to the Internet. See SMTP header in attached file.

To validate the migration, we’ve installed a test platform which incorporates the same conditions.
Windows 2008R2/Exchange 2010 SP1 and Windows 2012R2/Exchange 2010 SP3

Once validated full migration (with complete removal of the source server) we’ve completed the migration to production servers.
Following the problems, we have re-created a test platform to revalidate every elements and check any discrepancy between the test platform and the production.

We couldn’t find anything different.

On the test platform, when we stop the target server, a client connecting to Outlook automatically switches to the target server, and his profile changes automatically.

When we check on the production platform, connections through the rpcdiag option, we find that the connections pass through the source server. Yet users are connected to the target server.

The problem is similar to the transit of mails that makes a back and forth [server target / source server / target server]

We believe that an item exists in the directory AD / EXCHANGE redirecting systematically transactions to the source server.

When we check the Exchange settings, we find that nothing needed to use a priority server. As if the source server was a bridgehead server. This doesn’t seem to be the case in an Exchange 2010 environment.

We also control the configuration using the following controls :

Set-ClientAccessServer -Identity EXCHANGESRV -AutoDiscoverServiceInternalUri
Set-WebServicesVirtualDirectory -Identity "EXCHANGESRV\EWS (Default web site)" -InternalUrl
Set-OABVirtualDirectory -Identity "EXCHANGESRV\oab (Default web site)" -InternalUrl

But nothing happens.
please Help us !  :-)

Thanks in advance

Olivier BourreauAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott SilvaNetwork AdministratorCommented:
Changing server names will require the email profiles to be rebuilt... It isn't the cleanest, but it is the best solution.
Here is another option that might work for you, but you will have to test it...
Will SzymkowskiSenior Solution ArchitectCommented:
After reading all of that I am kinda lost to be honest. Server 2012R2 is not supported even with SP3 for Exchange 2010. Server 2012 (non R2) is supported so I would start there first and make sure that you are running on a supported operating system.

But doing an Exchange 2010 to 2010 migration is pretty straightforward. I would suggest that if you are having any issues follow the Exchange Deployment Assistant.

Exchange Deployment Assistant

Exchange Supportability Matrix


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Olivier BourreauAuthor Commented:
We installed incorrectly Exchange 2010 on Windows 2012 R2 because we had confused Windows 2012 and Windows 2012 R2.

Note: We built a model that works anyway but unfortunately is not validated by Microsoft.

Thanks for your answer.
Case fenced.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.