You have one or more GPOADmin servers with local AD LDS instances to host the Version Control Store and GPOADmin configuration.
You plan to migrate the GPOADmin configuration to a new server. Consider adding a new AD LDS instance and set it up as a replication partner is not an option in this scenario.
Reasons for migration could include:
Want to switch to a new operating system i.e. from Windows 2008 R2 Server to Windows 2012 R2 Server
Current AD LDS instance causes issues, however, the actual data is consistent
Steps to migrate the GPOADmin configuration data in AD LDS to a new server:
1. Export the GPOADmin configuration from the current AD LDS instance.
NOTE: You may have to change the port number (50000). You MUST change the AD LDS instance ID to your actual AD LDS instance ID. To find the current AD LDS instance ID you can use ADSI Managed Console (adsiedit.msc).
2. Install GPOADmin and target the new AD LDS instance.
NOTE: Do not export a GPOADmin 5.9 configuration when connecting with a GPOADmin Client 5.11. The version of GPOADmin should match the AD LDS data. The initial configuration must be performed in order to prepare the AD LDS schema.
3. Import the GPOADmin configuration into the new AD LDS instance
NOTE: The -k switch will prevent constraint violation errors to block the import. The -c switch is used to replace the context of the configuration partition (-c "
At this stage, you can start the GPOADmin Client again and confirm everything works as expected.
NOTE: Instead of following the export/import method above, you can set up a new server as an AD LDS Replica partner.
After successful setup and replicate a metadata cleanup of the previous AD LDS instance must be performed.