Insync client failed to activate using IMDv2
Problem description
This article will help you troubleshoot issues with activating the insync client using IMDv2.
IMDv2 script will run successfully, however the client will not get activated.
Cause
When the IMD token is saved in the registry, the values of the hostname and the email of the user are saved in it.
Register keys paths:- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Druva Software
Traceback
From insync client.log -
[2022-07-08 15:06:10,359] [ERROR] win32, Auto deployment failed: you seem to have activated this device before this. You will need to re-run the auto deployment msiexec command with proper parameters.
From insyncclientGUI.log -
[2022-07-08 14:55:32,664] [INFO] inSync Debug Server Agent serving on 127.0.0.1:59880
[2022-07-08 14:55:32,690] [INFO] Getting AD Info for user name: <Domain name>\<User name>
[2022-07-08 14:55:32,690] [INFO] sid: S-1-5-21-2089150009-1795477150-2862006797-1485
[2022-07-08 14:55:33,987] [INFO] AD Info fetched ok for user: <User name>
[2022-07-08 14:55:33,990] [INFO] IMD: found token at path 'Software\Druva Software\inSync\mass_deployment_enc_v2'
[2022-07-08 14:55:33,990] [INFO] IMD Details: email:<User email address>, massDeploy_ver: 2, objectSID_found: True
Resolution
- A user can only activate the device once with the same token. (Token saved in the registry after appending email.) Hence they would need to clear the registry and re-run IMD.
- The parameter that checks this is called 'usedonce' and can be found in the clientgui log. You will see true as its value if the user's email is in the registry token.
Script to clean inSync