Seperate CI for hardware and OS?

[Marijn]

I'm new to ServiceNow and have a question.

The organization i'm working in wants to use ServiceNow CMDB also for the datacenter. Here we have hardware hosts that run an OS for a user. 

The ServiceNow teams wants the physicals host and the OS to be represented in a singular CI and additional asset. 

However I think this might cause issues when we replace the physical server, due to repair/replacement/etc, or if we reuse the physical host to run another OS-configuration for another user. The implementation teams says they'll simply "overwrite the old data and the old info will be in the change log" ... but that doesn't sound like a good plan to me. 

How do i know to search for the information of retired server x if i don't know the hostname of the host using that same hardware right now?

My idea would be to use 2 CI's. One for the physical host and one for the OS. The relation between the hosts can indicate that one "runs on" the other. This idea was shot down, it's impossible.

Is it? are there best practices for cases like this? Could anyone help me with an answer or point me towards an best practice / whitepaper? I've been looking but did not find anything yet.

Kind regards,

Marijn

[AJ-TechTrek]

Hi @Marijn ,

Do you mean by a Physical Host  or OS host server record in ServiceNow.

ServiceNow Managing a single record for OS Host in Specific CI class. creating a New record Physical Server and then relationship with OS Host will mashed the CMDB.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thank You

AJ - TechTrek with AJ

Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/

YouTube:- https://www.youtube.com/@learnitomwithaj

ServiceNow Community Rising Star 2024

[Marijn]

Dear @AJ-TechTrek ,

I indeed thought we could do CI 2 records, one for the OS and one for the Physical server as i thought the CI-ASSET relationship should not be changed.

Now after thorough discussion the implementation team will make the CI-ASSET relationship more dynamic. Ensuring we always have a CI with the actual Asset it's using but also keeping the asset records for previous physical servers or ci records for previous installs if the host-phyiscal server configuration changes.