Related Assets within Software Asset Management.
Kristi_Miller
Customer IT Monkey ✭
I have noticed that hardware assets are still listed as a Related Asset in a Software Asset even though the computer has been re-imaged and no longer has that software installed. Why isn't that machine being removed from being a related asset, which would then give me a more accurate account of our licensing within that Software Asset?
0
Best Answers
-
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
This is caused because the data from ConfigMgr is still valid within the SCSM database.
Once the computer has been rebuilt, it will then need to- Run a valid Inventory from within ConfigMgr
- Have that data brought over to SCSM (Using the ConfigMgr Connector)
- Then the asset management workflow run to match the serial number of the computer to the asset record
- And finally, the asset workflow must run again to update the relationships
Some things that can prevent this from working well is not having the AD GUID recorded for the Computer within SCSM and the AD Connector account not having rights over the Deleted Items container inside AD.
These processes can be forced and therefore sped up if needed.
I hope this answers your question.6 -
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
No. This should not cause any issue with SCSM Asset Management as our workflow just uses the data that is pulled back from the ConfigMgr connector.
The Asset Intelligence data may be required if you are using the Software Metering Connector but this connector will not update installed counts etc. (Unless it is set as such. Not default.)6
Answers
Once the computer has been rebuilt, it will then need to
- Run a valid Inventory from within ConfigMgr
- Have that data brought over to SCSM (Using the ConfigMgr Connector)
- Then the asset management workflow run to match the serial number of the computer to the asset record
- And finally, the asset workflow must run again to update the relationships
Depending on schedules this can take days.Some things that can prevent this from working well is not having the AD GUID recorded for the Computer within SCSM and the AD Connector account not having rights over the Deleted Items container inside AD.
These processes can be forced and therefore sped up if needed.
I hope this answers your question.
I went back and watched the Webinar with Wally series and noticed one thing different. We do not have the Asset Intelligence synchronization enabled. Would this cause the re-imaged machines to not update their list of software within the asset? We are hesitant to re-enable it as we don't know what else it would affect. Do you know?
The Asset Intelligence data may be required if you are using the Software Metering Connector but this connector will not update installed counts etc. (Unless it is set as such. Not default.)
Can you give me the detailed instructions on performing each of these steps or point me to a knowledge article?
Run a valid Inventory from within ConfigMgrHave that data brought over to SCSM (Using the ConfigMgr Connector)Then the asset management workflow run to match the serial number of the computer to the asset recordAnd finally, the asset workflow must run again to update the relationships