Migrate domain to a new server

Every now and then you will want to, or have to, migrate an AD from from domain controller to another. You can just uninstall TechIDAgent from the old one and install it on the new one and everything will work. You will see two lines in the TechIDClient. One of the installation on the old domain controller and one for the installation on the new domain controller. You can also tell TechIDManager that they are the same domain and avoid that slight bit of confusion. There is an internal identifier called the TechIDAgentGuid that is used to identify each domain, and an RSA key pair used to secure the access of the agent. It is possible to set these when migrating an AD to a new server to keep history and stuff contiguous. To do this you need to set the new server to have the same TechIDAgentGuid and RSA key as the old server. If the old server died and it can’t be accessed then you need to follow a different set of instructions: https://techidmanager.com/migrate-domain-to-new-server-when-old-server-has-died/.

On the old server from an administrative command line run:

TechIDAgent.exe show
TechIDAgent.exe ShowDomainPrivateKey

Make note of the TechIDAgentGuid listed in the output, and the Domain <RSAKeyValue>…</RSAKeyValue>. They both need to be copied to the new server.

Before installing and starting the TechIDAgent on the new server, it should be stopped and uninstalled on the old server.

TechIDAgent.exe stop uninstall

On the new server from an administrative command line, before doing anything else related to TechIDAgent, run this and replace xxxxxx with the DomainGuid from the old server, and the <RSAKeyValue> with the private key from the old server. The use of quotes (“) is required.

TechIDAgent.exe DomainGuid xxxxxxx
TechIDAgent.exe SetDomainPrivateKey “<RSAKeyVal…</RSAKeyValue>”

Now install the TechIDAgent as usual on the new server. Other settings such as FriendlyName and RMMName should be brought over in the same manner as DomainGuid.

TechIDAgent.exe install
TechIDAgent.exe ClientGuid yyyyyyy
etc…
TechIDAgent.exe start

Migrating Additional TechIDAgent Instances

The instructions above cover migrating the Default TechIDAgent instance. If you have additional instances installed, such as a Shared User instance, each instance must be migrated separately, one at a time.

The migration process is the same as for the Default instance. The only difference is that each command must specify the instance being migrated.

For the following examples, we will use a Shared User instance named TechID-QA-Shared.

Retrieve the Instance Information from the Old Server

On the old server, open an administrative command prompt and run:

TechIDAgent.exe shareduser TechID-QA-Shared show
TechIDAgent.exe shareduser TechID-QA-Shared ShowDomainPrivateKey

Record the TechIDAgentGuid and the Domain RSA private key (<RSAKeyValue>…</RSAKeyValue>) from the output. Both values must be transferred to the new server.

Stop and Uninstall the Instance from the Old Server

Before installing the instance on the new server, stop and uninstall it from the old server:

TechIDAgent.exe shareduser TechID-QA-Shared stop uninstall

Configure the Instance on the New Server

On the new server, open an administrative command prompt.

Before installing or starting the instance, configure it using the DomainGuid and RSA private key obtained from the old server:

TechIDAgent.exe shareduser TechID-QA-Shared DomainGuid xxxxxxx
TechIDAgent.exe shareduser TechID-QA-Shared SetDomainPrivateKey “<RSAKeyValue>…</RSAKeyValue>”

Replace xxxxxxx with the TechIDAgentGuid from the old server and the RSAKeyValue with the complete private key.

Important: The quotation marks surrounding the RSA private key are required.

Install and Start the Instance on the New Server

Install and configure the instance as usual:

TechIDAgent.exe shareduser TechID-QA-Shared install
TechIDAgent.exe shareduser TechID-QA-Shared ClientGuid yyyyyyy
TechIDAgent.exe shareduser TechID-QA-Shared start

Transfer Any Non-Default Instance Settings

Any non-default settings configured on the old instance must also be carried over to the new server. This includes settings such as Just-in-Time (JIT) access, FriendlyName, RMMName, and any other customized configuration options.

Review the configuration of each instance before migrating it to ensure all settings are preserved.

Repeat for Any Remaining Instances

If multiple additional instances exist, repeat the process for each one, completing the migration of one instance before moving on to the next.

Each instance must use its own TechIDAgentGuid and RSA private key from the old server.

Important: Always verify that commands are targeting the correct instance. Mixing the identifiers or RSA private keys between instances can cause problems with domain identification and authentication.

We at Ruffian Software Inc. attempt to provide a white glove installation service and support. We are happy to setup a meeting to do all these steps with you, and anyone in your company. If you want help, then book installation assistance.

Any questions – support@ruffiansoftware.com