Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Chris Bridges

sbs2011 to exchange 2016 domain names

Hi,I wanted to check my understanding of the Exchange migration Para 6 ( Certificates)

On the SBS Server the Certificate is named remote.domain.com, and all outlook clients connect to remote.domain.com, both internally, and externally

On the new Exchange 2016, Can I still use the same remote.domain.com certificate, as defined in Para 5 , or does there HAVE to be a distinction in the domain name ( ie mail.domain.com) on the new Exchange 2016 setup in order for the migration to complete correctly.

and finally, where is the _autodiscover._tcp record held, I can't obviously see it in dns ?

 

Thanks

asked10/28/2019 16:16
61 views
Add Comment
Last Activity 11/07/2019 08:31

3 Answer(s)

  • Mariette Knap

    Hello Chris,

    Well, if you are going to use the same Hostname for the Exchange Server 2010 and 2016 you will create a DNS Loop. You won't be able to use OWA or possibly any Outlook client during the migration and even after the migration, you must get rid of the old Exchange Server 2010 asap because of that loop. It can be done using one Hostname but you need to understand the consequences.

    That SRV record needs to be created in Public DNS. Those are the people responsible for the DNS records. You can use MXToolBox to check your records. YOu can also see my record https://mxtoolbox.com/SuperTool.aspx?action=srv:_autodiscover._tcp.numinous-travel.com

    answered 10/28/2019 17:43
    Add Comment
  • Chris Bridges

    Hi ,

    OK, Changed to using different domain name ( mail.domain.com) for the new Exchange server - Perhaps the requirement for another domain name of mail.domain.com needs to be a bit clearer in the opening paragraphs for the exchange migration to show the separation from the remote.domain.com ?

    However in our setup, E-Mails on port 25 come in via an encryption appliance, and the SBS 2010 the send, and receive connectors both point to this appliance.

    At what stage in the guide do i point the new 2016 send / receive connectors to the appliance? Is this when ALL recipients have been migrated to the new 2016 server ?

    So at what point does the Exchange 2010 stop becoming a downstream proxy  

    Thanks

    Chris

    answered 10/31/2019 09:26
    Add Comment
    Mariette Knap

    Hello Chris,

    • I consider the different names for the two Exchange Servers basic understanding of DNS and name resolving but in a future version of the guide, I will add some text that clarifies that.
    • You can leave the send and receive connectors but as soon as a mailbox is migrated to the new Exchange Server you need to add that server to the Send Connector and make sure your appliance accepts that. The receive connector can remain untouched because any mail received by that connector will find its way to the mailbox normally, even if it has been migrated to the new server.
    • If a mailbox is still on the old Exchange Server and port 443 is pointing to the internal IP address of the new server, or if you have multiple Public IP addresses you should route traffic on port 443 for host 'mail.domain.com' to the internal IP address of your new Exchange Server. In that scenario, if a user connects for example to https://mail.domain.com/owa it will down proxy to https://remote.domain.com/owa. As soon as all mailboxes have been migrated to the new server the old Exchange Server is no longer needed and does not play a role anymore in the down proxy mechanism.
     
    Hope this helps?
    Chris Bridges

    HI Mariette,

    Can i just confirm the URL's you have started for accessing e-mail with for the Exchange migraton

    a) OLD SBS2011 server

    email URL : https://remote.domain.com
    OR
    email URL : https://mail.domain.com

    b) NEW Ex2016 server

    email URL : https://mail.domain.com

    When it gets to having completed section 9 ( Configure service point connector) if the recipient has not yet migrated, and is still on the SBS2011 server, if i launch the clients outlook connection status ( by "CTRL" and right click the outlook icon in system tray), would you expect the Server name to be the SBS2011 hostname, or the new EX2016 server hostname at this point ?

    replied 11/05/2019 08:07
    Mariette Knap

    Chris,

    For OWA to work it does not matter where the mailboxes are if the new Exchange Server is leading. If you go to https://mail.domain.com and the mailbox is still on the SBS you will that OWA 'old style' will open. If the mailbox has been migrated it will show the new blue OWA version.

    For Outlook clients it is a bit different. If the mailbox is still on the old Exchange Server nothing will change. You will still see it is connected to the old Exchange Server, you can see that in the profile properties also. It will show something like 'oldhostname' which is the SBS. Once the mailbox has been migrated you will something completely different. The server name will show the https://mail.domain.com and then something with /?MailboxId=2c1c29bd-0b07-4b43-96f7-d38104653d....

    replied 11/05/2019 08:32
    Chris Bridges

    Well,

    prior to migrating a test user account, then Outlook client worked fine.

    Now have migrated a single test account, and eventually Ex2016 migrated successfully, however outlook can no longer connect to exchange, and keeps on asking for the password ?

    Trying the outlook client test email autoconfiguration, after about 30 seconds it responds

    Protocol : SMTP
    Server : Mail.domain.com
    Port 587
    Login Name <Username>
    SPA : Yes
    Authentication Required : Yes

    Tried shutting down outlook, re-booting client. no luck ?

     

    replied 11/05/2019 19:26
    Mariette Knap

    Do you have public folders on the Exchange Server 2010?

    replied 11/05/2019 19:39
    Mariette Knap

    And what is that you try to do? We don't use port 587 anywhere when you connect Outlook to Exchange Server 2016.

    replied 11/05/2019 19:41
    Chris Bridges

    Hi, no public folders, and just simply trying to open outlook, like I said it worked before the recipient was migrated.

    This is on premises and internal lan based. 

    The only other possible clue is when in EX2016 I open the recipient details it still complains it cant find the OU.

    The user is held in Aduc under domain/Users CN

    replied 11/05/2019 19:56
    Reply
    replied 10/31/2019 09:46
  • Chris Bridges

    Finally resolved this. 

    Re-booting the SBS2011 server has now  allowed the migrated mailbox to be opened on outlook on the client.

     

    answered 11/07/2019 08:00
    Add Comment
    Mariette Knap

    OK, sometimes the SBS can be stubborn :)

    Reply
    replied 11/07/2019 08:31
Add an Answer