Advice for Exchange Server Migration + consultancy / support recommendations

%3CLINGO-SUB%20id%3D%22lingo-sub-3026973%22%20slang%3D%22en-US%22%3EAdvice%20for%20Exchange%20Server%20Migration%20%2B%20consultancy%20%2F%20support%20recommendations%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3026973%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20had%20a%20couple%20of%20issues%20in%20October%20with%20the%20Exchange%20Transport%20Service%20getting%20stuck%20in%20a%20%22starting%22%20state%20on%20our%20Exchange%20server%2C%20which%20resulted%20in%202%20weeks%20of%20interrupted%20email%20use%20for%20our%20clients.%20We%20didn't%20actually%20fix%20the%20underlying%20problem%20but%20did%20get%20the%20server%20back%20up%20and%20running%20after%20restoring%20a%20previous%20version.%20Due%20to%20that%20we%20feel%20uneasy%20about%20the%20current%20setup%20and%20would%20like%20to%20migrate%20our%20data%20to%20a%20new%20Exchange%20server.%26nbsp%3B%20%3CLINK%20to%3D%22%22%20issues%3D%22%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ECurrent%20Environment%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3EWindows%20Server%202012%20R2%20(Version%206.3%20Build%209600)%20running%20Exchange%20Server%202013%20(Version%2015.00.1497.023)%20virtualised%20(Hyper-V).%3C%2FLI%3E%3CUL%3E%3CLI%3E~1.3TB%20of%20databases%20split%20across%20public%20folders%20edb%20(which%20has%2010K%20folders)%20and%20user%20mailbox%20edb.%20(roughly%20650GB%20each)%3C%2FLI%3E%3C%2FUL%3E%3CLI%3EThis%20server%20runs%20all%20of%20the%20exchange%20services%3C%2FLI%3E%3CLI%3EPDC%20is%20on%20another%20VM%3C%2FLI%3E%3CLI%3EDNS%20Server%20is%20on%20another%20VM%3C%2FLI%3E%3CLI%3E60%20Users%20all%20using%20Outlook%20(2013%20or%202016)%3C%2FLI%3E%3CLI%3EAll%20external%20e-mail%20is%20in%20%2F%20out%20via%20Mimecast%20cloud%20services.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20purchased%20a%20new%20host%20server%20(PowerEdge%20r740)%20that%20currently%20only%20contains%20a%20WSUS%20VM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20think%20we%20should%20create%20a%20new%20Exchange%20VM%20on%20the%20new%20host%2C%20and%20then%20migrate%20all%20of%20the%20data%20from%20the%20current%20Exchange%20server%20over.%20If%20we%20DIY'd%20it%20we%20would%20just%20install%20Exc2013%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20we%20only%20look%20after%201%20site%20with%201%20Exchange%20server%2C%20so%20we%20do%20not%20have%20a%20great%20deal%20of%20knowledge%20when%20it%20comes%20to%20Exchange%20migrations%20and%20would%20potentially%20be%20looking%20at%20getting%20a%203rd%20party%20to%20do%20%2F%20assist%20with%20the%20migration%20with%20us%20as%20spectators%20or%20us%20being%20the%20hands%20with%203rd%20heavily%20involved%20%2F%20on%20hand.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe'd%20also%20be%20interested%20in%20ongoing%20Exchange%20support%2Fguidance%2C%20the%20company%20is%20UK%20based%20(South%20East)%20so%20it%20would%20be%20beneficial%20if%20the%20support%20came%20from%20people%20fairly%20local%20in%20case%20there%20was%20anything%20onsite%20that%20needed%20to%20happen.%26nbsp%3B%20We%20have%20a%20similar%20arrangement%20with%20our%20phone%20supplier%2C%20i.e.%20we%20triage%20%2F%201st%20line%20%2F%20minor%20mods%20and%20liaise%20with%20the%20phone%20company%2C%20which%20keeps%20the%20client%20happy%20and%20reduces%20the%20time%20and%20FAFF%20overhead%20down%20for%20the%20supplier.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20some%20point%20we%20would%20be%20looking%20at%20re-evaluating%20the%20set%20up%20w.r.t.%20hosted%20Exchange%2C%20but%20we%20heavily%26nbsp%3B%20use%20public%20folders%20so%20we%20would%20need%20to%20find%20a%20solution%20for%20what%20to%20do%20with%20those%20first.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20anyone%20has%20any%20advice%20or%20recommendations%20or%20able%2Fwilling%20to%20step%20into%20the%203rd%20party%20role%2C%20then%20the%20input%20would%20be%20great%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3EDan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3026973%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Hello,

 

We had a couple of issues in October with the Exchange Transport Service getting stuck in a "starting" state on our Exchange server, which resulted in 2 weeks of interrupted email use for our clients. We didn't actually fix the underlying problem but did get the server back up and running after restoring a previous version. Due to that we feel uneasy about the current setup and would like to migrate our data to a new Exchange server.  <link to issues>

 

Current Environment

  • Windows Server 2012 R2 (Version 6.3 Build 9600) running Exchange Server 2013 (Version 15.00.1497.023) virtualised (Hyper-V).
    • ~1.3TB of databases split across public folders edb (which has 10K folders) and user mailbox edb. (roughly 650GB each)
  • This server runs all of the exchange services
  • PDC is on another VM
  • DNS Server is on another VM
  • 60 Users all using Outlook (2013 or 2016)
  • All external e-mail is in / out via Mimecast cloud services.

 

We have purchased a new host server (PowerEdge r740) that currently only contains a WSUS VM.

 

We think we should create a new Exchange VM on the new host, and then migrate all of the data from the current Exchange server over. If we DIY'd it we would just install Exc2013 again.

 

Currently we only look after 1 site with 1 Exchange server, so we do not have a great deal of knowledge when it comes to Exchange migrations and would potentially be looking at getting a 3rd party to do / assist with the migration with us as spectators or us being the hands with 3rd heavily involved / on hand.

 

We'd also be interested in ongoing Exchange support/guidance, the company is UK based (South East) so it would be beneficial if the support came from people fairly local in case there was anything onsite that needed to happen.  We have a similar arrangement with our phone supplier, i.e. we triage / 1st line / minor mods and liaise with the phone company, which keeps the client happy and reduces the time and FAFF overhead down for the supplier.

 

At some point we would be looking at re-evaluating the set up w.r.t. hosted Exchange, but we heavily  use public folders so we would need to find a solution for what to do with those first.

 

If anyone has any advice or recommendations or able/willing to step into the 3rd party role, then the input would be great appreciated.

 

Thank you,

Dan

1 Reply
Hey Dan,

Exchange 2013 will be OOS in a couple of years I will recommend you to proceed with Exchange 2019 setup instead.

Can you send me the details of your company in Private Chat. I will check internally to see if we can align any Microsoft CE who can help you help you with the request.