Overview
As an administrator, you can perform the device replace process on behalf of the non-AD user. In this process, you will mark the required device for replace, create a user account on the new device, trigger the device replace process which will enable inSync Client to restore the user's data, and once this process is complete, you will ship the new device to the user.
Prerequisites
The home directory path needs to be the same on both devices for user data stored on the source device in its home directory to be restored correctly.
Adequate disk space should be available on the C\: drive on the destination device
Procedure
In this workflow, as an inSync administrator, you need to create a user login on the new device and set a password for it. You log in to the new device using the user’s account credentials to trigger its device replace.
You need to configure inSync client for IMD with the new FOR_USER, FOR_DEVICE and FOR_LOCAL_USER parameters, along with current optional RESTORE_SYSTEM_SETTINGS. You must run the following commands to enable device replace for AD users on Windows and MAC OS.
You can save the command as a .bat file. You can deploy these commands by using a third-party tool.
📝 Note
In IMD if ADD_NEW_DEVICE parameter has been set to "YES" then the administrator will add a new device for the user in inSync Client. 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 device replaceworkflow for non-AD users is as follows:
inSync Administrator actions:
On the inSync Management console, marks the device which needs to be replaced and start the device replace process.
If the ADD_NEW_DEVICE parameter has been set to "YES" then the administrator adds a new device for the user instead of replacing the old device.
System Administrator actions:
Login to the new device and create a local account.
UsingIMD, installinSyncclient on the user's new device.
Log in as the user on the new device.
inSyncClient restores all the data includingsystem settings andMAPIdataon the new device.
inSyncClient moves the restored data which is saved at the temporary location to relevant paths and folders as required.
The device is ready to be shipped to the user.
User actions:
Login to the new device which is ready to be used.
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>" FOR_LOCAL_USER= "<user's device>"
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>" FOR_LOCAL_USER= "<user's device>" RESTORE_SYSTEM_SETTINGS= "Yes"
For example
|
If you want to add a new device 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>” FOR_LOCAL_USER= “<local user's name>” ADD_NEW_DEVICE= “<new device to be added>” RESTORE_SYSTEM_SETTINGS= "Yes"
For example
msiexec.exe /qn /i inSync.msi TOKENV2='33-bb0af8c55da3f9ddxxxx’SERVERLIST="cloud.druva.com:443" FOR_USER="ernie.carter@sample.org" FOR_DEVICE="DDSPLxxxx” FOR_LOCAL_USER=”Ernie" ADD_NEW_DEVICE=”Yes” RESTORE_SYSTEM_SETTINGS=”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 " --for-local-user "ernie" --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" --for-local-user "user1" --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 " --for-local-user "ernie" --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" --for-local-user "user1" --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 log in to the device to complete the device replacement process For more information, see Manage data after remote device refresh.