How to identify obsolete OS version on Servers

Ed Shooshanian1
Kilo Expert

We have a need to store obsolesence data in ServiceNow for servers running obsolete OS versions.  The driver of these requirement is Change Management.  The Change process wants to increase risk when the there is obsolete version running the app.  So if there is a Windows 2003 server affected by the change, the risk level should increase so that the CAB would force a review, etc.

Is there a field in the CMDB to store the obsolescence value?  Should we add one?

We do plan to introduce the TPM module later this year but we have a short term need to help before we get there.

Open to any options.  Today the obsolescence data is actually stored outside SNOW and the ask is to bring the data in, but that would be a daily update of 30,000+ records which we are trying to avoid.  Has anyone build a table of current OS versions in SNOW?

Thank you

Ed 

1 ACCEPTED SOLUTION

Rahul Priyadars
Tera Sage

obsolesence data in ServiceNow for servers running obsolete OS versions--> May i know how CMDB data for let say server is Populated? Manual or Discovery?

It Seems that Consumer of this Obsolete data is ur Change Management Process.

You can add a custom attribute in CMDB_CI CLass or you can choose which best suits your need - Populate the custom attribute Obsolete for your CI data. You can use schedule Job to populate this FLAG based upon your obsolete criteria .

Has anyone build a table of current OS versions in SNOW?--> Its OOTB for server classes.

find_real_file.png

Regards

RP

 

View solution in original post

3 REPLIES 3

doug_schulze
ServiceNow Employee
ServiceNow Employee

If you are using discovery we populate the Many OS attributes that can easily be reported on or built into the CMDB dashboard. If you are using imported data then ensure that information is coming across.

Or am I mis-understanding your question...

Rahul Priyadars
Tera Sage

obsolesence data in ServiceNow for servers running obsolete OS versions--> May i know how CMDB data for let say server is Populated? Manual or Discovery?

It Seems that Consumer of this Obsolete data is ur Change Management Process.

You can add a custom attribute in CMDB_CI CLass or you can choose which best suits your need - Populate the custom attribute Obsolete for your CI data. You can use schedule Job to populate this FLAG based upon your obsolete criteria .

Has anyone build a table of current OS versions in SNOW?--> Its OOTB for server classes.

find_real_file.png

Regards

RP

 

R_mulo Subtil
Tera Contributor

I created a FLAG on cmdb_ci_server called OS EOL and I did a schedule Job to populate this FLAG with Yes or No.

 

First we need to create in the CMDB Group a health group type in order to group all servers that will match the OS Type and Versions conditions.

Second we created a schedule a job to flag with an Yes each server on my cmdb_ci_server table grouped on my CMDB Group.