This article applies to:
• OS: Windows
• Product edition: inSync Cloud and inSync On-Premise
inSync Client reactivation fails under following conditions while performing Integrated Mass Deployment (IMD) v2:
- Activate only the first device for every user setting is enabled under Settings > Mass Deployment tab.
- Old mass deployment token exists in the device registry.
Error log location on client device: C:\ProgramData\Druva\inSync4\users\username\logs\inSyncClientGUI
The following traceback is logged inside inSyncClientGUI folder:
“[ERROR] 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.”
The event viewer log entry appears as below:
Log Name: Application
Source: Druva inSync
Event ID: 167
Task Category: (1)
Error 167. The activation for user “username” failed. For more information on this error, see Integrated mass deployment error messages.
The mass deployment token residing in the device registry, which may be a stale entry, prevents reactivation of the device with the same user ID (email address).
The Activate only the first device for every user setting plays an important role as it prevents activation of more than one user on the same device. Even a "replace" script does not reactivate the device, as the mass deployment token is already present in the device registry. Since inSync already has the information about the device being activated once for the user during IMD, it prevents reactivation of the device because the Activate only the first device for every user setting is enabled.
To reactivate a device after IMDv2 using the same mass deployment token:
- Login to inSync Management Console as an administrator.
- Click Settings > Mass Deployment tab and click Edit.
- Uncheck (or disable) the Activate only the first device for every user checkbox. This is a temporary setting.
This change in the setting will allow you to reactivate and replace the device.
If Activate only the first device for every user is not disabled, the device will not reactivate even after deleting the token entry from the registry of the affected device irrespective of whether the deployment token used is new or stale. The following traceback will help you identify the same:
[ERROR] RPC to server failed, fault: Only first device is allowed to be activated during mass deployment. (#1000000a7)
[ERROR] [IMD] Auto-install failed: Only first device is allowed to be activated during mass deployment. (#1000000a7)
- Once the device reactivation is complete, select (or enable) the Activate only the first device for every user setting.
- Delete the existing (or stale) mass deployment token from the device registry (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Druva Software\inSync\mass_deployment_enc_V2)
- You can manually delete the token from the above-stated location only if 1 or 2 clients are impacted.
- If several users are impacted, you can create a script and use the deployment tool in your environment to replace the devices. You can use the following parameters in your script to delete the token from the affected devices.
Note: Back up the device registry before affecting any changes to it.
On 32 bit devices:
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Druva Software\inSync" /f
On 64 bit devices:
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Druva Software\inSync" /f
- Run the IMD script again with the same mass deployment token and set the REPLACE_DEVICE flag to YES.
msiexec /qn /i <path to inSync msi> TOKENV2='<mass deployment token>' SERVERLIST="<cloud.druva.com:port number>" REPLACE_DEVICE=YES
Note: For IMDv2, the token must be enclosed in single quotation marks (').
You can use the existing mass deployment token or create a new deployment token to reactivate the affected user. Generating a new deployment token will not affect/disable the users which are already activated with the old token. The user will be able to communicate with the server and the backups would complete successfully.
Note: If you have generated a new mass deployment token, you would need to use the new token for IMD on all the new devices in future. In case you have a custom script for the same, the must be updated in the script to avoid deployment failure.