Posts

Showing posts from November, 2018

MeshCommander 0.7.3 with CILA support

Image
MeshCommander is an open source web-based Intel® AMT management console. It’s a leading edge tool and today, MeshCommander added support for Client Initiated Local Access (CILA) . It's important to be able to remotely manage computers both in software and hardware regardless of where they are connected. Client Initiated Remote Access (CIRA) has been around since Intel® AMT 4.x and provides the way hardware management can connect back to a cloud server. Starting with Intel® AMT 11.6, CIRA is joined by CILA, the local version of the same tunneling system. With CILA, you can now configure Intel® AMT to connect back to a home management server both over the Internet and over the local network . Using a tunneling protocol on the local network means that Intel® AMT is always accurately discovered by the management server. This makes it easy for a server like MeshCentral2 to keep track of all of the Intel® AMT capable devices on a local network. In addition, local management ports (

MeshCentral now with reverse-proxy support

Image
MeshCentral is an open source web based remote management server. This last week, MeshCentral was improved again with support for reverse-proxies that allow for improved scalability and flexibility when deploying MeshCentral as a web service. Any serious network administrator will know about reverse-proxies, notably NGINX but many others exists. There are many benefits including more flexibility in how a web server is configured, allows many web applications can run together on the same server, TLS offloading and load balancing. As more people deploy MeshCentral2, it’s became a more frequent request to add proper support for reverse proxies, notably NGINX. This week, a new version of MeshCentral was released on NPM along with a new MeshCentral User’s Guide 0.1.8 and a YouTube video with a tutorial on how to support NGINX . MeshCentral has an interesting design where the Mesh Agents connect to the server using web sockets on the same port that users connect on with browsers. This