Windows Server discovery though Just Microsoft JEA

[Amit Panjwani]

Hi All,

What are the challenges and limitations we have for discovery with Microsoft Just Enough Administration (JEA) using WINRM in comparison with traditional  discovery approach using WMI which required Local admin credentials?

Thanks,
Amit

[Abbas_5]

Hello @Amit Panjwani,

Please refer to the below link:
https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/conc...

Mark my correct and helpful, if it is helpful and please hit the thumbs-up button to mark it as the correct solution.
Thanks & Regards,
Abbas Shaik

[Sohail Khilji]

Hi @Amit Panjwani ,

We recently implemented discovery via JEA, 

Challenges :

1. Certification will be a challenge, you need to move then to each servers via SCCM for validation.

2. Ports will be different 5986 & 5885

3. Mid server related configure would be required, you need to update the config file as needed for JEA.

4. Port probe classification needs to be updated with order.

Limitations: we did not face any limitations as compared to normal wmi discovery. It was efficient and getting us as much info as possible.

I hope this helps...

[jimmillet]

Sohail,

What changes did you need to make for port probe classification order?
Jim

[MartinKolodzey1]

Hi, we encountered the challenge that JEA worked but the Certificate scan did not. Message was that there are no credentials for WMI and the midserver is configured for WMI only.

I found this very helpful post and in lack of an ordering field I deactivated the WMI probe. We use JEA exclusively and therefore it was redundant anyway. After deactivation of this probe the discovery run yielded excellent results.