ylianst/meshcommander

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.

MeshCommander

*** Intel has discontinued support for this tool. Please contact Intel support for alternatives ***

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 directly from the Intel AMT web server. There are different ways to install and use MeshCommander.

Windows Installation

On Windows, simply go to MeshCommander.com/meshcommander and download and install the MSI installer.

NPM Installation

On Windows, Linux and MacOS, you can install MeshCommander from the Node Package Manager (NPM). Once you have NodeJS installed on your computer, you can do:

	mkdir meshcommander
	cd meshcommander
	npm install meshcommander
	node node_modules\meshcommander

This will start a small web server on port 3000 that you can access using a browser to use MeshCommander at http://127.0.0.1:3000.

Firmware Installation

For Intel AMT 11.6 and higher, you can load MeshCommander directly into Intel AMT storage flash space. Depending on the activation mode, MeshCommander can replace the default Intel AMT web page on HTTP/16992 or HTTPS/16993 making the built-in web site much more capable. On Windows, you can download the firmware installer here. On other platforms, you can use MeshCMD to load MeshCommander into Intel AMT.

MeshCMD Installation

On Windows and Linux, you can download MeshCMD, a command line tool for performing many Intel AMT management operations. Included in that tool is MeshCommander. You can start it up by running:

	meshcmd meshcommander

Like the NPM version, this will start an HTTP web server on port 3000. You can then access http://127.0.0.1:3000 from any browser to access MeshCommander.

Compiling MeshCommander

MeshCommander is a set of HTML web pages that can be used in many different ways. You can run it in a browser or in nw.js, you can run it as a stand-alone application or as a web application served from Intel AMT. Because of all the different roles MeshCommander can take and the unique requirement of being able to fit within 64k limit of Intel AMT file storage, MeshCommander has to be "compiled" using the WebSite Compiler tool that currently only runs on Windows. WebSite Compiler will merge all of the html, css and js files into a single big file, it will run a pre-processor to remove portions that are not needed and then minify and compress the output as needed.

Tutorials

There are plenty of tutorial videos here.

Introduction to MeshCommander.

License

This software is licensed under Apache 2.0.

meshcommander's Issues

How to enable AMT Redirection port and KVM feature from Setup.bin?

I've configured Setup.bin as:

But after provisioning, the AMT Redirection port and KVM features are not enabled:

How do I enable them in Setup.bin?

BTW, I'm trying to document a basic AMT setup at rgl/intel-amt-notes.

Feature Request: Allow for multiple meshcmd routes

My use case is that I have multiple devices that I want to route SSH through.
So on one local PC, I want to be able to have these tunnels open simultaneously.

localhost:1022 -> remote1:22
localhost:2022 -> remote2:22
localhost:3022 -> remote3:22
etc...

Currently, meshcmd accepts no inputs (other that password/token) and expects a single meshaction.txt file to be in that same directory for a single tunnel.

In order to do what I want,(I think) I would have to have multiple directories (one for each remote) with different, preset meshaction.txt files for each remote I want to connect through and a copy of meshcmd to run in that folder alongside its corersponding meshaction.txt file. e.g:

├── remote1
│   ├── meshaction.txt
│   └── meshcmd
├── remote2
│   ├── meshaction.txt
│   └── meshcmd
└── remote3
    ├── meshaction.txt
    └── meshcmd

Ideally, I would like to populate a single meshaction.txt file with all the tunnels I want to connect to and run a single instance of meshcmd to open all those tunnels locally.

Less ideally, I suppose you could have a parameter that specifies the path to the action file you want to use. However, this would method still end up with multiple instances of meshcmd running (one for each tunnel)

MeshCommander IIS timing out

Hi, This is a new setup. When using FF or IE to access MeshCommander (MC), I can access the remote MC console I can, but when I select a workstation to access the AMT functionality it keeps timing out. Using IIS8, AMT v 12. These are on the same subnet.
I can access and use the MC app and it works great to access AMT. Thanks

Multiple Support Desk Stations

I have setup a Support Desk Station using MeshCommander on a Windows10 computer. I have entered the 75 Intel AMT provisioned workstations I need to KVM to and setup the TLS and certificates. I would now like to add a couple of additional Support Desk Stations and would like to know how I can copy/export the list of 75 workstations I have in my original MeshCommander and copy/import them into the new MeshCommander installs so that I don't have to go through adding and setting up TLS for all 75 workstations every time I add a new MeshCommander install.

Also, congratulations to you and your team on creating an absolutely fabulous software application.

Is it possible to set AMT to activate network interface via the setup.bin file?

I got the setup.bin file configured and tested it out on a host and it doesn't activate the network interface.
Is this something we configure in the setup.bin file? I don't see a variable to configure that in the MeshCommander setup.bin manager.

Thanks

Add GitHub URL to meshcommander npm package

It would be nice to have a link to this GitHub repository at https://www.npmjs.com/package/meshcommander

For doing this just follow https://docs.npmjs.com/files/package.json#repository

Oh, looking at the package.json file, it seems to be an nw app, which means the npm package does not comes from this repository at all?

Attempts to load MeshCommander into Intel AMT via Firmware Loader and MeshCMD result in error message

Hi @Ylianst, I finally got around to trying out MeshCommander's Intel AMT integration with my Intel NUC earlier today but I've been running into some issues that I haven't been able to solve yet.

NUC Model: NUC7i7DNHE
BIOS: Intel Corp.DNKBLi7v.86A.0069.2020.0610.1805 (latest)
Intel AMT Firmware: 11.8.77.3664 (latest)
Intel ME Driver: 1950.14.0.1370 (latest)

I started the process today by installing the latest BIOS and firmware for this NUC model, rebooting it, entering the Intel MEBx menu by pressing CTRL+P and changing the default password admin to a different one. Next, I enabled the networking feature and restarted the NUC again.

The Intel Management and Security Status software shows that Intel AMT is "Enabled", that the Connection Status is "Connected" and that the Intel ME is "Configured" with Control Mode "Admin". I am also able to visit and log into the default Intel AMT website at localhost:16992 using the password I set up in Intel MEBx earlier.

The problem I'm facing right now is that when I try to flash the MeshCommander website onto Intel AMT using the latest Firmware Loader (irrespective of whether I choose the Standard or Advanced version), the upload fails with the error message "The remote server returned an error: (500) Internal Server Error."

When I first encountered this error, I downloaded meshcmd.exe and tried flashing the website by using the AmtLoadWebApp command instead, but the upload also fails that way with the error message "Error, check that computer is powered on." The computer is definitely turned on since I'm running both programs from the NUC itself.

Please let me know if you need any additional info in order to troubleshoot this issue.

IDE-R not working on Linux

When I run Meshcommander (currently 0.8.6a, installed through npm) on Linux, IDE-R does not work properly.

I can select an ISO, it is displayed for some seconds (0 in, 18 out), and then disappears.

If I run MeshCommander in a Windows machine, installed with the official installer, IDE-R works properly.

The target machine is the same in both cases.

Can only connect using RLE 8 / RAW8

Connection fails when using another encoding then RL8/RAW8. It then keeps on continuously connecting/disconnecting.

Running AMT 11.8.65 on a Intel® Core™ i5-7500T CPU @ 2.70GHz
 

Remote Desktop with the web app does not work with AMT 12.0.22.1310

With 11.8.70.3626 the WebSocket messages look like this:

-> 10:01:00:00:4b:56:4d:52
<- 11:00:00:00:01:00:0b:08:57:01:00:00:00

-> 13:00:00:00:01:00:00:00:00
<- 14:00:00:00:01:00:00:00:00

-> 40:00:00:00:00:00:00:00
<- 41:00:00:00:00:00:00:00:52:46:42:20:30:30:34:2e:30:30:30:0a

With 12.0.22.1310, this happens (it fails to skip authentication):

-> 10:01:00:00:4b:56:4d:52
<- 11:00:00:00:01:00:0c:00:57:01:00:00:00

-> 13:00:00:00:01:00:00:00:00
<- 14:02:00:00:01:00:00:00:00

If I connect directly with MeshCommander, it authenticates and then the RFB session works:

-> 10:01:00:00:4b:56:4d:52
<- 11:00:00:00:01:00:0c:00:57:01:00:00:00

-> 13:00:00:00:00:00:00:00:00
<- 14:00:00:00:00:01:00:00:00:04

-> 13:00:00:00:04:20:00:00:00:*
<- 14:01:00:00:04:4e:00:00:00:*

-> 13:00:00:00:04:b3:00:00:00:*
<- 14:00:00:00:04:00:00:00:00

-> 40:00:00:00:00:00:00:00
<- 41:00:00:00:00:00:00:00:52:46:42:20:30:30:33:2e:30:30:38:0a

I'm using MeshCommander v0.8.8.

error 400 when enabling vnc

I would like to enable vnc

and set in remove desktop : Port 5900 to Enabled, Legacy KVM viewers and added a 8 chars password.

Unfortunately I get Error 400, unable to set values.

Any idea? tx

Unable to set IPv6 state, error 400 when configuring IPv6 from MeshCommander

Hello,

while attempting to change the IPv6 network configuration using MeshCommander, I only get a pop-up window with the following error:
Unable to set IPv6 state, error 400

When I go to the AMT website directly, I am able to configure IPv6 there.

When capturing the session from MeshCommander to an unsecured AMT port using tcpdump, this is what I get (authentication headers redacted, XML pretty printed) when trying to disable IPv6 on an already IPv6-configured interface (it's the same HTTP result when enabling it, but probably with different data):

POST /wsman HTTP/1.1
Authorization: Digest username="admin",realm="(...)",nonce="(...)",uri="/wsman",qop="auth",response="(...)",nc="(...)",cnonce="(...)"
Host: (...):16992
Content-Length: (...)

<?xml version="1.0" encoding="utf-8"?>
<Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns="http://www.w3.org/2003/05/soap-envelope">
  <Header>
    <a:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Put</a:Action>
    <a:To>/wsman</a:To>
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ElementSettingData</w:ResourceURI>
    <a:MessageID>205</a:MessageID>
    <a:ReplyTo>
      <a:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
    </a:ReplyTo>
    <w:OperationTimeout>PT60.000S</w:OperationTimeout>
  </Header>
  <Body>
    <r:CIM_ElementSettingData xmlns:r="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ElementSettingData">
      <r:IsCurrent>2</r:IsCurrent>
      <r:IsDefault>0</r:IsDefault>
      <r:IsNext>0</r:IsNext>
      <r:ManagedElement>
        <a:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
        <a:ReferenceParameters>
          <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_EthernetPort</w:ResourceURI>
          <w:SelectorSet>
            <w:Selector Name="CreationClassName">CIM_EthernetPort</w:Selector>
            <w:Selector Name="DeviceID">Intel(r) AMT Ethernet Port 0</w:Selector>
            <w:Selector Name="SystemCreationClassName">CIM_ComputerSystem</w:Selector>
            <w:Selector Name="SystemName">Intel(r) AMT</w:Selector>
          </w:SelectorSet>
        </a:ReferenceParameters>
      </r:ManagedElement>
      <r:SettingData>
        <a:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
        <a:ReferenceParameters>
          <w:ResourceURI>http://intel.com/wbem/wscim/1/ips-schema/1/IPS_IPv6PortSettings</w:ResourceURI>
          <w:SelectorSet>
            <w:Selector Name="InstanceID">Intel(r) IPS IPv6 Settings 0</w:Selector>
          </w:SelectorSet>
        </a:ReferenceParameters>
      </r:SettingData>
    </r:CIM_ElementSettingData>
  </Body>
</Envelope>

HTTP/1.1 400 Bad Request
Date: Fri, 22 May 2020 20:32:33 GMT
Server: Intel(R) Active Management Technology 11.8.70.3626
X-Frame-Options: DENY
Content-Type: application/soap+xml; charset=UTF-8
Transfer-Encoding: chunked
Connection: close

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:g="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:f="http://schemas.xmlsoap.org/ws/2004/08/eventing" xmlns:e="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:c="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:h="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:i="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>205</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-0000000009F8</b:MessageID>
  </a:Header>
  <a:Body>
    <a:Fault>
      <a:Code>
        <a:Value>a:Sender</a:Value>
        <a:Subcode>
          <a:Value>e:InvalidSelectors</a:Value>
        </a:Subcode>
      </a:Code>
      <a:Reason>
        <a:Text xml:lang="en-US">The Selectors for the resource are not valid.</a:Text>
      </a:Reason>
      <a:Detail/>
    </a:Fault>
  </a:Body>
</a:Envelope>

System Status - Power "Unknown"

I'm trying to configure ASUS Pro Q570M-C motherboard into MeshCommander and all is working okay, apart from being able to use "Power Actions" which I find fantastic for remote working. Can anyone tell me how to get this enabled, if it's possible?

Some functional operation questions about MeshCommander.

1. Why does the function of saving state take a lot of time to complete? The state jason file size is 1.2 MB takes about 3 minutes to save entire Intel AMT state. (System Status->Save State)

2. Can't change Link policy settings at network settings.

3. Unable to remove issue certificate by MeshCommander. (Create certificate by adding certificate it can be deleted)

4. Can't use certificate by adding certificate. It can use issue certificate by MeshCommander.

0.8.2 for npm?

Hi and thank you for this software!
Is it possible to push 0.8.2 to github/npm?
The reason is that I see a bug/problem with [email protected] on Linux (fedora31) that I don't see on [email protected] (Windows 10):
When I connect with 0.8.0 to an AMT machine (ME v11.8.70, BIOS DNKBLi7v.86A.0068.2020.0312.1938) I can only do it with Digest / None. If I select Digest / TLS and then Connect I immediately (within a fraction of a second, so not a typical IP timeout) get Time Out and a Close button below. With 0.8.2 on Windows it works without problems. In the changelog I see that 0.8.1 may contain TLS fixes - maybe these solve my problem, too?

Additional Info: with the original BIOS on this NUC from 2018, Digest / TLS did work with [email protected] on Linux, but after the BIOS upgrade this problem above showed up. It seems the Digest / TLS handling changed in between the BIOS versions.

Bad calculation of mouse position in dual screen configuration

Hi!
I am using MeshCommander 0.8.8 (installable version running on Windows 10). It is connected to NUC7i5DNHE (BIOS DNKBLi5v.86A.0069.2020.0610.1823, ME v11.8.77). NUC connected to 2 monitors, host running MeshCommander working on single screen.

When connecting ME lets me select the screen i would like to see, choosing one with F1.

Now the issue is that X position of mouse cursor is wrongly calculated. It looks like the local host position X is translated to virtual position on ME as X*2. I think processing is confused whether it is really working on dual screen (2 times horizontal resolution) or on single screen (local host running MeshCommander).

To add, this happens when host OS is Ubuntu, or Windows 10. Does not happen on BIOS (there i guess there is only one screen activated).

Kind regards,
Chris

Error 400 during script running using meshcmd

Hi!
Surely not “issue”, but … help needed.
Created in MeshCommander script which did work there ok. It includes also adding digest user. Tried to run same script using meshcmd.exe (0.2.1.3) …
Setting up MEI...
Setting up LME...
Script Started
Fetching digest realm...
Call failed: Error #400
Script Completed
… As soon I removed adding digest user, script completed ok. What I’m doing wrong?
More thanks, Alar.

meshcmd source code?

I do not seem to find meshcmd in this repository nor in https://github.com/Ylianst?tab=repositories. Can you help me find its source code?

KVM shows black screen on HP EliteBook 850 G6

When using it to remote the device, one can see that it is connected and Keyboard/Mouse input is passed through.
No image is fed back into the client.

When using VNC Viewer Plus, the screen is captured and sent to the client.

CPU Intel i5-8365U
Bios R70 Ver. 01.03.04
Intel ME v12.0.45 activated in Admin Control Mode (ACM)

MeshCommander 0.8.4 - MSI version is in use.

Proper Releases?

Looking at https://www.npmjs.com/package/meshcommander it currently has version 0.9.0-d.

Looking at https://github.com/Ylianst/MeshCommander/releases it has nothing. Nor there are any tags in this repository.

This makes things pretty confusing.

Can we please have proper releases in the repository?

Connecting with the default password...

Hi.

I'm probably misunderstanding something, but MeshCommander has a required password policy to connect to a computer (min 8 chars, upper and lowercase and a special character.)

While I applaud the enforcement of special characters, this means that I can't log into my machine after resetting the AMT to admin/admin. What's the solution here?

TTL unit display error (seconds->minutes) in Dynamic DNS setting item at Network Settings page.

TTL unit display error (seconds->minutes) in Dynamic DNS setting item at Network Settings page.

Storage Redirection

While at the prompt:

I've only inserted the .iso file with a debian live.

When I tried to boot it, it worked up until the point where linux tried to find the rootfs, which failed with some odd errors about usb 1-16: reset high-speed USB device number 3 using xhci_hcd:

It turns out that I also have to specify a floppy .img file in the Storage Redirection window.

Can MeshCommander be changed to only redirect the devices that have an image? Or automatically insert an empty ephemeral floppy disk when we only specify an .iso file? Or warn the user about this? Or refuse to work until we supply both images?

MeshCommander 0.8.4 - SOL stops working after change 80x25 to 100x30

Hi.
Following scenario:

1. Connect
2. Connect SOL
3. all works ok
4. change 80x25 to 100x30
5. Only Enter works. None of other keys are sent to the other side.

To get SOL back to working condition SOL needs to be disconnected and re-connected again.

Tested on: NUC7i5DNHE DNKBLi5v.86A.0068.2020.0312.1721 IME v11.8.70

v0.7.33 - Unable to access desktop (remote control) of any clients

Hi, this was working 28 Dec with no issues (i expect an older version than v0.7.33 which its on now as our server updates daily).

Not sure when this update happened as my server as it updates every day, but today i cant access ANY desktops from any clients (both LAN and remote). They are logging in, can only see General, Events and Details tabs for every client. Cant tell you the version of client as its not listed.

Has this broken in an update? we are running it behind an Apache web server port 443, last use3d 28 Dec with no issues, no updates to Apache or Windows.

• Cant seem to find where to get the MeshAgent either, has that moved (appears to only be in the MAIN group of each area now)?
• Also cant seem to find how to delete PCs in the console, so what ever this MESH version update was, its not good, please advise

cant scroll in mcrec player

Hi,

doesnt matter which browser i use, in mcrec player i cant scroll throu the recording...

is it a bug or a feature? ^^

Thx!

Erik

MeshCommander 0.8.4 - SOL terminal size not respected

SOL window is always extended with new lines, not scrolled up like on normal terminal. So after bit of work on SOL terminal you might have window 80x1000 :-(

Tested on NUC7i5DNHE DNKBLi5v.86A.0068.2020.0312.1721 IME v11.8.70.

npm IDER keeps disconnecting

First and foremost, great work, great peace of software, really really nice, don't know about business use but home lab it is a blessing!

There seems to be though a issue with the NPM version(have not checked yet the Windows version that I believe uses a different library for IDER), seems to be related or similar to #23 , just that I am checking on MACOS Catalina

Hardware: Lenovo P52 notebook
OS: MACOS Catalina 10.15.6
Node.js version: 12.13.0
MeshCommander version: 0.8.9-a
Intel ME version: 12.0.68
Running MeshCommander on the mac directly with node.js connecting to the P52 on LAN

When trying to attach a ISO with IDER, it gets attached for 10-30 seconds(from a UI perspective), but when trying to mount inside the machine it hangs and than the connection drops I believe(in the UI the "session bar" disappears)
Tried with holding the shift key before clicking the IDER button, but unfortunately it does not make a difference
Tried with the OS fully loaded (ubuntu 20.04) and rebooting the machine
Tried with a smaller ISO 500MB and a small ISO netboot 885k
Tried also to reattach multiple times, it does not make a different
Tried also the "drag and drop" method, does not work either

There does not seem to be a error log (or I could not find it), I would be happy to provide any additional info or do debug steps if needed

Please let me know if I can help with anything else

Thanks

No KVM feature availble

I'm trying to use KVM feature from a ECS Q470H6-M6 motherboard with i5-10500 CPU via MeshCommaner 0.9.0 with no success.

I can connect to the system and check Active Features, but there is no KVM listed.
If I try to connect to Desktop I get: "The device indicates that this type of connection is not supported"
Is it a clear sign that MB's firmware is missing this feature or I can somehow troubleshoot this further?

Thanks in advance!

Add support for remote screen blanking

Add support for remote screen blanking. This is useful when:

When remotely performing maintenance on a client system, it can sometimes be necessary to ensure that the maintenance is not visible to people in the vicinity of the system. This is particularly true for sensitive maintenance conducted on systems located in public, such as ATMs.

I'm willing to add support for this feature if you provide some guidance on how I should/could implement it :-)

MeshCommander - Missing "Optional Token Request" parameter in nw.exe

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

Agentless Setup - Devices imported via MeshCmd defaulting to IP instead of hostname

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:

From M1 Mac i can't connect over the Firmware Remote Desktop to Intel ME

Hi,
i'm using Meshcommander IME firmware extension unfortunately from a Mac M1 (Firefox, Chrome, Safari) i can't get Remote Desktop working. The screen stays black connection stops after a second. ( i set it to 8Bit)

With VNC Player on the Mac i can connect to the Remote Desktop without any issue on Port 5900.
From a Win10 PC it works using the Remote Desktop on the Firmware Extension but only if i connect minimum one time with a local on my Desktop installed Meshcommander

failed to boot PXE with SoL enabled

Hi,

I try to boot pxe with console redirected to sol but get:
(2) Change Boot Order returns INVALID_MESSAGE_LENGTH

It works on v8 with the soap interface which is no longer present in v14.
How to do this with meshcommander, meshctl or wsman?

To reproduce use a Custom Power Action with Serial-over-LAN enabled and Boot Source "Force PXE Boot"
I tried with meshcommander 0.9.0 and 0.9.2 and Intel ME v8.0.0 and v14.0.36

Script Block - Issued Untrusted Certificate is not working

When trying to issue an untrusted certificate through the Script Block the script doesn't work and is pausing on jsonparse wsargs line. Attached screenshot.
Version on Meshcommander v0.8.1

meshcmd source code

Hello,
do I understand correctly that meshcmd is a closed source tool?

Cannot connect to AMT using an IPv6 address

Hello,

I have tried to connect to Intel AMT via IPv6. When I add a computer in MeshCommander and type the IPv6 address into the Hostname field, then save the computer entry and attempt to connect, I only get a Connection timeout. I have tried the two following formats with the same result:

• 2001:db8:1:2:3:4:5:6
• [2001:db8:1:2:3:4:5:6]

When I create a DNS hostname with only the AAAA resource record pointing to the same IPv6 address, MeshCommander can connect to the node with no issues. (IOW the connectivity works fine, the app works fine when using hostname.)

I'm happy to collect more data if needed, however I'm currently not sure what/where to check. I have only checked in Wireshark that the application does not attempt to send any packets to the destination, therefore my assumption is that the application does not correctly recognise the hostname as a pure IPv6 address.

Broken KVM keyboard mapping

Using an fr-fr keyboard with MeshCommander v0.8.2, some keys are correctly mapped, some other keys are mapped as en-us, some other keys are mapped otherwise, and some keys are not mapped at all. I get the same behavior whether the AMT host is running the BIOS UI, Windows 10 Pro with an fr-fr keyboard or Ubuntu with an en-us mapping.

I don't know if this can help, but with MDTK, in order to get an acceptable keyboard mapping, I had to select "Japanese keyboard" in the connection options of UltraVNC and to switch my Windows keyboard mapping to en-us for the KVM window.

Here is the exact mapping that I get with MeshCommander v0.8.2:

• a-z → a-z (no issues)
• ² → '
• Shift+² → "
• &é"'(-è_çà → 1234567890 (as if en-us)
• 1234567890 → !@#$%^&*() (as if en-us)
• )°=+^¨$£ù%*µ,?;.:/ → [{=+]};:`~\|,<.>/?
• !§<> and AltGr combinations → not mapped at all
• numpad: no issues

AMT host: Lenovo ThinkServer TS140, BIOS version: FBKTD9AUS, Intel ME v9.1.45 activated in Admin Control Mode (ACM).
Client: Windows 10 Pro 1909, 64-bit, fully updated, RLE8.

MeshCommander was installed using the MSI installer.

Tell me if you need more information.

KVM no longer working with v0.8.3

With my setup, KVM ("Remote Desktop" section) works fine with v0.8.2, but not with v0.8.3. After clicking "Connect", the state switches to "Setup..." for a couple of seconds, then to "Disconnected".

AMT host: Lenovo ThinkServer TS140, BIOS version: FBKTD9AUS, Intel ME v9.1.45 activated in Admin Control Mode (ACM), no OS, machine reset to BIOS.
Client: Windows 10 Pro 1909, 64-bit, fully updated, RLE8.

How to convert a Remote Desktop Session .mcrec file to a standard video file?

How to convert a Remote Desktop Session .mcrec file to a standard video file?

Or even, why not save it in a standard video file from the get go? For example, in a .webm file.

Web application is unusable by users with very limited permissions

If a user with very limited permissions tries to use the web interface in Firefox, all of the HTTP 400 errors cause the username and password to be forgotten and Firefox prompts for them again. This happens repeatedly.

The web interface needs to only make access requests that the user has permission for. If it's not possible to determine what permissions the user has then each section should only request data when it is selected.

Invalid Username or Password

Today I have tried to better understand (and use) MeshCommander. I just uploaded my MC server to 0.7.68.

I followed the instructions in MeshCmd User's Guide. I edited my meshaction.txt to include my Password. When I run meshcmd, I get "Invalid username or password." I then removed the password from the txt file, and tried to pass the pass on command line, and get the same issue.

I note that the action file has:
wss://www.REDACTED.com:443/meshrelay.ashx

Does this mean I should be able to go to a and web browser and type www.REDACTED.com:443? When I do, I get a Connection Reset in my Firefox browser.

Any help in debugging would be most appreciated!

(I did set debug level 1, but it didn't identify any issue that I can tell)

Note that MeshCentral Router works just fine (and is amazing!)

• Thanks!,
• Robert

MeshCommander capability to reset BIOS or BIOS password?

I have set up BIOS\TPM\AMT on a Panasonic Toughbook FZ-55.

I paired AMT with MeshCommander successfully and can still access the toughbook via AMT. Windows works as well because the BIOS is not requiring password to boot. The problem lies with the fact that I can no longer get into the BIOS because the password is unknown. Is there a way to reset BIOS password from MeshCommander\AMT?

I used a barcode scanner to enter and verify the BIOS password. The password creation entry fields must be treated differently than the entry fields requested upon entering the BIOS because it isnt letting me into the BIOS by scanning or hand entering the password. Panasonic does not provide a way to reset the BIOS, they charge $300 to send it in for a reset! Any ideas?

Feature Request: a workaround for "stuck at 10Mbps" issue

When I shutdown my Dell T7910 and do "Remote Command -> Remote Reboot to BIOS Setup" (to change the boot order and boot to another OS), my LAN adapter (built-in I217-LM Gigabit Ethernet) gets stuck at 10 Mbps connection speed. This seem to be a somewhat known issue, except that I'm using Serial-Over-Lan, not KVM... But I guess it works the same way.

They say "It is recommended to start the KVM session in S0". Thus, it would be nice if MeshCommander would automatically follow this advice, e.g. power on first and then (re)connect to SOL and go to BIOS somehow.

Regarding to MeshCommander UI

Hello Ylianst,
Sorry about to bother you.
We are Atrust Computer from Taiwan, and now developing a project that using MeshCommander open source to reproduce a remote device system management.
If possible, I would like to know your comments for the UI design to move MeshCommander to top right side of page as below screen capture.
Thank you.

MeshCommander Windows Program not showing Remote Desktop as an Option

Hey,

Started to try out your MeshCommander program and so far it looks great.
However, I have noticed on the left hand side, I don't have a remote desktop option. Perhaps a setting wasn't enabled in the initial set up. Perhaps you could advise on how to rectify this?

If you need them:
Running MeshCommander 0.8.8
End-User Machine is Intel ME v11.21.51

Lemme know if you need any other info to help out with this.

Thanks in advance.
Ceejay

IDE-R/IDER/USB-R/USBR unreliable linux always showing reset high-speed usb device

While running meshcommand 0.9.0-d (connected to a intel amt 11.8.82) and using iso storage redirection, linux is periodically showing the message reset high-speed usb device as you can see at:

Why is this happening?

How can I troubleshoot this?

Also, this does not work when trying to boot the machine from this redirected iso :-(

Remote desktop connection problem

My client machine is successfully connected with Meshcommander v.0.9.0 to a host PC with AMT. But:

1. in remote desktop view I can see only a picture from primary display. Switching to secondary display leads nowhere. The picture is shown from primary.
2. Keyboard and mouse don`t work. There is also disconnected status on the host PC.
   
   
   
   

MeshCommander for IIS is missing Kerberos support to Intel AMT machines

Hi @Ylianst

Have installed MeshCommander for IIS today, and noticed that I don't have the option to add machines to use "Kerberos / TLS".
I only have the option for "Digest / Digest TLS".

Is this something you will add in the next release?

Cheers
Best Regards
Horgster

MeshCommander can't enable IPv6, but it can enable from Intel AMT web console.

MeshCommander can't enable IPv6, but it can enable from Intel AMT web console.