I'm looking for a method whereby I can enforce a slow and methodical inclusion of hosts into BMC ASSET from discovery tool datasets. By not auto-identifying BMC_ComputerSystem instances in the discovery tool dataset, I can prevent them from being merged into BMC ASSET unless a BMC_ComputerSystem instance already exists in BMC ASSET and can be matched via the identification group rules.
However, for child CIs (harddrives, installed software, etc) I'd like to not have this same constraint. I want them to automatically merge with their parent BMC_ComputerSystem instance once that instance has been reconciled to a BMC ASSET computer system instance. It seems to me that when creating a merge activity, the "include child CI's?" option should facilitate this type of functionality. However, even when I set this option to "yes" Atrium refuses to merge Computer System child CIs with their associated parent instance. Can anyone shed some light on how best to achieve this sort of functionality (if its even possible)? I don't want to have to hand create each computer system child CI in BMC ASSET before their associated CIs in the discovery dataset can be merged, but I also don't want to firehose all the child CIs into BMC ASSET either, which is what happens when I auto-identify them. Tim O'Connor Staff Consultant Cell 925 324 6958 EMC² _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
