There is a need to roll back Legacy WMI Update Sets to support the new Paris Windows discovery


Description

Discovery in Madrid Patch 3/New York/Orlando added Windows WMI probe code that required Powershell and admin$ share access on targets, and many customers had to apply an update set provided by ServiceNow to allow the previous WMI functionality to work.

Discovery in Paris adds that WMI support back OOTB, but to allow Discovery to work, the customizations in the update sets needs reverting, and the update sets backed-out.

As the solution to this problem a fix script will be added to the upgrade code to automatically back-out the several differetn versions of the "Revert_To_Legacy_WMI" update sets with these sys_ids:

A communication was also sent out to all the customers identified as having applied this update sets.

Steps to Reproduce

  1. Take a Madrid, New York or Orlando instance
  2. Apply 1 or more of the update sets attached
  3. Upgrade to Paris
  4. The update set are still applied causing Windows Installed Software discovery to brea

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

After the fix, the update set(s) should be automatically rolled back.

In the meantime, the roll-back can be done manually:
KB0860580 Removing customisations of Discovery Windows WMI probes, that had been applied for the changes in Madrid Patch 3/New York


Related Problem: PRB1447649