Migrating the configuration store form AD LDS to MS SQL Server, run the GPOADmin.ConfigMig.exe with no error with the /T flag, when used without the test mode On it fails creating the version container.
Migration log show all of the containers are failing, either due to an SQL connection timeout, or potentially a blank property on the containers that we expect to exist. In this instance the most likely cause is the connection and command timeout values.
Open the registry on the GPOADmin server and navigate to "HKLM/SOFTWARE/Quest/GPOADmin/VCConfig"
Edit the values of "CommandTimeout" and "ConnectionTimeout" to larger values. These are represented in seconds. We would recommend extending both to at least 600 seconds (10 minutes) and try to migrate again. These can be increased in successive runs if we keep encountering SQL timeouts when attempting the migration.
If it keeps timing out on the container migration, and the basic containers (VCRoot, Protected Settings Root, Lost and Found) are not appearing might be the case that the SQL database was created from the scripts, and did not execute the 'InitializeDatabase' stored procedure.
Open SQL management studio and execute the stored procedure [dbo].[InitializeDatabase] against the GPOADmin database. After this is complete run the migration again, the missing containers may be the source of the timeout as the timeout values have been increased already.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center