Task: Extend Windows OS - Servers Pattern - Failed

[VibhuV]

Based on the task description :

• 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.

I have tried everything and still receive this error "Did you check the Windows OS - Servers pattern extension section is configured correctly to collect ..."

Please see the attached screenshots. Any help or assistance would be appreciated

[prasanna_da]

were you able to grab the voucher for cis

[atta]

I’m facing the same issue—even though the description field has been correctly updated with the Processor Name during rediscovery.

[Zurli]

✅ SOLVED: Windows OS - Servers Pattern Extension - Task Passed

Hi everyone!

I also had trouble with this task. Everything looked right — the Windows Server's Description field was updated with the processor name, but the validation still failed.

After some trial and error, I figured it out. Here's what worked for me:

🛠️ What Worked

Pattern Name: Windows OS - Servers
Extension Section Name: Windows OS Extension

Step 1: Enable Debug Mode

• Debug Type: Horizontal
• Host IP: your Windows MID Server IP (e.g., 10.x.x.x)

Step 2: Add These Pattern Steps

1. WMI Query - Get Processor Name

• Operation: WMI Query
• Namespace: root/CIMV2
• Table: Win32_Processor
• Fields: Name
• Target Table: $cmdb_ci_win_server

2. Set Description Field

• Operation: Set Parameter Value
• Name: $cmdb_ci_win_server[1].short_description
• Value: $cmdb_ci_win_server[1].Name

🔄 Final Steps

1. Click Save (do NOT publish)
2. Go to MID Servers, select windows_mid, and click Pattern Sync to MID
3. Run Discovery against IP 192.168.16.11
4. Confirm the Description field of the Windows Server shows the processor name
5. Click Validate Task

⚠️ Tips if Validation Still Fails

• Use short_description, not name
• Use index [1], not [0]
• Sync pattern to MID is required
• Run Discovery against the Windows target, not the MID Server

Hope this helps!
If this solved your problem, please mark my reply as the Accepted Solution and click Helpful so others can find it too.

Let me know if you need help reviewing your steps!

[EmilH2267059032]

Works! Many thanks for sharing! The issue was that one has to Run Discovery against IP 192.168.16.11 rather than the MID server IP. 

[roehltablada]

Hi @VibhuV ,

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