I have been having an issue with Windows Credentials for my Discovery. I have been through a laundry list of trouble shooting steps including remote connecting to a target server from the mid server host via WMI, connecting using a powershell commands, RDPing using the wmi credentials on the instance from my computer, and RDPing from the mid server host machine with the same credentials. All of these methods have comeback clean but I continue to receive this error back in the ecc from the windows classifier probe:
<error>Authentication failure with the local MID server service credential.</error>
<error>Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))</error>
<debug_info>{"debug_info":[{"xxxxxxxxxx":{"creds_failed_trying_local_mid_cred":true,"credentials_attempted":[{"credential_type":"Windows","credential_name":"WMI Credential","credential_order":"100","credential_success":false,"credential_id":"*windows credentials*"}],"local_mid_credential_success":false,"connection_parameters":{"credential_types":["Windows"],"target":"xxxxxxxxx"}}}]}
I'm now getting our Windows server team involved but the problem is I want to be able to show them the actual command the midserver is sending that is responsible for trying to log onto these target machines. I can not seem to find them on the instance under any of the windows probes.
As a follow up, we are running on New York, would it be a good idea to try and do a migration from probes to patterns for windows devices? I have heard patterns cam make trouble shooting a lot easier.
Thanks in advance
