After installing Exchange 2013 on a Server running Microsoft Server 2012 I am unable to bring up the (EAC) Exchange Administration Center. I am entering the addresshttp : // <servername> / ecp as listed in my instructions and i am getting ERROR 404 from the IIS8 Server.

404 - File or directory not found.

The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Hello,

If you to go check on Exchange CAS server, can you access it?

Did you get any error when you install the CAS server?

Thanks,

Evan

I reccomend using the FQDN of the server instead of servername, also you need to use https.

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Wednesday, February 06, 2013 6:13 PM

What does this cmdlet show:

get-ecpvirtualdirectory

???

That should show the correct URL.

Also, I think you would enter https (with s at the end).

This reference might help:

http://technet.microsoft.com/en-us/library/jj150562.aspx

I reccomend using the FQDN of the server instead of servername, also you need to use https.

Hi I think I found a workaround. Looking IIS settings it seems the Site host the exchange web is set to Port 444. However if you just type https://yourhostname/ecp this wil try to collect the port 443 and land in the "Default Web Site" where no ICP subfolder exist in c:\inetpub\wwwroot\. Try to use the following
https://yourhostname:444/ecp
this works for me.

Zoltn Forray
MCSE+I Hungary

• Proposed as answer by User_WGA Friday, July 05, 2013 2:15 AM

Hi I think I found a workaround. Looking IIS settings it seems the Site host the exchange web is set to Port 444. However if you just type https://yourhostname/ecp this wil try to collect the port 443 and land in the "Default Web Site" where no ICP subfolder exist in c:\inetpub\wwwroot\. Try to use the following
https://yourhostname:444/ecp
this works for me.

Zoltn Forray
MCSE+I Hungary

yes it worked out for me: 

https://servername:444/ecp

THANK YOU. I feel like a right nonce trying to log onto this from a *mailbox* server. Your post is the one that helped me overcome this problem.