Reinstall HDD/OS without losing KACE inventory info
I just finished up reinstalling the OS on a machine after the HDD decided it had had enough. This is basically a timeclock, nothing huge, just Win XP, browser, and one business specific program. Throw in Dameware, Symantec Endpoint Protection and a KACE agent and I'm done. I was hoping that once the OS and AMP agent were installed and everything matched back up with Active Directory that the K1000 would just detect the machine, since it hadn't checked in for a month. No dice. It's creating an entirely new entry, not linked to the tickets that the machine had in the past. Is there a way to make the K1000 realize it's the same machine, just with a new HDD and AMP Agent?
Answers (1)
The quickest way to fix this is:
- stop the AMP service
- find the new (duplicate) KUID in the computer's registry and replace it with the old (correct/desired) KUID
- restart the AMP service
- remove the duplicated inventory and asset records
For the full details, read the KB article: http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=673&artlang=en
Comments:
-
You can avoid this behavior in the future by using this script: http://www.kace.com/support/resources/kb/article/K2000-Retain-KUID-of-a-machine-when-deploying-an-image - mpace 10 years ago
-
Thanks for the assist here. Good tips, good reads. Only problem is that we handle all of our imaging/deployment manually. The only box I've got in house is the K1000. The last KB pertains to the K2000. Anyway to preserve the KUID in that respect? - aintITcool 10 years ago
-
We currently use Ghost for imaging. Before we capture the image (with sysprep, etc), we disable the AMP service and delete the KUID registry entries. Once the target has the image applied, we name the computer, join it to the domain, and reenable the AMP service. - grayematter 10 years ago
-
Much obliged sir. All is right with the box. Thanks. - aintITcool 10 years ago
