JEA Discovery issue in ServiceNow

[Hanumant Madan1]

Hi All,

We are trying to use JEA approach for discovering windows servers.

We have configured instance and endpoint as instructed in the document, however we are still facing below error.

Document reference: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0965705

Credentials are validated successfully but the discovery fails with below error in ServiceNow.

Classification payload is empty. Stopping classification.

Has anyone seen this before.

on Powershell getting below error:

PS C:\Users\jma> Enter-Pssession -ComputerName 10.1.2.3 -ConfigurationName JEA_Config -Credential $nonadmin
Enter-Pssession : The term 'Select-Object' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Enter-Pssession -ComputerName 10.1.2.3 -ConfigurationName JEA_Confi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Select-Object:String) [Enter-PSSession], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Regards,

Hanumant

[pratiksha5]

Try this command from mid server Powershell

gwmi win32_operatingsystem -computer <target_IP> -credential '<domain\User-Name>'

Check if you get any error

[Hanumant Madan1]

Hi pratiksha, isn't this command for WMI?

we are trying with WinRM here, not sure if this command can help here, let me know.

Regards,

HM

[pratiksha5]

You are right it is a WMI command. 

check this out : https://www.servicenow.com/community/itom-forum/windows-classify-error-quot-classification-payload-i...

[MattSN]

For anyone who gets "Classification payload is empty. Stopping classification." The issue is with your certificate or lack of certficate. You must have the certificate in place on both the MID Server and the target for discovery, per the instructions in https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0965705 

It will not work with the PowerShell execution policy set to unrestriced as designed.