We are seeing an issue with the unique situation described in the title, summarized as follows -
This works fine as expected:
This does not work as expected:
It appears if the old AMT FQDN resolves to a different system, than the RCS cannot manage the system remotely at all (fails to get password as well with same error).
I have found that if I manually edit the hosts file to force DNS resolution of the old AMT FQDN to the correct system, everything works fine.
Is there any recommended way to handle this scenario outside of manual edits to the hosts file? We are a large heterogenous organization and it is difficult for me to mandate what happens when systems are renamed in another unit, but I need to ensure AMT remains healthy on our fleet. Has anyone encountered this situation and found a method of resolving this within the SCS?
This document seems to indicate that the SCS software used to use a similar trick to resolve this problem, but perhaps this approach is no longer in the software?