GPCDIADMIN
asked on
Cannot Access Exchange Control Panel ‘ECP’ in Exchange Server 2013
I was working with the authentications methods for OWA and frankly, I must have messed something up.
Now, when trying to access the ECP, after providing your username and password, it takes you to the OWA page and it gives you a blank “HTTP 400 Error” page.
I understand an administrator can use the Exchange Management Shell to reconfigure the authentications on the virtual directories, but my online research turns up contradictory shell commands. I request help to properly format the shell commands to correct authentications on the virtual directories for the ECP and OWA.
FWIW; One Exchange 2013 server holds all roles, the server name is "mail" & the internal name is mail.wti.local
Now, when trying to access the ECP, after providing your username and password, it takes you to the OWA page and it gives you a blank “HTTP 400 Error” page.
I understand an administrator can use the Exchange Management Shell to reconfigure the authentications on the virtual directories, but my online research turns up contradictory shell commands. I request help to properly format the shell commands to correct authentications on the virtual directories for the ECP and OWA.
FWIW; One Exchange 2013 server holds all roles, the server name is "mail" & the internal name is mail.wti.local
ASKER
The commands published at http://lyncdude.com do not work for me. They appear to be incomplete or something is not correct for my application.
This is a production server. Please, to earn your 500 points, I ask that you respect my server integrity and provide me with complete and (correct for this instance) instructions. Here is some more information to assist.
> Get-owavirtualdirectory | fl
Name : owa (Default Web Site)
InternalAuthenticationMeth ods : {Basic, Fba, Ntlm, WindowsIntegrated}
MetabasePath : IIS://EMAIL.WTI.LOCAL/W3SV C/1/ROOT/o wa
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
> Get-ECPVirtualDirectory | fl
Name : ecp (Default Web Site)
InternalAuthenticationMeth ods : {Basic, Fba}
MetabasePath : IIS://MAIL.WTI.LOCAL/W3SVC /1/ROOT/ec p
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
This is a production server. Please, to earn your 500 points, I ask that you respect my server integrity and provide me with complete and (correct for this instance) instructions. Here is some more information to assist.
> Get-owavirtualdirectory | fl
Name : owa (Default Web Site)
InternalAuthenticationMeth
MetabasePath : IIS://EMAIL.WTI.LOCAL/W3SV
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
> Get-ECPVirtualDirectory | fl
Name : ecp (Default Web Site)
InternalAuthenticationMeth
MetabasePath : IIS://MAIL.WTI.LOCAL/W3SVC
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
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 had actually had found lyncdude's page prior to posting this question in experts-exchange. I posted a question here because I needed more comprehensive assistance with the command arguments.
With the more complete information, I could readily deduce what elements were missing in my commands to successfully execute them. That is why my solution worked.
With the more complete information, I could readily deduce what elements were missing in my commands to successfully execute them. That is why my solution worked.
http://lyncdude.com/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/
(le copy le paste from source)
Solution:
make sure that the authentication methods used by OWA and ECP are matching this is done by running the following
> Get-owavirtualdirectory | fl
make sure that you using “Form based Authentication” and “Basic Authentication”
3
do the same with ECP using the following command line
> Get-ECPVirtualDirectory | fl
4
If not then you just need to reconfigure the Authentications on both Virtual Directories, DONNOT use IIS use Exchange Management Shell.
For owa use the following
>Set-owavirtualdirectory -identity “owa <Default Web site>” -FormAuthentication:$true
use the same also for ECP
>Set-ecpvirtualdirectory -identity “ecp <Default Web site>” -FormAuthentication:$true
then restart your iis services using the following
>iisreset
once finished try to access your ECP page again and it should work now
if it didn’t make sure to run the same command lines but using “owa <Exchange Back End>” to make sure that both Default web site and Exchange back end website authentication methods are matching.
Cheers