Hello, Currently trying to migrate to Exchange 2013 and having issues. The initial test rollover did not go well on Saturday so I failed the DNS entries back.
Current environment is Exchange 2007 and Lync 2013. Clients are Office 2010 / 2013, and active sync users.
In adding the 2013 server, I did also create a legacy.domain.com DNS entry to point to the IP address of the existing 2007 server.
Everyone's mailboxes (and public folders) are on the 2007 server. I migrated one test account to the 2013 server for testing purposes only. That test account also has a Lync account.
So before rolling out the changes, I update the HOSTS file on my PC to try to simulate a real switch. Its internal on the network so I added the new 2013's IP address with mail.domain.com and webmail.domain.com.
In DNS autodiscover.domain.com has a CNAME to mail.domain.com so I don't think I need to put that in my hosts file. Anyway my account does appear to load in Outlook 2013. However Lync 2013 has a yellow banner under the 4 main icons that says Exchange credentials required. If I put them in, it keeps prompting. I just close out of it and Lync still works. So this is one thing that needs to be fixed.
If I try to access our webmail at https://webmail.domain.com, I put in my 2007 mail account username and password, but then it redirects to https://www.webmail.domain.com/owa/auth/owaauth.dll which cannot be displayed because there is no host called www.webmail. I would imagine it should redirect to legacy.domain.com right? I'm not sure where it is adding the www. in front because in the 2013 Exchange Admin Center under servers > Virtual Directories, the internal URL is https://mail.domain.com/owa and the external URL is https://webmail.domain.com/owa.
So this needs to be fixed as well.
Lastly, if I try to login with the test account that has the 2013 mailbox, Outlook and Lync both repeatedly prompt for credentials. It doesn't appear to accept the credentials at all. I can log into OWA at https://webmail.domain.com and that loads nice Even setting automatic replies or changing themes works, which is a function of /ecp.
So another piece of the puzzle is that the existing environment has https in the firewall pointed directly to exchange 2007. Whereas the new deployment has new outside IP pointed to a system on our DMZ. This system is running IIS ARR and works great for all the LYNC 2013 features like external LYNC access through mobile apps, off site PC's, hosting meetings, etc. And I seem to be able to go through this to get to the new Exchange 2013 OWA as well. But when I changed external DNS on Saturday, ActiveSync still worked, but if I tried to log onto OWA with my account from the outside, I got "too many redirects" on my mobile browser.
I am at a loss here of what could the issue be. Its a few problems here and I'm trying to get everything working fine using modified HOST file on my PC before spending downtime off hours changing internal and external DNS and the client access URL's on the 2007 server for both Internal and External.
Your help is greatly appreciated!