-----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...
_ARSlist: "Where the Answers Are" and have been for 20 years_
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:
_ARSlist: "Where the Answers Are" and have been for 20 years_ **_ARSlist: "Where the Answers Are" and have been for 20 years_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 SP2ARS 7.6.04 SP4Oracle 11.2.0.3.0 - 64bit ProductionWin 2008 ServerClaire SanfordInformation Systems DivisionMemorial Hermann Healthcare System
