How to merge models and their associated Assets which have different names related to one model

[reddy567]

Hello,

Am working on hardware asset management to eliminate duplicate Assets and Models. We have models created with transform maps, manually and SCCM. when importing Assets into hardware asset table they wrongly mapped to model field on Hardware Asset table because of that multiple Models are created for the same model and each model has assets associated with it. How can I move all assets under one Model name which are created with different model names? How can I make it a unique record with all the assets combined.

I have attached a screenshot of that

Thanks in advance

[Rajesh Mushke]

Hello reddy567,

This might be helpful, Here is the procedure,

Merge a software license

If you have multiple software licenses that are linked to the same model, you can merge these individual licenses into one new consolidated license.

About this task

To be merged, the individual licenses must meet the following requirements:

• The licenses cannot already be merged into another consolidated license.
• The information in the following fields must match for each license:
  • Model
  • Allocated condition
  • Assigned condition
  • Company
  • Location
  • Department
  • Cost center
  • State
• The licenses must have the same set of software upgrades and downgrades and the same set of assets covered. To verify this information, go to Software Asset > Software Licenses and select a license.
  • For upgrades and downgrades, go to the Software Upgrade and Downgrades related list.
  • For assets covered, go to the Assets Covered embedded list in the Contracts related list.

If a license can be merged, Merge with similar licenses appears under Related Links on the Software License form.To merge a license:Procedure

1. Open a license.
2. Click the Merge with similar licenses link.Displays a dialog box with a message stating that the merge process is irreversible and that license keys are not merged.
3. Click OK.All qualifying licenses, including the current license, are merged into a new consolidated license. An informational message appears until the user is redirected to the newly merged license.All qualifying licenses are merged into a new consolidated license unless they can be matched to an existing consolidated license. If they are merged into a new consolidated license, the Asset tag field is cleared. After merging, the merged license is marked as Is merged license (field = true) and the Merged into field is set to this license for the consolidated licenses.
   Note: Licenses that are marked as merged are not counted.
   For the consolidated licenses:

   • The number of rights are summed up into a new count.
   • The asset and user entitlements are transferred to the new license.
   • The expense lines and assets on contract rate cards are transferred to the new license.
   • The set of software upgrades and downgrades, as well as the set of assets covered, are copied to the new license.
   • The cost of each individual license is summed up into the new license using the system base currency.
   • A history of the consolidated licenses and where they went is maintained.

   
   

   Refer :

   
   

   Merge a software license

   
   

   Software license management

   
   

   License upgrade and downgrade

   
   

[reddy567]

Hi Rajesh,

Thanks for the response, am sorry if I did not convey my message properly. I want to merge the Hardware Assets of multiple models which are created with different model names even though it is a same model. Here is the thing, I want to keep only one model and delete the duplicates after moving all the associated assets to the selected record of that model.

Please look at the attached screenshot above it might give an idea of what am trying to accomplish.

Thanks!

[daviddixon]

Hi Rajesh,

We in my organisation are also struggling to address the multiple model issue.

If Dell for example change the name of a model in BIOS (which they do regularly) we end up with model bloat which makes our asset management and stock rules nigh on impossible to maintain. Software isn't the issue here, it is hardware models that I and reddy (from what i can see) are needing help with.

[Craig Rogers]

Did anyone ever get a good answer to these questions?  I am also curious as to the best way to clean up these "duplicate" hardware models created by SCCM discovery.  Can field normalization somehow be used for this and if so how?