How can I have the KACE ID shown when looking at devices?
I am very new to KACE and have been assigned the task of providing a device ID # to all present and future KACE devices.
I know there is a KACE ID provided to all devices found by the software, but I am struggling to make this number commonly visible. I would like it to be listed alongside the device name and the IP address. Any tips or directions to look would be appreciated.
Bonus: If possible I would like to customize a device ID inside of KACE. Something that can give a custom number to all current devices, and dynamically name the devices that will be added. I have been struggling inside of labeling and asset management to find even the slightest hint of manipulation in this direction. Again any help will be absolutely appreciated.
Current Agent Version: 13.1.19
Answers (4)
what KACE ID do you mean?
Examples, examples, examples.
(from what you write I have a few ideas, what you mean: the device id in the appliance (not changeable), the KUID (which is in c:\programdata\quest\kace\kuid.txt, also not changeable), the token, which is used to approve the agent (which is the same for all, you can find it under Settings | Agent Token, there is a limit how to change it), the certificates for encrypting the traffic between agent and the server (also not changeable) or anything you can imagine (like a Registry Setting, File on the system containing whatever you want and can be read out with a Custom Inventory Rule.
Comments:
-
I appreciate your reply. I seem to have limited permissions to the agent tokens. I believe there aren't many options for customizing the KUID anyway.
Are you aware of ways to apply a custom ID to say a group of desktops in a particular buiding? for example a desktop in the north building is now DTN-001
I have been asked to make this happen and the admin guide is not as direct on this subject as I would need. - willberto 1 year ago-
I would go with a registry setting and use a CIR to read it out to populate labels.
As I wrote, the KUID, the token etc are not changeable but used for identifying the system.
https://support.quest.com/kb/4262543 - Nico_K 1 year ago-
Great link. I will see if I can make it work for my purposes. Thank you. - willberto 1 year ago
I was able to add the KUID to the device detail bar, which is great, but I see it won't really be a convenient number for asset identification.
So why not use the Asset ID? It’s much simpler than the KUID and is unique to every asset, kinda like an Asset Tag??
You will find it in ASSET.ID field, now if you wanted to show that as the asset Tag, I recommend naming the asset as the asset tag by the way, then just create a ticket rule to copy ASSET.ID into either the ASSET.NAME field or just into the scannable value of Asset Tag so you can label and then barcode scan your assets, as in an asset management best practice kind of way.
Comments:
-
I absolutely agree the KUID is way too cumbersome. Speaking with my manager, the Asset Unique ID is likely the best option.
I have yet to create an asset tag. It seems perhaps easier than creating a custom inventory rule, but could it be applied to the device inventory? For instance, I am unable to search for the Asset Unique ID while inside the inventory | devices overview.
A part of my task is have this be a searchable variable for asset/device management.
edit: I had misunderstood ASSET.ID to be the same as the Device ID
I erased 2 sentences for clarity purposes - willberto 1 year ago
Top Answer
In discussion with the Quest support team, to fulfill my request I needed to:
> Create the field for my devices
> Export the asset data I desired to a .csv
> Edit the .csv to match the desired information for my new device field
> Import assets from the edited .csv to update the devices
This functions but is not automated or dynamic in the way my management requires.
I will mark this as answered