Comparing MeshCentral 2 to ScreenConnect
-
Does MeshCentral have a way to uninstall the remote agent from within the console like ScreenConnect does?
-
@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.
-
@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.
-
If I first remove the remote device agent, then I can successfully delete the server from the MC dashboard.
The test was on a remote server running Windows Server 2012R2.
-
@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.
That's odd. I've done this a bit and not seen that happen. But maybe the agent was no longer running?
-
@scottalanmiller 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.
That's odd. I've done this a bit and not seen that happen. But maybe the agent was no longer running?
Most likely. I can remove an agent and it pops back immediately, as @NashBrydges noted.
I want to remote uninstall the agent.
-
No obvious command to remove it in the agent command list...
help
Available commands:
amt, amtacm, amtccm, amtdeactivate, amtpolicy, amtreset, apf, args, av, cpuinfo, dbcompact, dbget, dbkeys,
dbset, eval, getclip, getscript, help, httpget, info, kill, location, lock, log, ls, netinfo, notify,
nwslist, openurl, osinfo, parseuri, plugin, power, print, ps, rawsmbios, scanamt, scanwifi, sendcaps,
setclip, setdebug, smbios, sysinfo, toast, type, users, wakeonlan, wsclose, wsconnect, wssend. -
Is there a way to make Powershell the default shell for Windows instead of Command Prompt?
-
@coliver said in Comparing MeshCentral 2 to ScreenConnect:
Is there a way to make Powershell the default shell for Windows instead of Command Prompt?
For Windows, yes...
-
For MeshCentral, no I don't think so. That would be nice, though.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
For MeshCentral, no I don't think so. That would be nice, though.
Yeah that's what I meant.
-
@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...
-
@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\Mesh Agent' $_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.
Edit: Fixed path for
C:\Program Files\MeshAgenttoC:\Program Files\Mesh Agent
Thanks @JaredBusch -
THis is what ConnectWise shows when you choose uninstall.
-
Bomgar does this and uninstalls automatically as soon as your end a session if it is on demmand or from the host.
-
@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.
-
@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.
