MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
Apache License 2.0
369
stars
80
forks
source link
MeshCommander - Missing "Optional Token Request" parameter in nw.exe #46
Would it be possible to add the "Optional Token Request" as an parameter for nw.exe ?
Reason for asking is due to that when we perform "PXE Boot" our DHCP server removes the DNS record for the machine.
In our setup, the DHCP Server owns the DNS records, and since PXE Boot can't present any "machine name", the DNS record is removed automatically.
At this stage, MeshCommander will struggle to communicate with Intel AMT if it's need to resolve IP.
So if we could add this parameter, we could connect with IP and at the same time use the Kerberos authentication :)
The Intel AMT device is provisioned with "Intel SCS" and the admin password is randomized, so we have not other alternatives to authenticate than kerberos as we don't know the admin password in current scenario.
The MeshCommander is started by a script due issue discussed here
Hi @Ylianst
Thanks for your great tool!
Would it be possible to add the "Optional Token Request" as an parameter for nw.exe ?
Reason for asking is due to that when we perform "PXE Boot" our DHCP server removes the DNS record for the machine. In our setup, the DHCP Server owns the DNS records, and since PXE Boot can't present any "machine name", the DNS record is removed automatically.
At this stage, MeshCommander will struggle to communicate with Intel AMT if it's need to resolve IP. So if we could add this parameter, we could connect with IP and at the same time use the Kerberos authentication :)
The Intel AMT device is provisioned with "Intel SCS" and the admin password is randomized, so we have not other alternatives to authenticate than kerberos as we don't know the admin password in current scenario.
The MeshCommander is started by a script due issue discussed here
That would be really helpful!
Best Regards Horgster