Home

Exchange 2016 Conversion

%3CLINGO-SUB%20id%3D%22lingo-sub-206840%22%20slang%3D%22en-US%22%3EExchange%202016%20Conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206840%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20customer%20who%20is%20looking%20at%20deploying%20an%20Exchange%202016%20DAG%20on%20VMWare%2C%20however%2C%20have%20a%20requirement%20to%20migrate%20to%20Hyper-V%20when%20the%20platform%20is%20ready.%3C%2FP%3E%3CP%3EMy%20guess%20is%20that%20converting%20Exchange%20members%20as%20part%20of%20a%20DAG%20from%20vmdk%20to%20vhdx%20shouldn't%20even%20be%20considered%20given%20the%20changes%20to%20the%20disk%20architecture%3F%20(underlying%20storage%20will%20also%20change%20as%20they%20will%20be%20moving%20to%20a%20new%20SAN%20solution).%3C%2FP%3E%3CP%3EWould%20the%20best%20approach%20here%20be%20deploy%20new%20Exchange%202016%20servers%20on%20the%20Hyper-V%20platform%20and%20migrate%20the%20mailboxes%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-206840%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216894%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216894%22%20slang%3D%22en-US%22%3EThe%20best%20approach%20will%20be%20a%20%22like%20for%20like%22%20server%20migration.%20Much%20lower%20risk%2C%20and%20will%20be%20less%20disruptive%20to%20your%20users.%20In%20fact%20they%20will%20barely%20even%20know%20its%20happened.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216752%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216752%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3Eeven%20though%20that%20it's%20technical%20possible%2C%20I'd%20prefer%20to%20setup%20new%20servers%20on%20the%20new%20hypervisor%2C%20as%20do%20not%20have%20any%20information%20if%20there%20any%20issues%20with%20the%20remaining%20drivers%20of%20the%20old%20hypervisor.%3C%2FP%3E%0A%3CP%3EAt%20least%20I'd%20create%20new%20data%20volumes%20following%20the%20recommended%20architecture.%20I%20guess%20that%20the%20storage%20itself%20is%20provided%20in%20a%20different%20way%20than%20it%20was%20in%20the%20old%20hypervisor%20platform.%3C%2FP%3E%0A%3CP%3E-Thomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214700%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214700%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206859%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Conversion%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206859%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20reason%20you%20couldn't%20do%20that.%20Found%20an%20older%20article%20but%20it%20should%20be%20similar.%20See%20answer%20in%20this%20article%3A%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F625473-exchange-server-migrate-from-vmware-to-hyper-v%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F625473-exchange-server-migrate-from-vmware-to-hyper-v%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Hambik Matvosian
Occasional Contributor

Hi All,

 

I have a customer who is looking at deploying an Exchange 2016 DAG on VMWare, however, have a requirement to migrate to Hyper-V when the platform is ready.

My guess is that converting Exchange members as part of a DAG from vmdk to vhdx shouldn't even be considered given the changes to the disk architecture? (underlying storage will also change as they will be moving to a new SAN solution).

Would the best approach here be deploy new Exchange 2016 servers on the Hyper-V platform and migrate the mailboxes?

 

 

Thank you

 

4 Replies

No reason you couldn't do that. Found an older article but it should be similar. See answer in this article: https://community.spiceworks.com/topic/625473-exchange-server-migrate-from-vmware-to-hyper-v

Thank you!

Hi,

even though that it's technical possible, I'd prefer to setup new servers on the new hypervisor, as do not have any information if there any issues with the remaining drivers of the old hypervisor.

At least I'd create new data volumes following the recommended architecture. I guess that the storage itself is provided in a different way than it was in the old hypervisor platform.

-Thomas

The best approach will be a "like for like" server migration. Much lower risk, and will be less disruptive to your users. In fact they will barely even know its happened.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Discussion - Updating our interface with Fluent touches
Elliot Kirk in Discussions on
102 Replies