Hybrid Migration from Exchange 2016 to office365

Anonymous
2018-02-15T08:36:09+00:00

Hi MS,

I am in the planing phase of doing 10 users Pilot Hybrid migration to office 365 in E3 plan using our Volume licence.

We have two 2016 exchange servers running in DAG

We also have email filtering done via Mimecast and for purpose of this exercise i want to leave email filtering to mimecast and not use EOP.

I want to get a clear idea of exact steps I need to take to configure this.

However, before I do anything i want to make sure it does't affect our SMTP or any other users from reading tons of articles and some previous experience with office 365 this are the steps i think needs to be performed.

  1. use exchange server deployment assistance

 - check prereq - all good

My questions  Questions are 

On step 14

If i add this TXT record this will not affect any mail flow this is purely for domain verification? 

Question 2

on the step 15 -29 here 

https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=3229-W-EwAIAAAAQAAAAAEAAAAAACAAAABEaAOFAAA~

will that affect any existing mail flow or existing connectors as we have few there

Question 3 

overall understanding is mailflow will still be going through exsting exchange server and other 240 users will not be affected and not other server or services such as smtp, scanning service will be affected due to this. 

We never need to change MX records and we don't have to make any changes to mimecast?

Please clarify these ASAP, would be really appreciated.

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

58 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-26T02:22:21+00:00

    Hi Erick,

    Just a question on Certificate.

    According to the pre-req regarding the certificate

    "Certificates   Install and assign Exchange services to a valid digital certificate purchased from a trusted public certificate authority (CA). Although self-signed certificates should be used for the on-premises federation trust with the Microsoft Federation Gateway, self-signed certificates can’t be used for Exchange services in a hybrid deployment. The Internet Information Services (IIS) instance on the Exchange servers configured in the hybrid deployment must have a valid digital certificate purchased from a trusted CA. Additionally, the EWS external URL and the Autodiscover endpoint specified in your public DNS must be listed in Subject Alternative Name (SAN) of the certificate. The certificate installed on the Exchange servers used for mail transport in the hybrid deployment must all use the same certificate (that is, they are issued by the same CA and have the same subject)."

    We have *.domain.com certificated from RapidSSL SHA256 CA which is installed on IIS and under onr EAC

    both of our internal and external EWS 

    https://mail.domain.com/EWS/Exchange.asmx

    How do i verifiy this part?

    "Autodiscover endpoint specified in your public DNS must be listed in Subject Alternative Name (SAN) of the certificate"

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-25T09:40:59+00:00

    Hi Roy,

    Has my reply answered your questions? Let me know if anything is unclear. 

    Best Regards,

    Erick

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-23T10:06:18+00:00

    Hi Roy,

    The answer is no. You can use the user name for different format, but the UPN must be unique. Based on my experience, if admins use the same username format, it is easier to manage users. I also recommend use the same username format.

    Best Regards,

    Erick

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-23T03:40:06+00:00

    Hi Erick,

    Yes, one more question.

    Some users have logon name as Firstname.Lastname John.smith and some users have firstname and last intial JohnS but all users have ******@domain.com ie ******@domain.com

    Currently we don't have or have a immediate need for ADFS servers for any applications. But in future we will have external applications which we need ADFS for.

    When migrating to office365 with SSO will that affect their login on domain computers? 

    Do I need to have all users to be on the same username format?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-22T07:41:51+00:00

    Hi Roy,

    Do you have any other questions about it? If so, please don't hesitate to let us know. 

    Best Regards,

    Erick

    Was this answer helpful?

    0 comments