Use cmdb_ci table to import servers

[SME]

Hi,

My client wants to import their servers in SNOW and they wants to use cmdb table. It is not a full cmdb implementation. We were thinking to load all 1000 servers in cmdb_ci_server table with class specified as windows, linux, unix etc.

Is this the right approach. Will it affect when they implement discovery and full cmdb? If yes, how and what is the right approach then?

Thanks.

[Mike Allen]

I have had real problems doing this in the past, but it was on Aspen and Berlin when I tried.   There were issues moving things to extended tables from the base table, like database errors, etc.   I ended up just having to do 4 separate imports (actually, I was using a JDBC data source and import sets).

[Deepak Ingale1]

Hi Mansi,

You can import to CMDB_CI_Server but keep in mind that you set the Class while doing import.

e.g., you can select class as 'windows server' for servers belonging to windows OS. You can do it by using onBefore script.

Transform Map Scripts - ServiceNow Wiki

There are few aspects to look after while doing this xform, you need to also consider the 'Model','Model Categories' also.

These are the reference fields on extended server tables. Also to check for if you are mapping server record (CI Server) with its Asset tag or Asset record as well. Or you are creating those while doing import of Server.

Some of the bookmarks which I have can help you are

ci imports from cmdb

CMDB data conversions and data mapping

You can do it in sandbox or DEV instance, test it completely and then move to PROD

[SME]

Thanks everyone. Let me try doing this. Will let you know how this goes.

My another question was:- This is not a full CMDB implementation, we are just trying to use cmdb server table. So, how will it affect when client does CMDB implementation?

[Mike Allen]

In the transform map, if they coalesce on the name (or whatever their unique ID is), it should not have any effect.