Link to home
Start Free TrialLog in
Avatar of labdunn
labdunn

asked on

Can't reach Exchange 2010 ECP tools

I’ve broken my access to RBAC and the other web-based tools in the EMC Toolbox on Exchange 2010.
I’m trying to setup an Exchange 2010 CAS array using the public name to avoid the SSL deadline.  The inside domain name is contoso.local and the outside name is contoso.com.  The CAS servers are CAS01 and CAS02 and the CAS Array name is CASArray.  

I followed the steps in this article http://exchange.sembee.info/2010/install/clientaccesshostnames.asp that I found here on EE.  The certificate name is webmail.contoso.com.  Following the steps in that article I set the internaluri for Set-ClientAccessServer, set-WebservicesFirtualDirectory, set-OWAvirtualDirectory, set-OABVirtualDirectory, set-ECPVirtualDirectory, and set-ActiveSyncVirtualDirectory to webmail.contoso.com/whatever.

When I try to open the RBAC editor it asks for my login credentials and then goes to a page cannot be found error.  The URL it is trying to reach is https://webmail.contoso.com/ECP/?ftr=AdminRbac.   I suppose that url is a result of one of the changes I made  with the set commands above
Does the URL webmail.contoso.com need to resolve to the address of the CAS Array?  I have tried creating a hosts file entry that resolves webmail.contoso.com to the IP of one of the CAS servers and still have the same page not found error.
Is webmail.contoso.com the correct name to use?

Tx

Bill
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

Client Access Array's are site specific, have you looked at the technet document regarding the steps to create/configure this?

Reference the site below for details steps on configuring the CAS Array.
Understanding RPC Client Access Server

Will.
The CAS Array name should NOT be an external host name and should NOT resolve externally. It is should be an internal name only and does not appear on the SSL certificate.

Setting up the CAS Array shouldn't have broken access to the RBAC tools though.

Can you access EMS? If so you could probably set the URLs back to the defaults (server.example.local), then run IISRESET and that will get you access again.

Simon.
ASKER CERTIFIED SOLUTION
Avatar of labdunn
labdunn

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of labdunn
labdunn

ASKER

Own solution