• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Exchange 2010 change primary authoritative domain = SSL affects

I need to change the Authoritative SMTP to domain mydomain2.com (existing is mydomain1.com and will be kept as a secondary).  I am fine with the steps to do this in exchange 2010 however my confusion is with my current ssl certificate for mydomain1.com.  If I keep dns pointers (active sync and owa) as mail.mydomain1.com...

1.  will users till be able to access their mailboxes?
2.  do I need a second SSL cert to satisfy the mydomain2.com if users are still using the primary mail.mydomain2.com addresses to reach active sync / OWA
3.  If I use the mydomain1.com address for remote access...will I need to make IIS changes.

My goal was to implement the new mydomain2.com as the primary for immediate public visibility in regards to email reply to and then phase II the change of SSL cert and IIS (if needed).  Or am I being Naïve?

The server domain of internal.local remains the same.
0
pscanevit
Asked:
pscanevit
  • 2
  • 2
  • 2
  • +1
2 Solutions
 
Jian An LimSolutions ArchitectCommented:
you need 1 SAN certificate that covers multiple domain.

autodiscover.domain1.com
mail.domain1.com
autodiscover.domain2.com
mail.domain2.com

this way all of them will be covered nicely
0
 
btanExec ConsultantCommented:
Indeed as also stated to add in additional domain under step 6
http://technet.microsoft.com/en-SG/library/jj218640(v=exchg.150).aspx

you likely need to add new domain into the Accepted Domain list and under Email policy for the user to include this new domain (e.g. "Set to reply"). After updating the email for the users, you should be able to see their SMTP has these two domain accepted account.  
http://exchangeserverpro.com/change-business-email-domain/

Normally for the SSL, it is more of the services that will encounter issue such as certificate mismatch error. As stated below, this can include Autodiscover Service and/or Availability Service use the FQDN of the Exchange host in their URL (eg https://server.domain.local/AutoDiscover/AutoDiscover.xml) but the IIS instance has an SSL certificate that does not match that name.
http://exchangeserverpro.com/outlook-2007-clients-display-certificate-mismatch-error-after-mailbox-migration/

There is also shared SMTP Namespace for separate systems (one hold as authoritative while the other is non-authoritative)  that is more control required and doubt this is your use case eventually. There is mention below the need for working to either disable recipient filtering, configure the product to do LDAP queries against all directories that share the namespace, or create Contacts.
http://exchangeserverpro.com/how-to-share-an-email-domain-between-two-mail-systems/
0
 
Jamie McKillopIT ManagerCommented:
Hello,

If you would like to continuing using mydomain1.com for all your Exchange URLs, you do not need to make any modifications to the SSL cert. All you would need to do is add an autodiscover SRV record to the mydomain2.com zone so that autodiscover clients are directed to the old URLs. The record would be in the following format:

Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: mail.mydomain1.com

Simply setup that SRV record then change your e-mail address policy so that mydomain2.com is the default. You will then need to apply the policy so that all your default addresses are changed on your mail-enabled objects.

-JJ
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
pscanevitAuthor Commented:
Thank you all.  Just to make sure, as I have conflicting information between Jamie and limjianan, I understand that if want to utilize mail.mydomain2.com as the URL (after I make it primary) I need to add to SSL.  However, I was hoping to attack this as phase II.  I am being pushed to change our public face in a hurry and am hoping that Jamie's answer will do the trick.  Make Mydomain2 the primary...leave the existing URL pointer / ssl cert in tack until I can replace the SSL to incorporate both domains.
0
 
Jamie McKillopIT ManagerCommented:
That is correct. If you want to leave the URLs as-is, you can use the process I outlined. If you want to later change the URLs to use the new domain, you will need a new SSL cert with that domain.

-JJ
0
 
btanExec ConsultantCommented:
Agree with Jamie. You can check out this and it applies for Exchange 2010 as well. As long as SRV record points to the FQDN in the SSL certificate, it should work as in phase 1.
http://support.microsoft.com/kb/940881
But do note that the Autodiscover A record (if added) needs to point to FQDN in the certificate. In other words, if there is no Autodiscover A record, it did not then be restricted to the FQDN in the certificate.

On the side note, you may be interested in this short article if adding accepted domain is increasing and it take a balance of which option such as SAN or SRV or redirect will better scale moving forward.
http://www.msexchange.org/articles-tutorials/exchange-server-2010/mobility-client-access/using-autodiscover-large-numbers-accepted-domains-part1.html
0
 
pscanevitAuthor Commented:
thank you both for the great information...I not only have my current issue answered, but also a guide to new domain SSL.
Thank you!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now