I would edit the robot.cfg and hub.cfg to update the domain name.
have to be careful as this is case sensitive.
Then delete the hub.sds file and the security.* files from the hub directory
last setup a namedIP connection to the existing domain or a tunnel to have the security file synched to this new hub.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 02-25-2020 12:44 PM
From: Operations
Subject: moving secondary hub to an existing domain
this is for version 9.02 by the way.
Original Message:
Sent: 02-25-2020 12:41 PM
From: Operations
Subject: moving secondary hub to an existing domain
What is the "right" way to move a secondary hub from one domain to another existing domain?
I experimented with changing the "domain =" setting in the hub.cfg and resetting security.cfg, but that method only created a new domain with the same name as the destination domain which seemed like a rather dangerous result.
I'm thinking the correct way to do this would be to remove the hub probe from the secondary hub ("demote" it), move it as just another robot from one domain to the other, and then re-install the hub probe onto the robot in the destination domain.
Thanks
Steve