Hi all,
I'm a migration consultant about to begin a domain consolidation in which I will need to migrate a functioning 1C server into another domain within the same forest. I will be using the Quest Migrator Pro for AD tool to perform this. The tool has a server agent which can process & re-ACL most standard Windows elements such as file system, user profiles, services, scheduled tasks etc. There is also a SQL agent which can update database permissions.
Are there any other aspects I need to be aware of? - any special considerations, config files, etc that would need to be updated in addition to the above?
I'm looking to be aware of any gotcha's which might cause issues after I have joined the 1C server to the new domain... has anyone done this previously?
Many thanks in advance for any insights!

Regards

PaulG.

Hi Paul!

Migrating a 1C application to another domain is not a complicated task. Unfortunately, I haven’t worked with the “Quest Migrator Pro” solution myself, but if it supports migrating SQL databases, that should be sufficient.

You should pay attention to the following points:

How is authentication currently configured in the 1C application? Is it simple username/password authentication, or is domain-based authentication being used?

When migrating the 1C application to another domain, you will most likely need to update your 1C license, as the license is “bound” to a specific server.

Otherwise, the process is straightforward: migrate the SQL database, install the 1C server in the new environment, configure the database connection in the server console, and, if required, update the license using additional PIN codes.