Orphan CI's using Orphan rule in CMDB health

[Ravish Shetty]

hi all,

how are you using the orphan ci rule in servicenow for CMDB health and what are the definitions that you have used for different classes? what is the remediation action taken if a CI is determined as an orphan?

[Nilanjan1]

@Ashutosh Munot : Do you know if there is a reason in which an admin cannot edit...any health inclusion rules?

Regards

Nilanjan

[Ashutosh Munot1]

HI,

I need to check that, but if there are some baseline rules then they might be protected.

Thanks,
Ashutosh

[Nilanjan1]

@Ashutosh Munot 

Thanks Ashu.. I was previously able to edit the health inclusion rules but now I am unable to do that it says that Record is not found, not sure what went wrong...whereas I could see the CMDB group rules are something that is configured properly... which needs to be corrected and with no access to the specific module...it seems nothing is working. 

Regards

Nilanjan

[Steve Arnold3]

Currently, our Orphan Rule is set up like this for Servers:

The goal is to make sure everything is related to an Application.

I'm sure we will eventually expand this rule for other purposes.

[lefthighkick1]

There are storage disks with child as 'empty' who appear in the Orphan list. As storage disks do not necessarily need a child relationship, can you help me regarding how to create an orphan rule to exclude storage disks with child relationship as 'empty'.