cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating EV to a new domain

STrossbach
Level 2

We are in the process of collapsing our AD domains into one and need to migrate an instance of EV it's existing domain into the new domain.  The EV instance is a legacy instance, used at this point only to store historical data and does not have any active journaling going on.  Our goal is to accomplish this move using the easiest method with the least risk to losing access to the data.  The AD Migration team is using Quest Migration Manager to perform the domain migrations.  Some of the tehcnical changes they are making that they said might impact other applications are: 

 1) Changing server membership from xxx.net to yyy.net  (Re-permission objects on server (files, shares, printers, user groups, services, registry and scheduled tasks ))
2) Changing any embedded credentials (user access) within databases
3) Changing any mail-enabled applications from xxx.net to yyy.net exchange services (SMTP.xxx.net -> SMTP.yyy.net)
4) Changing any active directory-enabled applications from xxx.net to yyy.net exchange services 

 

So my questions are:  Has anyone migrated EV to a new domain before, and if so, what approach did they use?  Does anyone see any issues with this approach outlined above?  Are there things we should look out for if we do this?   What are the risks?

 

We have a duplicate instance of this KVS on another server as a failover server, so we have somewhat of a fallback if there are issues, but want to make sure we truly understand the risks.  Any help or experience anyone can share regarding this would be appreciated.

1 REPLY 1

MichelZ
Level 6
Partner Accredited Certified
Hi there Would you mind telling us how you solved this problem? Cheers

cloudficient - EV Migration, creators of EVComplete.