Hello,   good point, you have right, the tool is working via IP address, not via FQDN only, which I have set in the scripts. I found, that the web face also is not working via FQDN anymore, and I also found the reason. During the upgrade to these newest iDrac versions is automatically changed "Auto Config Domain Name" to enabled in common iDrac settings. So, the filled "Static DNS Domain Name" is removed, and the FQDN access just stops working. I have no idea, why is this change performed during the upgrade, if is some objective security reason for this? Thank you in advance
Hello,   I would like to ask, what was changed in iDrac 9 generation 6 (exactly [URL] that I am not able to login to the iDrac via powershell module "DellPEWSMANTools". There was no problem until iDrac version 5.10.00.00, which we used previously. I don´t see any difference in HTTPS setting, so I have no idea, why the login is not working anymore. Version of DellPEWSMANTools 1.2.0.0 (I am not sure, if is newer) Error message: New-CimSession : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.   And of course, I am using thise setup, maybe needs to be something changed in this secure setting: $Cimop=New-CimSessionOption -SkipCACheck -SkipCNCheck -SkipRevocationCheck -Encoding Utf8 -UseSsl $Session= New-CimSession -Authentication Basic -Credential $Credentials -ComputerName $server -Port 443 -SessionOption $Cimop Thank you
DellPEWSMANTools stops working on iDrac9 gen6