In case of cloning, as a previous step, ensure robot/system IP/hostname consistency:
- Correct the hostname and IP in the robot.cfg by using the controller probe, configure probe, to set the new hostname and the new ip.
- Restart the robot. Right click on each probe that is not getting a port and select validate->security->okay
Reset niscache and reser robot device_id steps:
- Infrastructure Manager (IM):
- Navigate to the robot which needs to have its device id or niscache reset
- Highlight the 'controller' probe and press 'CTRL + P'
- When the probe utility for the controller probe comes up, select 'Options' (the icon with the gear)
- Put a check in 'Expert Mode' and click OK
- Pulldown on the 'Probe commandset' menu and select '
_nis_cache_clean' then press play, - then select '
_reset_device_id_and_restart' This will flush the niscache folder, including the robot device id.

The robot will restart and immediately begin to repopulate the niscache (beginning with the robot device id).
- Repeat this procedure on all robots which were cloned.
- Use Admin Console (AC)
- Access probe utility from the 3 dots to the left of the probe name.

- Find the options at the bottom of the list on the left. (There is no options or expert mode from Admin Console)

NOTE:
For cloned robots, it might be necessary to Delete the device and have the discovery server to "rediscover it" cleanly. For deleting device:
- Go to Operator Console and Inventory,
- Find these robots using the search from the Add Filter box.
- Put a check in the box next to the robot, from the three dots on the top right pull down select "Delete Selected".
- REMOVE the check from prevent rediscovery and press Delete.

This will clean up the entries in Operator Console.