SteveJM Posted August 28 Posted August 28 We have successfully created a set of relationships between our User Laptops and Desktop Applications (i.e. a One to Many relationship) My question is, what is best practice for maintaining these relationships? Maybe with a weekly update run? e.g. How do we cater for the following scenarios? A user installs or uninstalls a new Desktop App. A user upgrades Firefox from 127 to 128, A laptop is lost, decommissioned or drops off AD I see the removelinks section of the asset_rel_import.exe .JSON ... Is it easier to remove ALL relationships between the 2 Asset Types and reload all again? Or work out what the differences are and apply only those? If we attempt to create a relationship that is already there will that cause an issue? If we Decommission a Laptop (we have a Substate of decommissioned) will the links to Desktop Apps remain in situ? What I am asking here is what is best practice for maintaining CMDB relationships?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now