Closed catalinchertes closed 2 months ago
@inzi sadly not yet, But in the meshagent repo under one of the folders the is like a readme file which explains abit about its design
Wanted to let you know, everything seems to be OK except when adding a new agent now.
I'm getting the dreaded The Mesh Agent service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
I'm on v1.0.27, hosted on Server 2019 64bit - and the client I tried adding to is a re-install on an intel nuc with windows 10 Pro (64bit).
I deleted the old instances, etc. I've set the NoInteractiveServices to 0 and rebooted.
I tried remove the agent proxy and restarting service on my server.
I've disabled the local firewall.
I'm pretty much at a loss. I had this happen on another machine and it suddenly started working.
I see the agent connect and try and pull down the core agent and it just disappears.
Show's agent connected, but console doesn't work (typing help + enter and it does nothing). Getting no info.
I get this error when it tries to start the service.
@inzi plz open up a different issue about ur interactive issue, keep things separate
But glad to see the file issue is fixed!
When we upload a 19MB file to multiple devices using the batch feature. The folder is created and the file is uploaded, but when we check the size, it changes to 1KB, so something is happening with the file after upload since the original size is 19MB.
When we do it from the single device file upload option, it works fine and the file keeps it's original size.
We could really use this feature as we have over 700 remote desktops with mesh agents. This tool is so amazing and we are very thankful for it, thanks for your hard work.
This is the server log upon upload: (I removed the host name for privacy).