Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
User

Migrate exchange 2007 from SBS2008 to win2012 after already completed SBS2008 to 2016 server migration

Hello,

I've made a SBS 2008 to Windows 2016 server migration following the guide: How to migrate from SBS 2008 to Windows Server 2016 (Essentials). I didn't migrate exchange 2007. Is there a way to proceed? Will building a new Windows 2012 server for SBS/exchange2017 --> win2012/exchange2013 migration work having already migrate the domain controller to 2016?

Thank you for your advice

Regards,

Nicolas

asked12/09/2017 22:53
2634 views
Add Comment
Last Activity 06/02/2019 05:55

1 Answer(s)

  • Mariette Knap

    Hello Nicolas,

    What you are doing is perfectly fine. It does not really matter what you do first. You can either migrate SBS 2008 to Windows Server 2016 first or migrate Exchange Server 2007 to Exchange Server 2013 and leave the SBS 2008 awhile active.

    The way you should proceed now is as follows:

    1. Migrate Exchange Server 2007 to 2013, read and use How to migrate Exchange Server 2007 from SBS 2008 to a new Exchange Server 2013 on Windows Server 2012 R2.
    2. After you have done #1 and uninstalled the Exchange Server 2007 from the SBS 2008 you can migrate Exchange Server 2013 to 2016. That last guide is currently under review and I am working on that. It will be finished soon but for the time being just leave Exchange Server 2013 running.

    You see in #2 that I mention that you uninstall Exchange Server 2007 from the SBS 2008. There is a reason for that. Microsoft has made it impossible to install an Exchange Server 2016 in a network that contains an old Exchange Server 2007.

    answered 12/10/2017 07:27
    Add Comment
    User

    Thank you for your quick reply.

    In the given tutorial you mention that migration should be done like this:

    SBS2008: remote.server-essentials.net --> exch2013: mail.server-essentials.net

    Is this a best pratice? May i keep remote.* ? Also I just figured out that the server is running an expired wildcard certificat, may i still migrate and renew the certificat afterward?

    Thank you for your advices,

    Rgs

    Mariette Knap

    You should have two certificates, one for Access Anywhere on the Windows Server 2016 Essentials that is also your domain controller. In most cases this would be remote.yourdomain.com. For the Exchange Server you should use a different domain and certificate, like mail.yourdomain.com. You need to use two different domain names for the different functions but you can use a wildcard certificate or a multi-domain certificate. A multi-domain certificate is one certificate that can hold multiple subdomains, like the remote and mail. Read this Difference Between Multi-Domain, UC Certificate and Wildcard SSL

    The mail.yourdomain.com certificate will be used to configure services on your Exchange Server but it will also be used on your WSE2016 by ARR (Application Request Routing). The ARR will forward requests for mail.yourdomain.com to your Exchange Server and this way remote users connecting to OWA or with Outlook traffic will be forwarded to the Exchange Server.

    The end result of the above is that one Public IP address can used for remote.yourdomain.com and mail.yourdomain.com and depending what ARR will find it will forward it to the Exchange Server or do nothing and traffic will go to Access Anywhere on the WSE 2016

    replied 12/10/2017 14:12
    Reply
    replied 12/10/2017 13:21
Add an Answer