MeshCentral Blog

This week, the manageability reach of MeshCentral is extending even more to devices that don’t run a MeshAgent and located on private networks. MeshCentral v1.0.11 was published with support for MeshAgent relays for various device groups. This new feature allows a user to manage devices on a local network that don’t have an agent installed by creating the device on MeshCentral and relaying the connection thru a MeshAgent that is on that local network. The same can also be done for Raritan and Web Power Switch devices. In detail: Local Device Group with Relay . MeshCentral supports the local device group allowing devices that do not have an agent to be managed thru MeshCentral with regular SSH, SFTP, RDP, VNC protocols. Until now, the MeshCentral server had to be in LAN or Hybrid modes to support his device group and the managed devices had to be on the same network as the MeshCentral server. Starting with v1.0.11, users can create a local device group specifying a MeshAgent as a relay.

MeshCentral is taking another big step today in adding capabilities for large organizations with advanced support for configuring Intel AMT® with 802.1x network access. Large organizations use the 802.1x protocol to secure their wireless access points and wired ports. This is normally handled by the operating system, however since Intel AMT is its own computer within a computer with its own network stack, it needs its own credentials to access enterprise networks. Today, MeshCentral Satellite is being released that allows MeshCentral to perform Intel AMT 802.1x configuration in Windows domain controller environments while continuing to allow MeshCentral to be hosted in the cloud. In detail: MeshCentral Satellite . This is a new Windows tool that can run as a stand-alone application or as a background Windows service. It must run with sufficient permissions to create and remove domain computers and request that the domain certificate authority sign and revoke certificates. This tool wil