When an inSync administrator remotely marks the user's existing device for replacement, the existing device remains unprotected until the new device is configured and ready to be shipped to the user. In these scenarios, the user cannot take scheduled backups or use inSync Share on the existing device.
To avoid any instances of losing data updates made on the user's existing device while you configure the new device and prepare it for shipment, inSync has introduced the option of adding a new device to the user's inSync account, instead of replacing the existing device. The life cycles of both devices will be managed independently and will not result in any data loss for the user.
The capability of restoring the most recent data from the user's existing device onto the new device, while the new device is in transit is called Restore Delta Data.
Restore Delta Data is an on-demand feature. Contact Support to enable this feature for your account.
Advantages of adding a new device
- The user's old device is protected without any loss of data.
- The user can continue to take or schedule backups on the old device even when the new device is being activated and shipped.
- System settings and MAPI data can now be restored from the latest snapshot when the user logs in to the new device.
- The user can continue to use both devices independently.
Limitations of adding a new device
- The user will continue to have two inSync devices unless the administrator decides to deactivate or delete any one of them
- The space consumed by the new device will be added to the user’s usage quota. For example, if the data consumed by the old device was 20GB of inSync Cloud space. After backup starts on the new device, the user’s usage quota will change to 40GB.
Add new device workflow for non-AD users
The add new device workflow 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 add device process.
System Administrator actions:
- Login to the new device and create a local account.
- Using IMD, install inSync Client on the user's new device. An additional parameter FOR_LOCAL_USER is added while installing inSync Client
- Log in as the user on the new device.
- inSyncAgent activates the new device for the inSync user if there is an existing device of the name provided in FOR_DEVICE schedule in OS migration restores.
- inSync Client restores all the data including system settings and MAPI data on the new device.
- inSync Client 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.
- Login to the new device which is ready to be used.
The user can use both devices until the administrator decides to deactivate the older device.
Device Replace process for non-AD Users
The following table describes the multi-step process for the integrated mass deployment (IMD) device replace.
|Step 1||Mark the old device for replacement from the inSync Management Console.|
|Step 2||Create a user account on the new device.|
|Step 3||Generate a mass deployment token.|
|Step 4||Select the IMD command parameters.|
|Step 5||Log in as a user on the replacement device.|
|Step 6||Run the IMD commands for the Non-AD users.|
|Step 7||inSync Client restores all the data on the new device including system settings and MAPI data. For more information, see Temporary location directories for restored data.|
|Step 8||inSync Client moves the data from the temporary location to relevant folders and paths and ships the device to the user. For more information, see Device replace for Non-AD users.|
|Step 9||The device is now ready to be shipped to the user. Users can complete further steps when they receive the replacement device.
See User actions after adding a new device for Non-AD users.