Unable To Discover an MS Windows Os Instance due to Wmi Access Errors
(Doc ID 1588314.1)
Last updated on JULY 20, 2023
Applies to:
Enterprise Manager Ops Center - Version 12c (12.1) and laterInformation in this document applies to any platform.
Symptoms
This failure occurred when following the online docs for a Windows client discovery. We first tried creating a separate account with just the WMI "Remote Enabled" privileges. We also ran the CMD command to enable to firewall for Windows Server 2008 R2. The OC discovery job failed almost immediately. We tried with the Administrator account, and verified it too had "Remote enabled" WMI permission. This also failed.
The Administrator account has ALL the options in WMI enabled/checked off, so the root cause of the discovery failure was tricky to find. The Job log data will provide some information on the failure itself:
Changes
NA
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |