MeshCentral Blog

This week, many more improvements and features where added to MeshCentral, most notably a big improvement on an important feature: the remote desktop recording system. In order to conform to auditing policies, some administrators must be able to record remote desktop sessions that are carried out by technicians. Because of the protocol, it was not possible to skip to any location in the file until today. This and many other improvements this week in detail: Recorded Remote Desktop Indexing . Many months ago, MeshCentral was released with support for session recording. It works by recording the network traffic and adding timestamps and direction flags when writing the stream to a file. Because remote desktop only sends portions on the screen that change, it was not possible to skip forward into a remote desktop session using the MeshCentral Player. This week, we fixed this with a new indexing feature. MeshCentral can now create an index each 10 seconds of the location in the file and

It’s been a while since the last blog post and MeshCentral continues to evolve with multiple new releases on most business days. In this post, we got a bunch more new features including some more crazy ones. Probably the most important is the ability for the MeshAgent to be installed within a Docker container. Using this new feature, you can now manage your Docker container just like any other device remotely using MeshCentral. The Linux install script will automatically detect it’s being installed within Docker and adjust accordingly. Many more new features in detail: MeshAgent within a Docker container . This is probably one of the more crazy features that has been published in a while. Normally on Linux, the MeshAgent will install itself so it can auto-start using Systemd or Initd, but these services don’t exist within a Docker container and so, the latest version of the Linux install script will auto-detect this situation and install the agent correctly within Docker. As a result