RSAs can not be duplicated.
The fix does require support engineer and a tether placed on the original RSA for versions less than 4.0.
First, configure the RSA as normal, adding it as a remote site and check the desired data to sync to the RSA. Take EXACT notes of what was chosen as this will need to be replicated later in the instructions. Sync the data to the RSA.
On the K2000, delete the RSA from Deployments | Remote Sites. Delete the RSA from Settings & Maintenance | Linked Appliances.
On the RSA, remove config from Control Panel | Remote Sites (if still configured) and disable Kace Linking.
In versions under 4.0 Contact your support person to let them know you have finished this procedure and are ready for the next step. At this point the support engineer will connect to your RSA and remove the ssh fingerprint. When the support engineer has completed their process you will be notified to complete the next steps. Remove the tether key from the RSA.
In version 4.0 a tether is not required.
All versions should continue with the steps below.
Power off the RSA and then duplicate it for your original. You should not power on your original for any reason, it should only be cloned.
Now the RSA has all the data on it. To use it, clone it to the site and start up the RSA. If prompted, select "I copied it" as this will assign a new MAC address. We want the MAC address to be different from the original.
Configure the new RSA with the appropriate settings, such as host name and IP. This restarts the RSA.
Enable linking on the RSA, In versions under 4.0 copy the linking key and enter it into the K2000. In versions 4.0 and higher, go to Settings | Linking Key and click the "Regenerate" button. This will create a new linking key for the RSA.
Under Deployments | Remote Sites, add the new RSA and select the EXACT same files to sync as you did earlier.
The RSA will say that it needs to update a certain number of files, but once they start communicating, there will be very little to sync.
