Regarding Kace Device migration and asset management

Hello everyone,

My company is planning to migrate our kace (currently hosted localy, we are planning to change that) and i have a question regarding asset/device migration.

I tried migrate a device/asset to the new system to see if important informations (user, location) were exported and it seems that it is not the case.

The problem that i have is that if try exporting wanted data then import them, rather than adding datas to existing asset, a new asset is created.

My question is : Is there any way to migrate a device with all his datas, or to easily add those missing data post migration, or am i forced to manually re-add those datas to thoses migrated assets ?

Thank by advance for your response.

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Nico_K 1 month ago
Red Belt

you have two options:
1st option is simply restore the backup on the new appliance and change then all network data.
2nd option is to export the data in question (Settings |Ressources) and import it to the new appliance

For moving devices (your computers in inventory) to the new appliance you have many options:
1. simply create a DNS Alias to the new appliance
2. create a script on the old one which just replaces the host. Something like:

Launch “$(KACE_APP_DIR)\amptools.exe” with params “-resetconf host=NEWHOST token=NEWTOKEN"This just resets the Agent configuration (on all supported OS!) and rewrites it with the new hostname (NEWHOST) and (if applicable) new token (NEWTOKEN)

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ