Thank you for your response.
To answer your questions:
We use DHCP for our clients. (Only the servers have a fixed IP.)
I don't see an error code 91 in the log.
We don't use a dedicated network file as described in the three scenarios you list above.
The two errors that keep showing up are always the same:
- "A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target. (0xc000521c). "
- "Finish operation with Error (0xc00007d2) - Initial connection to the Intel(R) AMT device failed. (0xc00007d2). A TCP error occurred."
The network IP Settings section of my configuration Profile is identical to the one shown on page 127 of the 'User Guide'.
Consequently, one would expect it to be the same between Host and AMT device.
That said - and I want to thank you for the hint - it most likely isn't. Because, if for testing's sake, I create a Reservation in DHCP, so that a "lost" client is guided back to the IP address the SCS console holds, password retrieval works and the 'Connection Status' returns to 'Connected'.
For now, I'll try to find out why Host IP address and AMT Device IP address are not aligned and might have further questions.
...in the meantime:
The log of an .\acuconfig.exe systemdiscovery attempt:
PS C:\> .\ACUConfig.exe /output console systemdiscovery
Starting log 2018-04-09 17:30:21
ACUConfig 11.2.0.35
[ClientFQDN]: Starting to discover the system information...
Wire support:************** 1
System Discovery failed to get data from some of the interfaces on this system.
Failed to get data from the GetDNSLookupName interface.
Failed to get the FQDN.
Call to function failed.
DNS server failure.
***********
Exit with code 32.
Details: Intel(R) AMT operation completed with warnings:
System Discovery failed to get data from some of the interfaces on this system.
Failed to get data from the GetDNSLookupName interface.
Failed to get the FQDN.
Call to function failed.
DNS server failure.
What I notice, .\acuconfig.exe systemdiscovery does correct the IP address stamped into the registry of the client
Disappointingly, .\acuconfig.exe systemdiscovery /ReportToRCS /RCSaddress [FQDN of RCServer] make no impression on the connection status in the SCS console.
Again, thanks for your help.
Martin