Comparing MeshCentral 2 to ScreenConnect
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@dbeato said in Comparing MeshCentral 2 to ScreenConnect:
Bomgar does this and uninstalls automatically as soon as your end a session if it is on demmand or from the host.
No one is talking about on-demand. On demand should not install anything in the first place. merely run.
Exactly. MeshCentral does the same. Run on demand and it just "vanishes" when you close.
-
Up to 0.4.2-h
-
Just updated to 0.4.2-i. As always, quick and painless!
I really need to get in the habit of checking every day...
-
@srsmith said in Comparing MeshCentral 2 to ScreenConnect:
Just updated to 0.4.2-i. As always, quick and painless!
I really need to get in the habit of checking every day...
If you want, you can enable SelfUpdate in your config.json file to auto update.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@MordyT said in Comparing MeshCentral 2 to ScreenConnect:
@NashBrydges said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@JaredBusch it has "delete device". I don't know if it removes the remote agent. But it makes the remote agent useless at least. I've never tested to see what the remote agent does when that option is selected. But it definitely removes it from MC itself.
Interesting behaviour I just observed when I tested this. I can click on the "Delete device" option and it does momentarily remove it from my MC installation however the remote device immediately returns to the MC My Devices dashboard. It looks like there may be a bug that prevents it from being removed if the remote agent is still running on the remote device.
Download the uninstaller, transfer with meshcentral to the pc, run with meshcentral remote commands, delete device from portal?
Would be nice for a button, but in theroy that could work...
Heck, could likely make it all a powersehll script with invoke-webrequest, so you can in 1 script download, run uninstaller, delete installer (maybe). Then it's a matter of deleting from portal...
No need to download the installer.
Create a script with something like this.$_oFile = 'MeshAgent.exe' $_oMeshAgentPath = 'C:\Program Files\MeshAgent' $_oMeshAgentArguments = @( '-fulluninstall' ) Start-Process -FilePath "$_oMeshAgentPath\$_oFile" -ArgumentList $_oMeshAgentArguments -Wait -NoNewWindowBut having a option to delete device and to uninstall meshagent and then delete device would be awesome.
This almost worked... The correct path also has a space in the folder
Mesh Agent. F'ing windows-esque devs.... -
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@MordyT said in Comparing MeshCentral 2 to ScreenConnect:
@NashBrydges said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@JaredBusch it has "delete device". I don't know if it removes the remote agent. But it makes the remote agent useless at least. I've never tested to see what the remote agent does when that option is selected. But it definitely removes it from MC itself.
Interesting behaviour I just observed when I tested this. I can click on the "Delete device" option and it does momentarily remove it from my MC installation however the remote device immediately returns to the MC My Devices dashboard. It looks like there may be a bug that prevents it from being removed if the remote agent is still running on the remote device.
Download the uninstaller, transfer with meshcentral to the pc, run with meshcentral remote commands, delete device from portal?
Would be nice for a button, but in theroy that could work...
Heck, could likely make it all a powersehll script with invoke-webrequest, so you can in 1 script download, run uninstaller, delete installer (maybe). Then it's a matter of deleting from portal...
No need to download the installer.
Create a script with something like this.$_oFile = 'MeshAgent.exe' $_oMeshAgentPath = 'C:\Program Files\MeshAgent' $_oMeshAgentArguments = @( '-fulluninstall' ) Start-Process -FilePath "$_oMeshAgentPath\$_oFile" -ArgumentList $_oMeshAgentArguments -Wait -NoNewWindowBut having a option to delete device and to uninstall meshagent and then delete device would be awesome.
This almost worked... The correct path also has a space in the folder
Mesh Agent. F'ing windows-esque devs....Good catch. It's fixed now.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@dbeato said in Comparing MeshCentral 2 to ScreenConnect:
Bomgar does this and uninstalls automatically as soon as your end a session if it is on demmand or from the host.
No one is talking about on-demand. On demand should not install anything in the first place. merely run.
Exactly. MeshCentral does the same. Run on demand and it just "vanishes" when you close.
Understood. Bomgar doesn't install a client on demand so it was my bad wording.
-
0.4.2-k a couple hours ago and -p now!!
-
0.4.2-u now
-
0.4.2-v now.
And we've upgraded to Ubuntu 19.10 as well.
-
0.4.2-z is out there now.
-
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
0.4.2-z is out there now.
Just updated. Had some stability issues with 0.4.2-w
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
0.4.2-v now.
And we've upgraded to Ubuntu 19.10 as well.
Did you have any issues with MC after the 19.10 upgrade?
-
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
0.4.2-v now.
And we've upgraded to Ubuntu 19.10 as well.
Did you have any issues with MC after the 19.10 upgrade?
Yeah, we are having some stability issues. BUT we just finished some updates so I'm not ready to report them unless they continue after NodeJS was updated. So far stable on NodeJS 13.0.x.
-
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
0.4.2-v now.
And we've upgraded to Ubuntu 19.10 as well.
Did you have any issues with MC after the 19.10 upgrade?
Since updating NodeJS, no issues.
-
0.4.3-a now
-
And now 0.4.3-b
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
And now 0.4.3-b
Uh oh. Updated to this and now there is no login option!
-
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Looks like he posted a fix overnight
