Just recently , our old domain was replaced with a new domain. Ex. *.###-systems.com (old) , with new *.antera#######.com (new). We corrected all the DNS entries from the old to the new so that the migration would be seamless. our SSL which was installed on the Windows server 2008 with Exchange server 2007 Standard has expired, which was for https://exchange.###-systems.com. We have since purchased a new SSL for exchange.antera@#@@#@#@.com (new domain, some characters blanked out for security reasons) and installed it per instructions on petri.il forums. I have installed the new SSL cert, however I am unable to go to OWA , as i get a Infinite Loop Redirect error. Things that are working are : Internal Outlook mail connecttion by clients : GOOD RPC Connectivity via Outlook anywhere : GOOD - Outlook 2007 clients working fine and but only can connect under the new SSL URL https://exchange.antera#######.com Active SYNC to mobile devices : Working FINE and updating as normal. Push is working OWA URL : Not working and not correct. I need to change all the URL's from the old domain to the new domain and make all the services, OWA, OAB, OOF , Autodiscovery and such as well as ActiveSync all work from external access. please help. Thanks. Doug

I would start by taking the redirect off the root of the server. It could be a home page modification or in IIS manager. It would NOT be something that Exchange will do, so something has been changed. Changing the URLs is quite easy, most of them you can do through Exchange Management Console. Web Services has to be done through EMS: Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx Autodiscover doesn't have to be touched, unless you have clients internally that are not on the domain. If you want to check then it is part of the client services settings: get-clientaccessserver and is under AutodiscoverServiceInternalUri (note the i) It would be changed for a single server deployment thus: Get-ClientAccessServer | Set-ClientAccessServer -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml Multiple servers thus: Set-ClientAccessServer -Identity "CAS-Server" -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

I have read the forums and information found on Petri.il in regards to using the command-lets for updateing hte URLS. I know how to change them in the EMC, and EMS. I have checked using all the commandlets you have listed. They come up with the old domain's URL, which i know how to change i guess now, using the command lets from the EMS. however the redirect off the root of the server and stuff like that, I have no idea how or where to even look on this. Thanks. Doug

That is someone has changed something, because it isn't a standard setting. It would seem that whoever did it, hasn't done it correctly. You wouldn't hard code the URL, you would set a redirect to /owa so that it didn't matter what was used. You will have to go through IIS manager carefully, check the home page settings, error page settings, properties of the root of the web site. There are a number of ways that it can be done. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

We have the system sitting on windows server 2008 with the latest IIS which is different than what i'm normally accustomed to in managing and maintaining. I have looked over the settings, and assure, you I am the only one who has been in the server, and I have not touched IIS at all. The only thing that i have done, was copy the crt file to the c drive, ran the import CRT command let in EMS and said yes to the overwirte of the old cert to the new one, for SIPW services and then tested. And this is where i am now.

If you could browse to host.example.com (where that was the previous name) and it loaded OWA, then something has been changed. Exchange never sets itself at the root of the web site. It is always host.example.com/owa Did you do anything to force or redirect http traffic, so users could enter host.example.com and get redirected to https://host.example.com/ ? I presume that you have checked the DNS is pointing to the server and it is that server which is generating the error? Changing the SSL certificate shouldn't have caused this error, at worst you would get an error message about the certificate name not matching. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

Our site has always been https://thedomainname.com/owa Always, we have never set it to root redirect at all.... Like i said, i have never changed anything on that. I looked in there just now, the only thing i see about redirects, is the http redirect is set for the system and pages, that if a user goes to http://thedomainname.com/owa -----> https://thedomainname.com/owa that is all.....I dont' see any other redirects in there, not to mention, i have not changed anything ....I so puzzled at this. At this point, i would be willing to let you remote to our server and see if you can pinpoint the problem. I have logmein installed and can set you up w/ an acct... I am so frazzled on this.

Unfortunately I am not covered insurance wise to remote in to servers that don't belong to my own clients. Have you got host headers configured for the web site? You will see that in bindings. If you do, remove them, particularly if this is a dedicated server. More than one web site on the machine? There are very few ways that it can be put in to a loop. Change the Exchange server so that I is not listed, or remove it from the web site in IIS manager. Remember to run iisreset after doing so. Does the same thing happen then? How are you doing that redirect from http to https ? Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

I will look into the host headers information under bindings. LIke i said, i'm new to this version of IIS and it's managment. It's really kind of foreign in this new manager to me. As it stands this is a standalone server, one physical installation, one website, Exchange is the only thing on the server. Change the server so that I is not listed ---- what do you mean by this Remove it from the website in IIS Manager - How and OK? Lost on this also. how are we doing the redirect from http to https: - Not sure exactly, i just know that in that spot when you open IIS 7 manager snap in, on the right of the default site, there is this icon for http redirect. when i click that, it brings up 2 boxes where you can type in the URL of where if a user types in http://Yoursitehere.com and it will redirect to the URL you provide. Thanks for you help so far. Doug

If you have put something in that does a redirect, then it would make sense to take it out. Any changes to IIS away from the default should be reversed, and run IISRESET afterwards to ensure that IIS has picked up the change. If that means an impact on the users, tough, if you want this resolved, then changes will have to be made. I cannot tell you how the loop is occurring, because I haven't seen it before myself, and have been unable to replicate it. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/