This is working as expected. To fix it 1. Remove the old CAS server role from the old server (or) 2. Change the ServiceConnectionBinding Object to point to new CAS server (ServiceconnectionBinding is the properties of Autodiscover, server->protocol->autodiscover in ADSIEDIT)VJ

This is working as expected. To fix it 1. Remove the old CAS server role from the old server (or) 2. Change the ServiceConnectionBinding Object to point to new CAS server (ServiceconnectionBinding is the properties of Autodiscover, server->protocol->autodiscover in ADSIEDIT)VJ

Hi jksport, Any updates? Frank Wang TechNet Community Support

Hi jksport, Any updates? Please Ctrl+click the Outlook icon to do a "Test E-mail AutoConfiguration". Please check whether you can browse the OOF url in IE.Frank Wang TechNet Community Support

Dear colleagues! I'm trying to migrate my Exchange 2007 to new hardware(MB, CA, HT roles). I installed new Exchange 2007 SP3 with all three roles, moved all mailboxes and everything looks fine. Now I'm testing all this by powering off the old server and looking what is wrong. And the thing which doesn't work at the moment is OOF feature. My Outlook says "Server is anavailable" and wont open OOF window. If I power on the old server - everything is fine, OOF is working. I know that OOF is using Autodiscovery and EWS features of Exchange2007 and I've recreated them several times on my new server - no success. Please help me with my question. Why my Outlook still want to connect to my old server for EWS? What should I do to point my Outlook to my new server for OOF service? Thank you in advance.