📝 Note
This article applies to
• OS: Windows
• Product edition: inSync Cloud and inSync On-Premise
Problem description
inSync Client reactivation fails under the following conditions while performing Mass Deployment using AD/LDAP when
Activate only the first device for every user setting is enabled
An old mass deployment token exists in the device registry.
Error log location on client device:
C:\ProgramData\Druva\inSync4\users\<username>\logs\inSyncClientGUI
Traceback
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:
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).
Resolution
To reactivate a device after IMDv2 using the same mass deployment token:
On the Endpoint workload page, select Mass Deployment.
In the Mass Deployment Settings section, Click on Edit
3. Uncheck the “Activate only the first device for every user”.
4. Click On Save
If Activate only the first device for every user is not disabled, In that case, 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:
📝 Note
[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)
To fix this you need to perform clean uninstallation of the client and reactivate the client. Please refer the KB