How to debug WinRM/WMI from FGLAM side?
To view the exact connection used, you can add the following property when running fglam:
-Dquest.debug.windowsinfo.types=true
Kerberos/Negotiate authentication is used by default and only fully qualified domain administrator accounts are permitted.
For Basic authentication, which requires extra setup, only local Administrator accounts are permitted.
Once the above has been implemented, run the following command (from FglAM)to verify connectivity between FglAM and target host on WinRM (change port as appropriate):
Note that for WMI there can be two printouts depending the type of WMI connection used, either ‘WMINativeConnectionImpl’ or ‘WMIJavaConnectionImpl’. For WinRM, instead of ‘WMINativeConnectionImpl’ you will see ‘WinRMConnection’.
The IC agent itself decides what WinRM port will be used when it is running and it only tries the default ones, 5985 and 80 for HTTP connections, 5986 and 443 for HTTPS connections. FglAM will use whatever port is provided to it.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center