/build/static/layout/Breadcrumb_cap_w.png

Computer names are differently reported in Asset and Inventory module

We are having problems after changing the names of computers, Now asset module is showing different name (old) and inventory module is showing new name, I dont know how to solve this problem. One quick solution in my mind is to delete all the Asset data but it will also delete History informaiton as well. Any help will be highly appriciated.

Regards,


0 Comments   [ + ] Show comments

Answers (3)

Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
If you change the names of a computer the asset name will not change. You could delete the asset record but then any asset data and history is gone.

There are two solutions but first:
How do you map your assets to computers? by name? BIOS S/N ? Other?
Posted by: afzal 12 years ago
Fourth Degree Green Belt
0
We are using by 'Name'

Thanks for your quick reply.

Regards,
Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
steps i would take if you don't care about asset history but just the data
1. run a report against computer assets getting both the asset name and the PC's actual name -- only report the ones that are different
2. delete all computer assets that mismatch
3. allow machines to checkin and created new computer assets
4. import your report from step 1 using the pc name as the key and ignoring the legacy asset name
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

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

Sign up! or login

Share

 
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