J D
asked on
Exchange Server 2007 to 2013 Migration
We are in the process of migrating from Exchange 2007 to Exchange 2013. I have gone through this migration guide (https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=3227-W-FgCEAgAAQACIAAEBAQAAAAQAAAAAwAMAAAA~), which has been very helpful. I am at the point where we just got the Edge server subscription configured with our MBX server. That is where my question comes in. Since I did this, our CAS server cannot connect to itself via the management shell, and I also cannot access the EAC anymore. I believe there is something in IIS, but I haven't any knowledge about IIS. I can get out to other sites as well, just not the EAC. I have attached a couple of screen shots of the problems we are running into. Any assistance is greatly appreciated.
CAS-management-shell.jpg
EAC.jpg
CAS-management-shell.jpg
EAC.jpg
ASKER
Thank you very much for your prompt reply. I tried both steps in the links you provided, and a no go for both. The cert wasn't in the Exchange back end bindings, so I added it, restarted the server, and no luck with that, either. :(
ASKER
I was looking at the CAS server certs, as I agree, its a cert issue, and I do not see the default client access server certificate there. Not sure how or why it got removed. There have been a lot of hands on this project, and it got designated to me, so I'm wondering if our client access server is shot....
Update - I was able to re-create the default cert, and will test now.
Update - I was able to re-create the default cert, and will test now.
Check the below link a guide for the migration and co-existence of Exchange 2007 to Exchange 2013:
http://msexchangeguru.com/2013/05/10/exchange2013-migration/comment-page-12/
Step-by-step guide for migrating from Exchange Server 2007 to Exchange Server 2013:
http://community.spiceworks.com/how_to/122658-step-by-step-guide-for-migrating-from-exchange-server-2007-to-exchange-server-2013
Hope this helps!
http://msexchangeguru.com/2013/05/10/exchange2013-migration/comment-page-12/
Step-by-step guide for migrating from Exchange Server 2007 to Exchange Server 2013:
http://community.spiceworks.com/how_to/122658-step-by-step-guide-for-migrating-from-exchange-server-2007-to-exchange-server-2013
Hope this helps!
ASKER
Thank you Kevin. I actually used those guides during a rebuild of the servers, and we are actually in the migrating phase now. I migrated over a test mailbox last night, successfully, but now cannot open the mailbox using Outlook, so time to do some research on that. I greatly appreciate you taking the time to assist me with this matter, and for the great links as well.
Maybe permissions got screwed up from migration from Exchange 2007 to 2013. Although you have full mailbox access, it can happen that user has set specific permissions (Deny) on mailbox items.
If that is not the case, try to create test user account with mailbox and give that user full mailbox permission over same mailbox and see if issue persist.
Also check this earlier discussion might help you to give some point - Unable to Open Mailbox in Outlook After Successful 2010-2013 Move: https://www.reddit.com/r/exchangeserver/comments/31hh6o/unable_to_open_mailbox_in_outlook_after/
Hope this helps!
If that is not the case, try to create test user account with mailbox and give that user full mailbox permission over same mailbox and see if issue persist.
Also check this earlier discussion might help you to give some point - Unable to Open Mailbox in Outlook After Successful 2010-2013 Move: https://www.reddit.com/r/exchangeserver/comments/31hh6o/unable_to_open_mailbox_in_outlook_after/
Hope this helps!
ASKER
That did get me a bit further, I wasn't able to even let the autodiscover go last night. After this though, I cannot check name, and the Exchange server name is a lot of alphanumerics, rather than the name. I have attached a screen shot.
Outlook.jpg
Outlook.jpg
ASKER
Getting closer. Just can't seem to get the server to auto populate when trying to open a migrated mailbox. Any suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran the test, and it did indeed fail. Our autodiscover Uri is set to https://autodiscover.fnbancs.com/autodiscover/autodiscover.xml. On the failed test, it's trying to go to https://autodiscover.pwcbank.com:443/Autodiscover/Autodiscover.xml. Not sure where it is obtaining the pwcbank.com:443 from??
ASKER
I also think there may be a permissions issue. If I log on as an administrator, and I manually key in the old exchange mailbox server that the migrated mailbox was originally on, it will switch over to the new Exchange mailbox server, and I can proceed to sign on. When I try doing it logged on as the user that is the owner of the migrated mailbox, it does nothing. I will have to do some research on permissions.
ASKER
I have tried all of the links provided, and still a no go. As I noted above, if I key in the server where the mailbox used to reside on, it will populate, but still not open. Running out of ideas.
ASKER
This issue has been resolved.
Take a look here:
https://evotec.xyz/exchange-2013-powershell-errors-out-and-exchange-2013-ecp-doesnt-work-correctly/
http://markgossa.blogspot.ca/2015/11/exchange-2013-2016-connecting-to-remote-server-failed-with-the-following-error-message.html