"Connection failed to WMI service. Error: Permission denied" after upgrading to Madrid
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2019 06:24 AM
We recently upgrade to Madrid in our Dev environment. We now noticed that our Windows discovery is failing with "Connection failed to WMI service. Error: Permission denied" in Dev. In Prod, it has no problem against the very same target.
Does anyone know what could have changed? It has to be the Madrid code, but what?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2019 06:48 AM
Have you checked/confirmed that all your MID Server settings and configurations are correct on your Dev instance. There can be times when clones and upgrades can affect the values you set (and need).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2019 06:27 AM
We discovered that in Madrid Patch 5, they created a MID Server property (not documented) called mid.use_legacy_wmi that allows you to revert Windows Discovery back to the way it previously was before the drastic change in Patch 3. 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2019 01:33 PM
What are the security implications of basically undoing what the patch did? Are you sure the patch did not change the way WMI works because of vulnerabilities in the legacy version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2019 02:07 PM
Can you pls check if the credential had domain name as prefix. If that is not the issue, then you need to check if the credential that you are using has access to adminshare ($admin\temp) on the target windows machine.
