How to move server agent to another server and maintain existing syncing

Server agent can be used to migrate local CIFS share/attach local folder to the cloud. Admin can also attach CIFS share and link cloud folders to local, via Server Agent.

In these scenarios, the server agent will sync the local folder/remote CIFS share with cloud folders.

Sometimes, an admin may need to stop the machine where the server agent runs, and move the server agent to a new server while maintaining the sync configuration. Since the old server agent in this process is already syncing data from on-premise to the cloud, it is not possible to configure a new sync share with a folder name that already exists in the cloud. This gives the impression that all of the data needs to be synchronized all over again with a new folder name. 

In that case, please follow the procedure below. Keep in mind, only follow the procedure when:

1. The sync on the old server no longer needs to be maintained.
2. The local folders on the new server are on the same drive, under the same folder.
3. The new server does not have any existing local folder/remote CIFS shares in sync via server agent.
4. If you don't want server agent to resync the data which is already in sync, can use other 3rd party tool to sync the local folders on the new server with the  same folders on the old server.

To move the server agent to a new server:

• On the old server, check the task manager from the server agent management console. Make sure there are no pending/pending retry subtasks. The local and cloud folders are already in sync.
• If the attachment is  Attached/Linked to local a folder, make sure the same local folders are on the new server, under the same drive/folder. And 'SYSTEM' user has full control over the local folders.
• If the old server has a remote CIFS share attached, verify the new server can access the CIFS share via the same UNC path.
• Stop server agent service (Cloud Access Service) on both old and new servers.

Alternatively, this PowerShell Command from an Elevated PS Session can be used to pause the Service on each server:

       (Get-Service -Name GladGroupSvc | Stop-Service -verbose -PassThru) | Get-Service

• On the new server, go to C:\ProgramData\gteamclient. Rename gsettings.db here as a backup.
• Copy gsettings.db from the old server, under C:\ProgramData\gteamclient, to the same location on the new server.
• On the old server, open Registry Editor. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Gladinet.
• Copy the value for DropFolderLocalId. It should be a GUID like {CB0AB4E8-5000-47FA-9CC6-21BC4476252D}.
• On the new server, open Registry Editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Gladinet.
• Save the current value for 'DropFolderLocalId', just in case.
• Copy the value from the old server here. In the example, 'DropFolderLocalId' is '{CB0AB4E8-5000-47FA-9CC6-21BC4476252D}' on both old and new server, after the copy.
• Save the change and close the registry editor.
• On the new server, restart the server agent service.
• Launch the Agent Management Console, and navigate to the Attached Folders tab. The attached local folder/remote CIFS share/linked local folder should reflect those of the old server. 
• Verify the sync between local and cloud still works. Add a new file locally and it should sync to the cloud automatically. Upload a new file via the web portal, and it should be sync down to on-premise.
• On the old server, uninstall the server agent and reboot, to avoid starting the cloud access service and starting syncing old files to the cloud unintentionally.