Do you have something like HTTP redirection or default web site (servername.domain.com/) redirection to .../exchange configured in IIS? That would explain how you're being redirected to the old URL. I'm extremely confident that certificates don't do that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

The default website in IIS redirects to "/exchange", but not the full URL (I've gone through the IIS config thoroughly and cannot find any reference to the old URL). We don't have any redirection from http to https setup, since our firewall only allows in https for the front end server. Any other suggestions?

The default website in IIS redirects to "/exchange", but not the full URL (I've gone through the IIS config thoroughly and cannot find any reference to the old URL). We don't have any redirection from http to https setup, since our firewall only allows in https for the front end server. Any other suggestions?

Do you have ISA, TMG or other web publishing appliance?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Do you have ISA, TMG or other web publishing appliance?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Have a really strange issue that we aren't able to figure out... We have an Exchange 2003 front-end/back-end server setup, with a 3rd party SSL certificate and forms-based authentication setup on the front-end server. We are attempting to change the FQDN of the front-end server but are running into a weird issue. We were able to successfully import the new certificate with the new FQDN, but as long as forms-based authentication is enabled, we get a certificate error with the browser saying that the certificate doesn't match the FQDN (it lists the old FQDN). If you click continue, it redirects you to the old FQDN with a certificate error. If we disable forms-based authentication, everything works fine (the certificate is accepted with no warning but then we can't utilize ActiveSync). We have checked the logon.asp file and have even done registry/file searches for anything containing the old FQDN, but we can't find anything and are stumped. Any ideas???

The default website in IIS redirects to "/exchange", but not the full URL (I've gone through the IIS config thoroughly and cannot find any reference to the old URL). We don't have any redirection from http to https setup, since our firewall only allows in https for the front end server. Any other suggestions?

Do you have ISA, TMG or other web publishing appliance?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

No, the front end server is sitting in a DMZ hanging right off our firewall. I looked at the rules on our firewall and they are pretty basic. It just uses a static NAT to forward port 443 on the external IP to the front end server's internal IP. Basically, after I make the certificate switch (and run "iisreset") if I type in https://mail.newdomain.com, I get a certificate mismatch saying it is for https://mail.olddomain.com. If I click continue to bypass the warning it loads up https://mail.olddomain.com. If I immediately swith the old cert back in IIS everything works perfectly (no other config changes needed). Really weird...

Do you have something like HTTP redirection or default web site (servername.domain.com/) redirection to .../exchange configured in IIS? That would explain how you're being redirected to the old URL. I'm extremely confident that certificates don't do that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."