Hi,
We use an AD Service account for iDRAC discovery and most of the time this works fine. However, I've noticed that for some iDRAC's we cannot get anything more then the information provided by a ping. I could login to the troublesome iDRAC fine with the AD service account using a web browser to prove its not an authentication issue.
However, when I test using the troubleshooting tool I get the response "Connected. Could not collect WSMAN profile data":..
Out of 124 Devices on the subnet range I get this issue with perhaps half. I have also raised the privilege for the AD service account to Admin, this was no help. Using a local account on the iDRAC in the troubleshooting tool returns the expected result.
I looked into 2 iDRACs that don't show properly in OME and found they were both v 3.30 (build 17). Could this be an iDRAC version specific issue? Any tips to resolve please?
We'd prefer NOT to use local iDRAC credentials for discovery in OME.
Regards,