Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Changing Outlook Anywhere external name, and certificate problems

Unanswered Changing Outlook Anywhere external name, and certificate problems

  • Friday, April 20, 2012 5:48 PM
     
     
    Sign In to Vote
    0
    We need to change the external URL on our new Hosted Exchange 2010 (SP1) for Outlook Anywhere.  When the system was first set up, we had a temporary name pointed to it for testing (call it mailtest.companyname.com).  Now that we are preparing to go live with our server, we need to get rid of the testing name and put on a production name (mail.compname.com).  So far, I have changed the external host name using the Set-OutlookAnywhere command, but now I get a certificate error because the common name of the certificate is mail.companyname.com (mailtest.companyname.com and mail.compname.com are both included inside the certificate).  I didn't get that error before I made the change with Set-OutlookAnywhere, and I presumed that was because mail.companyname.com and mailtest.companyname.com had the same root domain (companyname.com)...but it didn't go away when I reversed the Set-OutlookAnywhere command and put things back they way they were before I started.  

    Also, when I do an autodiscover setup in Outlook 2007 using testuser@compname.com, it works but it sets the Exchange proxy to mail.compname.com (that's good), and it uses mailtest.companyname.com as the Microsoft Exchange server (that's not good).  

    Anyway, I need to have the Outlook Anywhere external name of our server work with the production name mail.compname.com.  I cannot use the common name of the certificate (mail.companyname.com) as it is still in use on the old 2007 Exchange system that we are trying to migrate from (yes, we are using the same certificate on both servers...I know, but it's just until we can get migrated off of 2007, it's not going to be a permanent thing).  Is there a way to eliminate mailtest.companyname.com completely? Can the existing certificate be made to function properly?...or can I at least make it so it doesn't throw certificate errors at the users when they connect using Outlook Anywhere?  I can fix the certificate properly once we resolve the whole migration mess, but I need things working for the users in the meantime.