Discovery Admin Share

Tuna · ‎10-11-2019

Hi Guys,

Since we've upgraded our instance to New York, Discovery requires a admin share on Windows Servers to work properly. Right now we do not have an admin share on our Windows Servers which results in failing discoveries because of following error message:

Is there a way to switch back to the old Discovery method without the necessity to have an admin share on the target system?
This is currently very critical for us and I am assuming that it can't be the only solution to set up an admin share on every Windows Server that needs to be discoverd.

See also following link to the doc: https://docs.servicenow.com/bundle/newyork-release-notes/page/release-notes/summary/rn-summary-chang...

Any help is appreciated.

Best Regards

Tuna · ‎10-22-2019

Following steps are required to switch back to the legacy WMI Discovery:

Contact ServiceNow Support and ask for the Update Set "WMI_Revert_To_Legacy_Discovery". Load and Commit this Update Set on your instance. The Update Set already contains the MID Server Property mid.use_legacy_wmi. It also contains some changes to the Probes to prevent WMI to use the admin share.

After committing the Update Set the first Discovery run takes a bit longer than usual but the second one then works as expected.

View solution in original post

tompowe · ‎10-11-2019

Try setting this property to true: mid.use_legacy_wmi

This sets Discovery back to the way things were working in Kingston, I think.

Tuna · ‎10-11-2019

Didn't work unfortunately. I also couldn't find any MID Server Parameter that could match.

tompowe · ‎10-11-2019

This is a MID Server Property, not Parameter. Go to MID Server -> Properties and create it.

Tuna · ‎10-15-2019

Ok, got it. Created a MID Server Property with name "mid.use_legacy_wmi" and set it to "true" with the result that it failed during Classification. Did some furhter tests and set the Property to "false" with the result that the Discoveries succeeded. Also created a Case to get further assistence.

Somehow it is misleading that setting the Property to "false" results in the old behaviour.
Will keep this post updated as soon as I have some more information about it.