Prefix on server serial number from VMware via Discovery

[Henrik Jutterst]

Background:

We are running ServiceNow Discovery on VMware and it seems like serial number have a different format when the CI is updated from Discovery.

Discovery also adds a prefix to the serial number. 

Question:

Is there a setting for this on VMware Discovery or how can this be addressed so that we have the same serial number as displayed on the actual virtual server?

To my understanding the serial number is the same in both VMware and on the virtual server, but when Discovery is done, the serial number is written in another format and with a VMware- prefix.

//Discovery
VMware-42 23 62 aa 3b 11 bd 52-9f a4 f3 97 c3 05 db 01

//Scripted import
422362aa-3b11-bd52-9fa4-f397c305db01

[Henrik Jutterst]

Hi @MattSN and thanks for your input. I agree 100%!

I've already set up that rule but since the custom script goes via Table API, the IRE will not run. Atleast not to my knowledge.

Do you have any ideas about that?

I've asked script owner to change on their side and start using "CMDB Instance API" instead that goes via IRE. But no luck so far. I've thought of using ACL's instead for the script, but that's not going to be a sustainable solution in the long run.

But please let me know if you have any ideas to solve this.

Kind regards

/Henrik

[MattSN]

Hi @Henrik Jutterst 

That is is tough spot. Data hitting the Table API will not set the required tracking for data prescedence. Either a Scripted REST API plus a transform for the scripted data source or like you mentioned the CMDB Instance API.  Maybe ask the owner if they will let you build the script on their behalf?

[Rashmika BS]

We are facing the same situation here. Did you get this resolved?

[Henrik Jutterst]

Stoped digging into this issue, but I'm quite sure that it's not solved yet.