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

Marc_See · ‎05-01-2020

Performance decrease, more CPU utilization and memory consumption. Check out SN's KB article:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0752537

Community Alums · ‎05-01-2020

Thanks Marc. One more query I have though it's from different context. If it is okay can I ask here.

Marc_See · ‎05-03-2020

I'll try to help, but I think i'm on the same boat as you 🙂

Community Alums · ‎05-04-2020

Thanks Marc.

Does Vcenter event collector removed events only marks VM instance as Stale or it also Stale CI as well .

Marc_See · ‎05-04-2020

I honestly don't know. You might want to create a new question so someone might be able to see this easily and respond to you.