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
352
stars
75
forks
source link
Agentless Setup - Devices imported via MeshCmd defaulting to IP instead of hostname #45
Having a new issue here in our agentless environment where the device will no longer be imported using its FQDN hostname after adding it via meshcmd. This used to work fine, but about a month ago when we updated to address different issues it started falling back to IP.
We looked into it being a DNS issue but even the server seems to pick up the hostname fine during the add process - it just doesn't show up in the device info afterward. We updated again today to latest but the issue is still persistent.
ad-85
commented
3 years ago
Having a new issue here in our agentless environment where the device will no longer be imported using its FQDN hostname after adding it via meshcmd. This used to work fine, but about a month ago when we updated to address different issues it started falling back to IP.
We looked into it being a DNS issue but even the server seems to pick up the hostname fine during the add process - it just doesn't show up in the device info afterward. We updated again today to latest but the issue is still persistent.
Versions:
Server log excerpt during add:
Ping/NSlookup test
Sample device: