Cool! I never even thought of that. Note carefully: These steps assume that a host record exists in the DNS to map the FQDN that you specify to the IP address of the CAS server
What it doesn't say (and should, I'm going to file an update request), is that the IP address must be an INTERNAL/LOCAL (on the LAN) IP address. -----Original Message----- From: Miller Bonnie L. [mailto:[email protected]] Sent: Thursday, January 21, 2010 10:06 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Issue http://support.microsoft.com/kb/940726 BTW, if you are able to create a cname for the old server to point to the new server's IP in DNS your 2003 and earlier clients may reconfigure themselves as well. -Bonnie -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, January 21, 2010 7:56 AM To: MS-Exchange Admin Issues Subject: Exchange Issue Hi folks. Wondering if anyone can point me in the right direction with this: Last weekend I migrated from Exchange 2003 to Exchange 2007. There are no issues concerning mail flow or access. My Outlook 200/2003 client needed to be manually reconfigured. My Outlook 2007 client found the new server and automatically reconfigured themselves. The server has a SSL certificate from VeriSign for active sync and OWA. The certificate is for the .com name of the Exchange 2007 server. We are having an issue with the Outlook 2007 clients only. I removed the self signed cert that was setup with exchange 2007. Every time outlook 2007 is open my users on the LAN are getting a certificate error if they click yes, it pops twice. If they hit yes both time outlook functions normally. Any ideas? Thanks! Dave
