- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 06:06 PM
[Rome]
I've enabled JEA discovery on 2 Azure Windows servers. They seem to be configured identically, but while I'm getting a good discovery from one of the servers, the other one is giving me this error, and I can't seem to find any reference to it or what might be the cause:
Discovery log shows this Warning: "Classification payload is empty. Stopping Classification" from WMI Runner input
Here's the first few lines from the input XML from WMI: Classify
<results probe_time="35201" result_code="0"
<result>
<output> { } </output>
</result>
I believe the credential login is successful, as a credential test is successful and also the sys_id of the proper JEA credential is referenced in the XML. Maybe something is preventing the execution of the classification probe commands, so a null/empty output results?
Any troubleshooting suggestions?
-thanks
Bob
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2022 01:13 PM
This is resolved
JEA for Discovery requires a certificate, and I found out the certificate was not properly imported on the second VM. Corrected that and discovery works properly now.
Appreciate the help
-Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2022 01:11 AM
Hi Bob,
I feel this is wmi connection problem, Please follow below steps by logging into mid server:
1. Log in to Mid server & try to rdp the target server- If you are not able to rdp then reach out to server team for rdp access.
2. Next use below powershell command on target server to check wmi connection:
get-wmiobject win32_operatingsystem -computer IP ADDRESS -credential ‘USER NAME'
Hope it helps!
Thanks
Deepti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2022 01:13 PM
This is resolved
JEA for Discovery requires a certificate, and I found out the certificate was not properly imported on the second VM. Corrected that and discovery works properly now.
Appreciate the help
-Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2023 12:51 AM
Hi Bob,
Thanks for sharing. I'm facing the same issue. Could you pls share some detail about how to resolve it? I have no idea about how to get the cert and how to import it..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 06:09 AM
I am getting the same error and have the certificate installed on target server and Mid-server properly. I validated the credentials and had the Port 5985 open. Everything still in place correctly but still I am facing the issue. Can anyone please help me on this?
Does anyone have the detailed instructions on how to setup JEA Discovery including all PowerShell commands and required list before configuring the same?