Scheduled Discovery not able to find valid credentials for Windows Discovery but working manually
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8 hours ago
Hi Everyone,
I have a few Windows Server CIs that are unable from being Discovered through our Scheduled Discovery running on the weekends. I'm getting the "Could not find any valid credentials to authenticate the target for type [Windows]".
We use a CyberArk credential and it's working fine when you do do manual discovery. I've also configured the Credential Affinity. I've tried manually discovering with the same MID Server, MID Server Cluster, and through the "Discover Now" related link and they've all worked but when the Discovery Schedule runs on the weekend, it ends up not finding any valid credential.
I've also checked the ECC queue records and found that it's trying the exact credential that works when doing manually discovery but it fails during the Scheduled Discovery execution.
Has anyone else experienced this issue?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
I have same issue:
Message: "Could not find any valid credentials to authenticate the target for type [Windows]"
Credential: Windows
Account: Domain/discoveryaccount
ECC queue input: WMIRunner