Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Exchange 2016 Co-Existing with Exchange 2010 - Wild Card Certs

Posted on 2016-10-19
6
Medium Priority
?
88 Views
Last Modified: 2016-10-21
We are  currently using a SAN Cert for Exchange 2010 and we plan to install 2 new Exchange 2016 servers into our organization.  The  plan is  to Co-Exist for 3 months before moving all the mailboxes to Exchange 2016. Can we use a "Wild Card cert" when we install the new Exchange 2016 servers?
0
Comment
Question by:JimmyRiverside
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41851233
Yes. Just export the cert from 2010 and import into both 2016 servers.
1
 
LVL 32

Expert Comment

by:Scott C
ID: 41851341
Todd's got the answer.  Please don't assign me points.  Just confirming.
0
 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41851446
Just make sure the internal and external URLs in Exchange are set to an FQDN with the domain name that is represented in the certificate.
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 

Author Comment

by:JimmyRiverside
ID: 41853090
Do we still have to export a new Wild Card Cert from the Exchange 2010 Servers to the new Exchange 2016 servers?  I'm confused on why we need to export from the 2010 servers?  It's seems all that needed to import and export from the new 2016 servers only???
0
 
LVL 16

Accepted Solution

by:
Todd Nelson earned 2000 total points
ID: 41853093
However you do it the existing wildcard cert that is currently installed on the 2010 server needs to be exported (via EMC or EMS) and then imported to both 2016 servers (via EAC or EMS).
0
 

Author Comment

by:JimmyRiverside
ID: 41853094
Now I understand why. You are right.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question