4 Replies Latest reply on Aug 27, 2020 10:21 AM by Gordon Yeh

    How to administer instance CI's vs "general CI"

    Karl-Johan Halleni
      Share This:

      Asset/CMDB version 20.02


      Am about to populate the CMDB with CI’s, but not from a discovery software, instead from excel sheets via spoon. There will be relatively few CI’s, since there are only a few systems handled by this CMDB environment. Some of the systems/CI’s are located at a site that the CMDB has no access to, hence the CI-updates will be done via excel sheets. The systems/CI’s located at the same site as the CMDB environment will in the initial project phase also be updated via excel sheets.  At a later state in the project (at the earliest most likely in a couple of years), a discovery software will be used.


      CI classes to be used so far:
      Computer System
      Disk Drive
      Operating System
      Pysical Location


      Now to the question
      For hardware and software CI’s the project use the ordinary Status attribute to keep track of the status for each CI instance. I.e. each instance of installed McAfee antivirus software or each instance of hardware monitor HP LA2306x.


      The project also want to keep track of the general/overall status of McAfee antivirus and the monitor HP LA2306x. E.g. if the McAfee or HP monitor is to be decommissioned or such. Where and how is this kind of information supposed to be administered?


      Exampel:  McAfee is reaching end of life and to be decommissioned soon, and will be replaced by a new antivirus. Even though this is about to happen, and also when it has happened, there will be instances of McAfee antivirus still deployed on servers. These instances will still have the Status = Deployed, but where and how is it administered that the McAfee software is end of life/decommissioned as such?