Ylian Saint-Hilaire

FYI. I just checked my outbound email folder and saw that an email with you GitHub handle was sent at 9:25am PST. So, it does look like it's working on...

Can you provide some numbers on the leak? Indeed, there was a specific plug-in that would store lots of data in the MeshAgent database and cause issues. However, except for...

There should be one instance running, but when you open a agent KVM session, a second instance will show up. The first instance is managed by the Windows service manager....

Good request. Bryan needs to add support for this in the MeshAgent.

Agreed that there is no standard way to get license information. Bryan has been looking today at getting installed software list on Windows and he made progress on that. Once...

Yes, that is coming. I think Bryan added this to the agent for Windows.

Sure, I just made improvements to this feature. In v1.0.54 try this: ``` "altmessenging": [ { "name": "Meet", "url": "https://FQDN:5001/meet/{2}", "type": "user" } ] ``` There is a new "type"...

Oh, got it. I will put in another fix. If you don't put in the type, the chat button will also show up in the "My Users" tab here: 

Ok, once MeshCentral v1.0.54 is out, try exactly this: ``` "altmessenging": [ { "name": "3CX Meeting", "url": "https://FQDN:5001/meet/{6}", "type": "device" } ] ``` It should do exactly what you want.

This is an issue for Bryan.