Good day all. We have installed Exchange 2013 into our single server 2010 environment. After a successful install I am not able to log onto the 2013 EAC. I know that since my mailbox is still on 2010 that I should not see EAC unless I use the
https://server/ecp/?ExchClientVer=15 but this does not work either.
I opened a case with MS on this and got a response but I am confused as to one part of the instructions. I replied to the engineer but she is offline for a few hours and I wanted to drop the instructions here and see if you know what it is that she is stating.
Question that I need answered: Below, at step 4 she left a note "Please run above command with your production install directory script". What you think this line means? Run this script from the provided scripts that came with 2010? Grab the script from 2013 files and run it on the 2010 server? or run this script on the 2013 server?
Thanks in advance!
Action Plan
=========
1. Recreate the ECP virtual directories on exchange 2013 server with the following commands (Run as Administrator) on EMS:
Remove-EcpVirtualDirectory -Identity "Server2013\ecp (Default Web Site)”
New-EcpVirtualDirectory -Server Server2013 -InternalURL https://Server2013.domain.com/ecp
Set-ECPVirtualDirectory -Identity "Server2013\ecp (Default Web Site)” -AdminEnabled $True
2. Recycle MSExchangeOwaAppPool under IIS, Application Pools.
3. Ran "iisreset" on EMS.
4. Ran the "UpdateCAS.ps1" powershell script from the Exchange install directory scripts subfolder. The command example is as follows:
C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateCas.ps1
Note: Please run above command with your production install directory script.
5. Open the IIS manager, find the Exchange Back End site, double-click Authentication on the right “/ecp Home” page. Point to Windows Authentication after launching Authentication windows. Right-click windows authentication, point to Providers. Make sure Negotiate and NTLM under Enabled Providers. You can refer to the related screenshot from my test environment as below:
6. Then re-run "iisreset" EMS.
=========