exchange, office 365

Hi,

you don't need to create legacy name for migration from 2010/2013 to Office 365.

Are you planning to have more then 1 Exchange server, or you are planning to migrate to Office 365?
If you are going for DAG, then you cant use NLB on those servers, but CAS can use DNS round robin, which works ok (not perfect, but ok).

PS: You don't need legacy name. That name is used when migrating from Exchange 2003 to 2007/2010.

How to do a staged migration of 2007 to Office 365, can be found here: https://support.office.com/en-us/article/Perform-a-staged-migration-of-email-to-Office-365-83bc0b69-de47-4cc4-a57d-47e478e4894e?ui=en-US&rs=en-US&ad=US 

If I am not mistaking, you have a lot of users, so you cannot perform cutover migration.

Regards,
Ivan.

"Upgrading to Exchange 2010 would have the least impact on users.  Going the 2010 route still would still enable GNC to migrate to Office 365.

•      Exchange 2010 Support end on January 2020
•      Office 365 supports Exchange 2010 in a hybrid solution
o      Enables GNC to migrate accounts to Office 365 with minimal to zero impact on the user
•      No need to create the “legacy” namespace
•      Similar architecture to 2013/2016 for redundancy
•      Windows Network Load Balancing will work with Exchange 2010.
o      Windows NLB will cater basic Load Balancing requirements for small level environments but never to be confused with High-availability. Whenever you have requirements such as High-Availability on Web Layer, Real-time Filtering, Monitoring, and Security the only option is Hardware/Virtual Load Balancer which gives all in one."

I got thise xpert comment from my consultant regarding exchange 2010 to office 365, I was referring to legacy namespace?

so you say there is no legacy name space require when migrating either from exchange 2010 or exchange 2013 to office 365

Hi,

the man is right. If you want to do a Hybrid configuration/ migration, then you need 2010/ 2013.
Same for NLB.

so why he has specifically highlighted for exchange 2010 , for exchange 2013 there is also no legacy name space required?

he is referring advantage of having exchange 2010 over exchange 2013 in middle for hybrid migration to office 365

which I don't see any reason why you should keep exchange 2010 and not exchange 2013 in middle

Do you have more then 1 Exchange 2007 right now, when you are planning to deploy multiple 2010/2013 server, before going to Office 365?

ivan can you answer my above thread please , kindly be specific to what I have asked

yes we have 5 exchange servers each is different AD site

so why he has specifically highlighted for exchange 2010 , for exchange 2013 there is also no legacy name space required for office 365

 he is referring advantage of having exchange 2010 over exchange 2013 in middle for hybrid migration to office 365

 which I don't see any reason why you should keep exchange 2010 and not exchange 2013 in middle

A key point is that there is no silent redirection for OWA so users would have to sign in twice if redirected. I typically tell users that the new OWA is outlook.office.com (if they have been migrated).  You might be able to use an F5 to look at AD Attributes to determine if users has been migrated (targetaddress attribute) and thus have the URL remapped.. but that is another discussion entirely :-)

You should upgrade to Exchange 2010 or 2013 so you can have a hybrid...

There used to be a recommendation for legacy namespaces but that stopped a year or two ago.  I would absolutely recommend you walk through each possible scenario in the Exchange Deployment Assistant. It basically tells you how to do the migration... It is a great tool:

https://technet.microsoft.com/en-us/office/dn756393.aspx