Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

Asset Model Mapping issue due to Intune Discovery

Kokila Vani
Tera Contributor

Hi Team,

 

During the Intune discovery process, approximately 300+ assets were identified and corresponding Configuration Items (CIs) were successfully created.

However, instead of being mapped to the existing asset models within ServiceNow, these assets were associated with newly generated unique models. This has resulted in a misalignment between the discovered assets and the established model framework in ServiceNow, requiring corrective action to ensure proper mapping and consistency across the asset management system.

 

Any good recommendations?

 

Thanks,

Vani

5 REPLIES 5

Hi @Kokila Vani ,

So there 2 options for :

Option 1: Here what you can do is changing the ETL mapping Configuration of SGC-Intune , follow the steps to change it 

1. In all navigator search for "integrationhub ETL"

VishnuK_0-1770139031812.png

 

 

2.Now open the SGC-Intune 

 

VishnuK_1-1770139068793.png

 

3. Now open the Step3 in that

 

VishnuK_2-1770139113342.png

 

4.Then open the computer class by clicking on view mapping

 

VishnuK_3-1770139160646.png

 

 

5.Then click on the Transform data tab and search for the model field 

 

VishnuK_4-1770139217539.png

VishnuK_5-1770139225607.png

6. Now you can write a new transform script operation on that field , with following script 

 

var currentModel = new GlideRecord('cmdb_model');
currentModel.addQuery('name', modelId);
currentModel.query();
if (currentModel.next()) {
// Model exists, return its unique value
output[i] = currentModel.getUniqueValue();
} else {
// Model does not exist, create a new one
currentModel.initialize();
currentModel.setValue('name', modelId);

currentModel.insert();
output[i] = currentModel.getUniqueValue();
}

 

7. now change the mapping  of Model ID field in the map to cmdb tab 

 

VishnuK_6-1770139497537.png

 

so that is option 1

 

Option2: So here what you have to do is that ask the clients manage the manufacturer in their intune side  so no changes needed on our side.

Note : I would not suggest the Option1 cause if you change the OOB connector then you won't receive any future updates regarding that Connector, so mostly try to convince the clients to manage the manufacturer in Intune.

 

Hope this helps you, Please do mark it as helpful . And accept the solution.