ServiceNow Discovery Fundamentals on Demand - Simulator 1.9.5 Task: Extend Windows OS - Server Patterns

Peter Seres
Giga Contributor

Dears,

I am struggling to complete this last task in my simulator. The requirement is detailed below.

find_real_file.pngI would be grateful if someone could help out with a walkthrough. I find that the training does not provide sufficient background to resolve this. Spent hours on this task already.

Thank you in advance,
Peter

 

18 REPLIES 18

Thank you 

Good guidance - thanks 

thanks, it works.

This worked, many thanks

Arpan Baishya
Kilo Sage

Hello,

 

I grappled with this lab exercise for hours before I was finally able to get it right. I would like to put forward what I did so that it can help others who are struggling to complete this activity. And I will do my best to keep it simple and accessible.

 

Disclaimer - I am not an ITOM expert. At the time of writing this answer, I am merely a student of CIS-Discovery who is new to the world of ITOM Visibility.

 

Here are the steps -

 

  1. Navigate to Pattern Designer > Discovery Patterns. Filter the name column for 'Windows OS - Servers'. Open the only record that the filter returns.

  2. Head to the Extension Section and create a new Extension Section called Windows OS Extension.

  3. Enable Debug Mode by doing the following.

    • Select MID Server - windows_mid
    • Host name IP - 198.51.237.194 (Why? Because this is the IP address of your Windows MID Server)
    • Click Connect.
    • Enabling Debug Mode can take a few minutes. Wait for the debug to finish successfully and then close it.
  4. Create your first step. Give it a name of your choice (I named it "Collect Processor Name").
  5. Fill in the values (screenshot attached).
    • Operation - WMI Query
    • Namespace - "root/CIMV2"
    • Select Table Name and fields - Win32_Processor and Name
    • Target Table - $cmdb_ci_win_server
  6.  Save the step and click the Test button to test this step (recommended).
  7. Confirm that the Test runs successfully. Check the output and see if you find the Processor Name under the Name column (check screenshot attached).
  8. Now, create your second step. You can name it 'Filter table' or something of your choice.
  9. Fill in the values (screenshot attached).
    • Operation - Filter Table
    • Source Table and Target Table values - $cmdb_ci_win_server
    • Query - $cmdb_ci_win_server[].Name - Contains - Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
  10. Save the step and click the Test button to test this step (recommended).
  11. Confirm that the Test runs successfully. Check the output and see if you find the Processor Name under the Name column like step 7.
  12. Now, create your third and final step. You can name it 'Set Processor Name' or something of your choice.
  13. Fill in the values (screenshot attached).
    • Operation - Set Parameter Value
    • Value - $cmdb_ci_win_server[1].Name (Why? Because we found the Processor Name under the Name column in some of the previous steps)
    • Name - $cmdb_ci_win_server.short_description (Why? Because that's the field the lab activity wants us to populate)
  14. Save the step. You don't need to test this step as such.
  15. Now, go to the MID Server list, checkmark windows_mid and click Pattern Sync to Mid to synchronize the updated pattern with the MID Server.
  16. Now, I would highly recommend you navigate to Discovery > Discovery Schedules and open the Windows Only Schedule record. Under the Discovery IP Ranges Related List, open the IP Address Range record.
  17. If your Ending IP is configured to 198.51.188.74, please change it to 198.51.237.194 (this is the IP of the Windows Server record you are trying to update) and save the record (screenshot attached). We are changing the value because this IP falls outside of the previous range configured and without doing so, our Windows Server will not fall under any existing Schedule for us to run Discovery.
  18. Now, go to your Windows Server record with OS as Windows 2012 R2 Standard and click Discover Now.
  19. Wait till Discovery finishes running and then go back to the Windows Server record and confirm that you are seeing the Description field updated with "Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz" (screenshot attached).
  20. This indicates that the lab has been successfully completed. You may now validate the task on Now Learning.

So, I hope these steps helped you with what you were looking for. Let me know if you found this answer helpful.

 

Thanks for reading.