Link to home
Start Free TrialLog in
Avatar of oncall4you
oncall4youFlag for Canada

asked on

Exchange 2010 OWA not working right after SP3 upgrade

My OWA on exchange 2010 was working fine until I installed SP3. Prior, I had it configured so that my users didn't need to specify https: to get access.  After the upgrade, I went into IIS 7 and set the http redirect to https://mail.mycompanydomain.com/owa and told it to not require ssl and ignore certs.  I have an entrust cert for mail.mycompanydomain.com but I don't want users getting the continue prompt when then accessed internally in the network.  There is also a cert generated by the exchange server "email" for server "email".

Ok, so here is what happens now.  Users internally can use email/owa  and external users can use mail.mycompanydomain.com/owa   They are then prompted to login.  They do not need to specify https://.  But then things go wrong.  They click on new to send and email and a warning pops up saying "Your request couldn't be completed.  This may have occured for security reasons or because your session timed out"  They can't even type in an email address.  It won't accept it.  If they specify the https:// on the address line, everything works fine.

My boss has instructed me to make sure they DON'T need to type that.  The users find it annoying.  It used to work.  I am sure it is something with the redirect not working, but I am confused as to what to do to fix it.  

HELP!!!
ASKER CERTIFIED SOLUTION
Avatar of Adam Farage
Adam Farage
Flag of United States of America image

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 oncall4you

ASKER

Brilliant!  I had the redirect set to the full path and it should have just been to /owa, and then the redirect had to be removed on the sub pages, but most importantly I had to edit the web.config files in the OAB for authenticated users read and execute AND in the OWA directory to make require ssl FALSE.  For the record for anyone else reading the steps in the first link are what fixed this.

I posted on TechNet two days ago, I got one response from an MS engineer after 30 hours asking what my cert names were, I posted on EE and got the right answer within an hour.  This absolutely proves that my subscription to EE is money VERY well spent.