Comparing MeshCentral 2 to ScreenConnect
-
@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller gotcha, I don't think a roadmap has been posted has there?
I don't believe so.
-
Thanks for reporting it, yes 0.3.2-b had a problem where some agents would disconnect in just the right way and cause a server fault. Should be fixed. Got a lot of small fixes done today.
As for a roadmap, I don't really want one as I don't want to be committing to stuff in advance. However:
- Support for improved Intel AMT activation and usage is going to be coming.
- We are working on a way for a second agent to be on a timer that would call back to the server every few days and perform agent recovery if something goes wrong. This way, it serves as a back-stop if something goes wrong with the agent.
- User notification and/or user consent when taking control of a computer. I really need to get on that.
- Lots of things people are asking for on GitHub...
It's really never ending. It's possible companies could take the open source version and provide a professional version and/or deployments. That would be great and I certainly want to encourage this.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
User notification and/or user consent when taking control of a computer. I really need to get on that.
That would be HUGE!
-
@scottalanmiller Yes... yes...
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
User notification and/or user consent when taking control of a computer. I really need to get on that.
That would be HUGE!
I tried but I can only upvote this once.
-
Ability to blank the background of things we remote into so we don't stream the image, that would be nifty.
-
But my biggest desire is... "send keystrokes!!" So huge.
-
0.3.2-i in a late evening update!
-
Late night update to 0.3.2-k
-
Just published MeshCentral v0.3.2-l with early support for user notification when a remote session is connected. I expect to keep adding to this going forward, but wanted to release a starter version that just displays a toast notification when a remote session is connected. You can go in the device group page and edit this. You can also add "UserConsentFlags" in config.json domain section to force all device groups domain wide:
"__UserConsentFlags__" : "Set to: 1 for desktop, 2 for terminal, 3 for files, 7 for all", "UserConsentFlags" : 7Feedback appreciated,
Ylian
-
@Ylian awesome!!
-
@Ylian went to update and v0.3.2-m was current!
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian went to update and v0.3.2-m was current!
Yup, we are on that for a bit now (several hours.)
-
Anyone having issues with time online? My agent is online and working but the machine uptime is not displaying correct?
-
Ha yes, I have to do some more work on the timeline. However, normally I would see "Connectivity: MeshAgent" if the agent was online (just below "Active User"). Since it's not present, I imagine the agent is not currently connected?
-
@Ylian
Agent is working and connected, can access desktop and files on machine. Perhaps Its just my machine. I'll try reinstalling agent at some point to see if it changes anything. -
Is there any support for OSX from MeshCentral 2? or if you know a link on how to?
-
When using the Desktop function, hitting spacebar activates the All displays, Display 1, Display 2 drop-down menu. Can this be disabled?
-
0.3.2-o has released.
-
@Osvaldo said in Comparing MeshCentral 2 to ScreenConnect:
Is there any support for OSX from MeshCentral 2? or if you know a link on how to?
In case @Ylian didn't see this. He's asking if there are steps needed, as using the agent failed for him.
