Avoid duplicates machine record due to re-imaging
Hi,
We are in a process of implementing Asset MGMT module and want to avoid duplicate records due to re-imaging. I have seen some training videos form which i get the idea , if we map BIOS Serial No to custom asset field BIOS then Kbox will recognize the machine every time it get re-imaged.
But some of my old Kbox users told me that it is not going to work until you map BIOS Serial No to default asset field 'name' . I will grateful if someone can inform me which method is right.
Thanking you.
We are in a process of implementing Asset MGMT module and want to avoid duplicate records due to re-imaging. I have seen some training videos form which i get the idea , if we map BIOS Serial No to custom asset field BIOS then Kbox will recognize the machine every time it get re-imaged.
But some of my old Kbox users told me that it is not going to work until you map BIOS Serial No to default asset field 'name' . I will grateful if someone can inform me which method is right.
Thanking you.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
afzal
13 years ago
I have noticed that with Kbox 5.3 and agent 5.3 ,Mapped inventory field is updating according to the change in the mapped inventory field selection. Previously when I have mapped BIOS Serial number to BIOS and it was not fetching the BIOS Serial# till I deleted the previous Asset Record but with this new 5.3 release Kbox is updating the old record without deleting the Asset record.
Posted by:
GillySpy
13 years ago
The problem of duplicates in inventory and duplicates assets is not relevant to what field you map between the computer asset type and the computer records. Once the two are linked it is unbreakable unless you delete one of them. Although we do recommend mapping bios s/n from inventory to a bios s/n value in the asset.
To avoid a duplicate you want to pull the KUID from the machine being reimaged and then re-inject this same KUID back in when done -- before the agent is started (before the agent connects to the kbox without this KUID). If you are using the K2000 to re-image they have pre and post scripts to do this.
If not then please read this:
http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=851&artlang=en
your image should already be setup for that faq.
If it is a new machine then you just let the machine connect to the kbox (after it has been names/ sysprepped).
If it is a re-image then That reg key is where you re-inject KUIDs -- again before agent hits the network.
To avoid a duplicate you want to pull the KUID from the machine being reimaged and then re-inject this same KUID back in when done -- before the agent is started (before the agent connects to the kbox without this KUID). If you are using the K2000 to re-image they have pre and post scripts to do this.
If not then please read this:
http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=851&artlang=en
your image should already be setup for that faq.
If it is a new machine then you just let the machine connect to the kbox (after it has been names/ sysprepped).
If it is a re-image then That reg key is where you re-inject KUIDs -- again before agent hits the network.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.