Move Devices Between VoiceConsole On Prem Deployment Instances

This procedure applies only to moving devices to a VoiceConsoleOn Prem deployment. See Device Migration Config to move devices to a VoiceConsole SaaS deployment.

There are occasions when moving (or migrating) devices between different instances of VoiceConsole servers is necessary such as infrastructure upgrades and disaster recovery or prevention.

Source refers to the VoiceConsole instance that currently contains the devices that are intended to be migrated. The source may be either a VoiceConsole On Prem or SaaS deployment.
Destination refers to the destination instance for those devices. The destination must be a VoiceConsole On Prem deployment.

Honeywell recommends choosing an acceptable number of devices so as not to disrupt production if devices are temporarily not available. Use discretion when loading device profiles via RF because loading too many devices at once may disrupt production.

When moving devices between VoiceConsole instances, consider the site IDs may be different between the instances, for example SiteID3 in the original instance might be Chicago, but SiteID3 in the new instance could be New York. In that case, the best process is to move one device, configure that device, then use TouchConfig to configure the additional devices.

Below are most efficient and commonly used methods to move devices between VoiceConsole instances.

Use Hostname to Move Devices

The first method involves a working VoiceConsole instance , whereby devices have stable connectivity and are reporting the status as In charger.

From the Source VoiceConsole instance:

From the VoiceConsole tab, select the Device Management tab.
Under Navigation, click Device Profiles.
Under Device Profile Actions, select Edit hostname for all profiles.
The Edit Hostname for All Profiles page opens. Note the current value for the hostname and record it.
In the Hostname field, delete the existing hostname, and enter the IP address of the Destination VoiceConsole instance.
Click Save Changes.
Under Navigation, click Devices.
Highlight the devices to be migrated.
These devices must report the status of In Charger.
Under Device Profile Actions, select Load Profile to Selected Devices.

Open the Destination VoiceConsole instance.

Devices begin to appear in this instance as the process the hostname change.
These devices can now be loaded with the complete profile from the Destination VoiceConsole instance via RF.
Once the devices successfully load the Destination VoiceConsole profile load they should manually be removed from the Source VoiceConsole instance. This step is necessary as the devices are no longer communicating with the Source instance.

Once confirmed that the devices have migrated successfully, return the hostname field to the earlier value in the Source VoiceConsole instance.

Use New Device Profile to Move Devices

Use this method to avoid changing the hostname field. This method requires creating a profile on the Source VoiceConsole instance to populate devices in the Destination VoiceConsole instance.

This method is ideal if the Destination instance is a duplicate of the Source instance with a database and only one site. Otherwise, make a report of the siteID values between the Source and Destination instances to ensure that devices migrated in this method move seamlessly between the original siteID and the new siteID value.

From the Source VoiceConsole instance:

From the VoiceConsole tab, select the Device Management tab.
Under Navigation, click Device Profiles.
Under Device Profile Actions, select Create new device profile.
Create the device profile as normal, except add an additional parameter under the Advanced Parameters. Add one of the following parameters replacing the bracketed text with the information for the Destination VoiceConsole instance:
```
VoiceConsoleUrl = http://<ip address>:<port>/VoiceConsole/Tmgr/<siteID>
```
Example:
```
VoiceConsoleUrl = http://10.0.0.10:9090/VoiceConsole/Tmgr/-1
```
Click Save Changes.
Under Navigation, click Devices.
Highlight the devices to be migrated.
These devices must report the status of In Charger.
Under Device Profile Actions, select Load Profile to Selected Devices.

Open the Destination VoiceConsole instance.

Devices begin to appear in this instance as the process the hostname change.
These devices can now be loaded with the complete profile from the Destination VoiceConsole instance via RF.
Once the devices successfully load the Destination VoiceConsole profile load they should manually be removed from the Source VoiceConsole instance. This step is necessary as the devices are no longer communicating with the Source instance.

Load Configuration via Cable

This method uses the Talkman Startup Tool to load the unit's configuration.

Use the Talkman Startup Tool and a Micro-USB cable to load the device with a configuration profile to connect with the Destination VoiceConsole instance.
The device reboots at the end of the Talkman Startup Tool process and connects to the Destination VoiceConsole instance.

Open the Destination VoiceConsole instance.

Devices begin to appear in this instance as the process the hostname change.
These devices can now be loaded with the complete profile from the Destination VoiceConsole instance via RF.
Once the devices successfully load the Destination VoiceConsole profile load they should manually be removed from the Source VoiceConsole instance. This step is necessary as the devices are no longer communicating with the Source instance.