Skip to main content
Device replace for Active Directory (AD) and SCIM users
Updated over a week ago

Overview

As an administrator, you can perform the device replace process, for an AD user. In this process, you will mark the required device for replace, run IMD commands to install inSync Client on the user's new device and restore data on the new device. Once this process is complete, you will ship the new device to the user.

Prerequisites

  • Adequate disk space should be available on the C\: drive on the new device.

Procedure

In this workflow, as an inSync administrator you will replace and migrate the data from the old device to the new device on behalf of the user.You need to configure inSync Client for IMD with the new FOR_USER, FOR_DEVICE parameters, along with current optional RESTORE_SYSTEM_SETTINGS parameter.You need to run the IMD commands to trigger device replace for AD users on Windows and MAC OS.


๐Ÿ“ Note
โ€‹ In IMD ifADD_NEW_DEVICE parameter has been set to "YES" then the administrator will add a new device for the user in inSync Client instead of replacing the old device. Meanwhile the user can continue to take backups on the old device. inSync Client will retain both the device details till the administrator decides to deactivate or delete the older device.For more information see Add new device workflow.


The devicer epla ceworkflow for AD users is as follows:

inSync Administrator actions:

  1. On the inSync Management console, marks the device which needs to be replaced starts the device replace process.

If theADD_NEW_DEVICEparameter has been set to "YES"then the administrator will add a new device for the user instead of replacing the old device.

System Administrator actions:

  1. Using IMD, installs inSync Client on the user's new device and logs into the new device.

  2. inSync Client restores all the data on the new device.

After this step, the new device is ready to be shipped to the user.

User actions:

  1. Using Active Directory credentials, logs in to the new device.

  2. The inSync Client restores system settings and MAPI data. inSync Client then moves the restored data which is saved at the temporary location to relevant paths and folders as required.

The device is now ready to be used.


๐Ÿ“ Note
โ€‹ Incase of all drives, the home directory path needs to be the same on both devices. If the home directory paths are different, then the data will be restored to the new device but will not be moved.


IMD commands to be run

On Windows

The inSync client executable is located on a shared network. You can run the following command by using an automated installation tool:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" FOR_DEVICE="<old device name>" FOR_USER= "<inSync user's email id>"

If you want to restore system settings as well then the command is:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" FOR_DEVICE="<old device name>" FOR_USER= "<inSync user's email id>" RESTORE_SYSTEM_SETTINGS= "Yes"

For example

msiexec /qn /i"\\sharelocation\inSync.msi"TOKENV2='33-bb0af8c55da3f9ddxxxx'SERVERLIST="cloud.druva.com:443" FOR_USER=" ernie.carter@sample.org " FOR_DEVICE="DDSPL1xxxx"

If you want to add a new device for the user then the command is:

TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" FOR_USER= "<inSync user's email id>โ€ ADD_NEW_DEVICE= โ€œYes"msiexec.exe /qn /i inSync.msi TOKENV2='1-33-bb0af8c55da3f9ddxxxx' SERVERLIST="cloud.druva.com:443" FOR_USER="ernie.carter@sample.org" FOR_DEVICE="DDSPLxxxx" ADD_NEW_DEVICE=โ€Yesโ€

On macOS

inSync Client 6.2.0 and earlier

You need to install the inSync Client on the device either manually or installation tool before you run the following IMD command:

cd /Applications/Druva\ inSync/inSync.app/Contents/MacOS

For example

./inSync -t "1-10e3b492ebf60232654f20e583c465ed89a32d23683360dxxxxx" -m "ernie.drtst.org:443" --for-device "DDSPLxxxx" --for-user " ernie.carter@abc.org " --restore-system-settings Yes

If you want to add a new device for the user then the command is:

cd /Applications/Druva\ inSync/inSync.app/Contents/MacOS

For example

/inSync -t "1-33-bb0af8c55da3f9ddxxxx" -m deviceref.drtst.org:443 --for-device "device1" --for-user "user@druva.org"--add-new-device Yes

After the IMD command is run, the device replace process is initiated. You can check the device replace status on the Device Details page. Once this process starts successfully, the old device will be deactivated.

The user data is restored to the temporary location. For more information see Temporary location directories for restored data.

After the data restore is finished, the device is ready to be shipped to the user. The user needs to login to the device to complete the device replace process For more information, see Remotely replace a device linked to your inSync account.

inSync Client 6.5.0

You need to install the inSync Client on the device either manually or installation tool before you run the following IMD command:

cd /Applications/Druva\ inSync.app/Contents/MacOS

For example

./inSync -t "1-10e3b492ebf60232654f20e583c465ed89a32d23683360dxxxxx" -m "ernie.drtst.org:443" --for-device "DDSPLxxxx" --for-user " ernie.carter@abc.org " --restore-system-settings Yes

If you want to add a new device for the user then the command is:

cd /Applications/Druva\ inSync.app/Contents/MacOS

For example

/inSync -t "1-33-bb0af8c55da3f9ddxxxx" -m deviceref.drtst.org:443 --for-device "device1" --for-user "user@druva.org"--add-new-device Yes

After the IMD command is run, the device replace process is initiated. You can check the device replace status on the Device Details page. Once this process starts successfully, the old device will be deactivated.

The user data is restored to the temporary location. For more information see Temporary location directories for restored data.

After the data restore is finished, the device is ready to be shipped to the user. The user needs to login to the device to complete the device replace process. For more information, see Manage data after device remote device refresh.

Did this answer your question?