When re-imaging a machine we'd like to keep the same machine entry. currently we create an image with the client installed and remove the kuid from the registry. When re-imaging we export the existing kuid then apply an image and then re-apply the kuid to the registry before the machine boots to go through the rest of the sysprep process. Even though we do this we still get a new machine created in inventory until the system reboots, then the amp connection is on the old entry.

we are grabbing the keys from.

HKLM\SOFTWARE\DELL\KACE
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I've never tried this, so I'm not sure if the KUID in the registry is the only thing you'd have to copy. However, if you are applying the old KUID while the agent is active and not restarting the service - then that is the issue. Changing or removing the KUID won't take effect until the agent is restarted. That would also explain why AMP shows correctly after a reboot.
Answered 08/02/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
Duplicate detection was creating a new entry. I turned it off under the amp settings and it's working fine now. The KUID was applied in the winPE environment before booting the final installation.
Answered 08/02/2011 by: craig.thatcher
Orange Belt

Please log in to comment
0
Good to know. I'm glad you were able to figure it out! I've never disabled duplicate detection due to the "OMG! Don't push the red button!" warning it gives you if you click the info icon for that setting. [;)]
Answered 08/02/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
I was scared of it for a while too; the language is unclear. Duplicate machine detection sounds like a good thing right?! Well in some cases it is- where a KUID is on multiple machines (usually because of a bad imaging practice) but where that's not in play the Dupe detection can actually cause multiple DB entries for the same machine. I believe this is being addressed in engineering, although I am unsure of when/what release. Cheers!
Answered 08/02/2011 by: cblake
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity