Due to an infrastructure change I needed to move my exchange 2013 (Version 15.0-build 847.32) on Server 2012 to another Windows Server R2 with exchange 2013 (Version 15.0-build 847.32). Both servers are virtualized with Hyper-V and  all updates applied. They are currently running in a coexistence mode and working fine. How I did the switch over by taking the IP from the old sever and added it to the new server. the old server is offline.  In the virtual directories I matched the Internal and External URLs.

When I brought up webmail I did get a logon box. However, after I logged on I get a auth page that can't be found. What step did I miss in transferring over to the new email server in a coexistence environment?

I'm going to guess that you moved the mailboxes from the old server to the new server. If not, you may need to change the urls on the old server to something else, and try again. what happens when you try to log on to the ECP on the new server?

All mailboxes have been moved.

When I tried to log on to the ECP I couldn't get there. Therefore I started back up the old mail server put the IPs back and ran in a coexistence mode and everything worked again. I did notice the address was correct of the new mail server when it worked. It may be an internal DNS thing. Not sure.

In moving the OAB from the old server to the new server is this done by just moving the system box to the new database on the new mail server?

Is there a script that moves all OABs to the new server?

I noticed when I ran this script:  Get-OfflineAddressBook | Format-List  That the virtual directories still showing are from the old mail server.

try running this: 

Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like "*oab*"} | ft name,database

That should show the new server and one of the new databases if it's been moved, chances are it's still going to show the old server and one of the old databases.  If it does, then run this command:

Get-Mailbox -Arbitration -database db1| where {$_.PersistedCapabilities like *oab*} | New-MoveRequest -TargetDatabase db2

Once that's done let AD replication run and try to shut down the old server again.

I would also suggest using 2 different namespaces for each server just to make life easier on you.  Maybe use something like webmail.domian.com for all the namespaces ont he new server with dns pointing to the new server and something like legacy.domain.com for the namespaces on the old server.  

I checked the databases and they have been moved to the new server as per the script. I then put the IP back onto the new server and the Exchange Management page showed up OK and I logged in. After I logged in I received a page not found and the URL is https://myserver/owa/auth.owa

Still not happening.

If you turn on the old server again and you go to https://newserver.domain.com/owa what happens?

Finally working.

I deleted all internet temp files to include cookies and restarted all of the application pools and it seemed to work. I have mail flow in and out with the old IPs on the new server. I used this KB as information:

http://support.microsoft.com/kb/2931385

• Marked as answer by sgtjd 17 hours 19 minutes ago
• Unmarked as answer by sgtjd 17 hours 17 minutes ago

Just went to another mailbox whose domain is also on this server and ran into the https://myserver/owa/auth.owa

Still trying to figure this out why one authoritative domain works and the other does not. I have 6 other domains that WORK and one that does not. Where do you go from here?

I checked on all other authoritative domain mailboxes and they work.

then I created another mailbox with the same authoritative domain and it worked.

restarted the application pool and now it seems to work. Hopefully this all works out in a few days.

• Marked as answer by sgtjd 16 hours 22 minutes ago