I agree with this. A few years ago we looked at a similar situation where we were going to bring in Add/Remove Program info for PCs and laptops from our LANDesk system (primarily for license tracking). At that time there were 1 million records (I think it is closer to 2 million now) including a large bulk of MS patch info that we didn't really care about because LANDeskis used to verify patch levels.
The project never got off the ground but what we talked about was in LANDeskthere would be a custom table and all non-MS patch program info would be dumped into it and that is what we would use for populating the CMDB. Of course the trick is how do you identify what to bring in. We talked about using a field on the Product Catalog to determine if the software was one we wanted to track in the CMDB. This way it is still configuration driven and manageable by the product catalog people. The job in the LANDesk DB would reference the Product Catalog directly to determine what apps to bring in to the table. At that point anything in the table was something we wanted in the CMDB. Jason On Thu, Apr 3, 2014 at 10:15 AM, Roger Justice <[email protected]> wrote: > ** I recommend that Patches and Hot Fixes are not sent to the CMDB since > only the last one is needed. Leave these in the discovery tool to be > review/reported as needed. > > > > -----Original Message----- > From: Rick Cook <[email protected]> > To: arslist <[email protected]> > Sent: Thu, Apr 3, 2014 1:07 pm > Subject: Re: CMDB 7.6.04 to CI or not CI, that is the question... > > ** > Make each update a single CI, and map relationships to the devices that > have that update installed. > Rick > On Apr 3, 2014 10:05 AM, "Sanford, Claire" < > [email protected]> wrote: > >> ** >> We are in the process of doing an integration with TADDM and Remedy >> CMDB and need to know how other people document things like the MS KBXXXXXX >> patches etc. >> >> By our figures it would be about 800K records and every month we would be >> adding appx 500K records for all the patches on the 1925 servers. >> >> Would each one of these items in this screen shot be a CI for every >> server? Would it be one CI and then related to each server? Either way >> that is a lot of overhead. >> How do you handle/manage this in your environment. We are starting from >> scratch and want to do it the right way! >> >> >> >> >> ITSM 7.6.04 SP2 >> ARS 7.6.04 SP4 >> Oracle 11.2.0.3.0 - 64bit Production >> Win 2008 Server >> >> Claire Sanford >> Information Systems Division >> Memorial Hermann Healthcare System >> [email protected] >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
<<inline: image003.jpg>>
