Sheridan Posted August 4, 2011 Posted August 4, 2011 I've got an Exchange 2003 box on Server 2003 with OWA enabled for remote access (with SSL on the site) I cannot for the life of me get the OWA Admin site to work - it needs SSL, but I cannot set the site to use SSL as it conflicts with the OWA site. I understand you can only have one SSL per IP address. I need SSL on the OWA, and I need to occasionally use OWA Admin - so whats the best way to do this? If I add a seperate IP address and put SSL on that it causes problems as the OWA site can be access via that as well? Is there an easy way around this or am I missing something obvious?!
Bruce123 Posted August 5, 2011 Posted August 5, 2011 You probably need to change the virtual web folders (if that's what they're called) so from the user's perspective they use https://xxx.xxx.xx/OWA for OWA and https://xxx.xxx.xx/Admin for Admin (i.e. the same domain name/IP). Look at the OWA publishing rule on ISA (assuming you use that) and IIS on the OWA server.
sukh Posted August 5, 2011 Posted August 5, 2011 1. What do you mean by OWA Admin ? 2. Where is this V DIR?
Sheridan Posted August 8, 2011 Author Posted August 8, 2011 Somehow I seem to have fixed it. The OWAAdmin virtual folder was still using the OWA ip address for SSL, when it should be using its own unique IP address. Once I changed that its working for both on their own IP addresses now.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now