I need to extend the pattern to get the Environment details of servers in my organization

Ashupakasma
Tera Expert

Hi Experts!

 

Hope all are doing good.

 

I am reaching out here to get some solution on "to extend the pattern to get the Environment details of servers in my organisation". That details is updated in Registery value of the servers, so I have tried to extend the -Windows OS - Servers pattern.


I am trying to get it via Get Registery Key Operation, but not able to sucess.

Can I get some help on this.

 

Thanks!

 

Note :I have tried to search and get 

https://www.servicenow.com/community/itom-articles/extending-patterns-method-2/ta-p/2326781

https://www.servicenow.com/community/itom-articles/extending-patterns/ta-p/2326816

But not able to solve my issue.

 

2 ACCEPTED SOLUTIONS

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @Ashupakasma 

 

I see you are directly using the actual win server cmdb ci name itself in the registry step, instead you better use a temporary value and then copy it to actual CI in different step.

 

Though you did it, still I could see the env value is set in CI attributes section in 6th image, so what is the concern here that its not working.

 

Please mark Helpful / Accept Solution so that it helps others with similar questions.

View solution in original post

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @Ashupakasma 

 

You should not change the source table name in steps 8 image, keep the source table also as win server CI name.

 

Once you do above change, in debug mode go to next step and in right CI attributes view you should see all the win cI attributes filled properly

 

Please mark Helpful / Accept Solution so that it helps others with similar questions.

View solution in original post

11 REPLIES 11

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @Ashupakasma 

 

How are you saying that the info is not populated after discovery too? Where all have you checked for the existence of this new field whether populated or not?

 

Please mark Helpful / Accept Solution so that it helps others with similar questions.

Hey @SiD2 ,

 

Apologies, we have some reconciliation rules created (for SCCM(100) and Intune(200)) and ServiceNow is not taken in those rules, so it's not allowing us to update via discovery. Now It's working fine. Thanks for this.