Regression: Connect-HPEiLO fails with “Server Information could not be determined for EISA ID” when run as SYSTEM on a ProLiant MicroServer Gen10 Plus v2

HPE iLO PowerShell Cmdlets:
- Working: 3.3.0.0
- Failing: 5.1.0.0

Server:
- ProLiant MicroServer Gen10 Plus v2
- iLO 5 firmware 3.16
- System ROM U64 v2.50

OS:
- Windows Server 2022 (PowerShell 5.1)

Execution Context
- Tested under SYSTEM and interactive user
- Regression is SYSTEM-context specific

**Result on 5.1.0.0: (Running under SYSTEM context)**
_Connect-HPEiLO -IP 192.168.1.240 -Username xxxxx -Password xxxxx -DisableCertificateAuthentication_
WARNING: [192.168.1.240] DNS name translation not available.
Connect-HPEiLO : [192.168.1.240] : Server Information could not determined for EISA ID: $0E11089A At line:1 char:1 + Connect-HPEiLO -IP 192.168.1.240 -Username xxxxx -Password xx + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [Connect-HPEiLO], Exception + FullyQualifiedErrorId : HPE.iLO.Cmdlet.Connector.ConnectHPEiLO

TLS handshake and authentication succeed, but the cmdlet aborts during Redfish/EISA platform detection.

Running 5.1.0.0 under User context - works correctly.

**Result on 3.3.0.0: (Running under SYSTEM context)**
_Connect-HPEiLO -IP 192.168.1.240 -Username xxxxx -Password xxxxx -DisableCertificateAuthentication_
WARNING: [192.168.1.240] DNS name translation not available.


IP : 192.168.1.240
Hostname :
Timeout : 30
DisableCertificateAuthentication : True
TargetInfo : @{ProductName=ProLiant MicroServer Gen10 Plus v2; ServerFamily=ProLiant; ServerGeneration=Gen10Plus;
ServerModel=MicroServer; iLOGeneration=iLO5; iLOFirmwareVersion=3.16; SystemROM=U64 v2.50 (08/06/2025);
ProcessorName=Intel(R) Xeon(R) E-2314 CPU @ 2.80GHz}
ExtendedInfo : @{UserSuppliedAddress=xxxxx; HttpConnectAddress=xxxxx; UserName=xxxxx;
Modifier1=xxxxx=; Modifier2=xxxx==}
ConnectionInfo : @{Redfish=}

We have Solarwinds monitoring tools which use PowerShell under System hence this has flagged up.
This is the only server I have that is a ProLiant MicroServer Gen10 Plus v2 - all my other bigger servers work fine under system context with 5.1.0.0 so I assume it's product related with 5.1.0.0