How to solve : Discovery Fundamentals On Demand (Course) Task: Extend Windows OS - Servers Pattern

[prasanna_da]

How to solve : 

Discovery Fundamentals On Demand (Course)  Task: Extend Windows OS - Servers Pattern (Content)

Task: Extend Windows OS - Servers Pattern

SCENARIO:

Cloud Dimensions has gained confidence in how easy it is to extend ServiceNow Discovery for applications. Next it would like to extend the Windows OS - Servers pattern to collect the processor name value from Windows Servers and write the value to the Description field. The processor name is an important attribute that Cloud Dimensions wants to report on to assist in future infrastructure planning. 

REQUIREMENT:

As the Cloud Dimensions Discovery administrator, you are tasked with extending the base system Windows OS - Servers pattern to collect processor name from discovered Windows Servers and write the value back to the Description field. Use the following information to accomplish the task.

From the Windows OS - Servers pattern:

• Create a new Extension Section called Windows OS Extension

Open the Windows OS Extension Section and do the following:

• Enable Debug Mode using your Windows MID Server IP Address (i.e. 10.x....) for the Host Name/IP

  NOTE: Enabling Debug Mode can take a few minutes.

• Create the steps needed to collect the processor name and write it back to the Description field of a discovered Windows Server

Hint: One option to collect processor name is to use a WMI query from the "root/CIMV2" namespace, WIN32_Processor table, Name field. Review the steps you created in the iTunes pattern for additional guidance.

VERIFICATION:

Before validating the task, perform the following:

• Save the pattern

NOTE: When creating or updating an extension section, the pattern only needs to be saved and not published.

• From the MID Server list, checkmark windows_mid and click Pattern Sync to Mid to synchronize the updated pattern with the MID Server

• Run discovery against your Windows MID Server

• Confirm the discovered Windows Server Description field is updated with the processor name as shown

-------------

Upon completion of this task, select the Validate Task button. If the validation fails, you will be presented with feedback text that indicates what could be failing, along with clickable links to the ServiceNow documentation site for more guidance.

ISSUE :: Unable to validate task.
  I have created those Pattern extension : 

Step 1 : 

STEP 2 :

Used the IP Address of the windows mid server ;

Record Updated after Syncing the Pattern and running the scheduled discovery > quick discovery,

And Results are:

Please help me with this. The task is still not validated.

@Ankur Bawiskar 

[Harish Bainsla]

Hi @prasanna_da  check below link

https://www.servicenow.com/community/itom-forum/servicenow-discovery-fundamentals-on-demand-simulato...

if my answer helps you mark helpful and accept solution 

[roehltablada]

Hi @prasanna_da,

As of today, May 27, 2025, there is a bug in validating that task. Even if got the correct steps, the validation will still fail.

Here's the solution:

Step 1:

• Step Name: Collect Processor Name
• Operation: WMI Query
• Namespace: "root/CIMV2"
• Get Full Statement: "SELECT Name FROM Win32_Processor"
• Target Table: $cmdb_ci_win_server

Step 2:

• Step Name: Set Processor Name
• Operation: Set Parameter Value
• Value: $cmdb_ci_win_serverl[1].Name
• Name: $cmdb_ci_win_serverl[1].short_description

Once you execute Quick Discovery, this will create a record in cmdb_ci_win_server table. However, validation will fail if ServiceNow has not corrected the defect yet.

To correct the defect, replace the Description field with:
      Intel(R) Xeon(R) Platinum 8270C CPU @ 2.80GHz

[roehltablada · Accepted solution]

Hi @prasanna_da,

As of today, May 27, 2025, there is a bug in validating that task. Even if you got the correct steps, the validation will still fail.

Here's the solution:

Step 1:

• Step Name: Collect Processor Name
• Operation: WMI Query
• Namespace: "root/CIMV2"
• Get Full Statement: "SELECT Name FROM Win32_Processor"
• Target Table: $cmdb_ci_win_server

Step 2:

• Step Name: Set Processor Name
• Operation: Set Parameter Value
• Value: $cmdb_ci_win_serverl[1].Name
• Name: $cmdb_ci_win_serverl[1].short_description

Once you execute Quick Discovery, this will create a record in cmdb_ci_win_server table. However, validation will fail if ServiceNow has not corrected the defect yet.

To correct the defect, replace the Description field with:
      Intel(R) Xeon(R) Platinum 8270C CPU @ 2.80GHz

[Suresh K1]

Defect does not seem to be fixed as 0f 20 June 2025, the workaround helped me to complete the task successfully, thanks roehltablad

[shobhaH]

Hi   

Mega Guru can you please help me with this steps, im stuck in this lab simulator, 

i am facing error with mid discovery, not getting why after follwing lab setps.