Comparing MeshCentral 2 to ScreenConnect
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
OK, makes since. I get the login prompt, just cant pass the ctrl-alt-del, which is why i asked. I am only messing with it in lab environment.
In a command line environment, is there any purpose for CTRL-ALT-DEL? It doesn't do anything in a CLI environment, it is part of the GUI system.
Um, CAD absolutely does something. Because that is how Windows Core (and thus Hyper-V Server) requires you to access the system.. Always has.
Not in the terminal. Try using MeshCentral (or ScreenConnect.) There is no purpose for it and nowhere for it to go. It never asks for it and is never used. It is exclusive to the GUI screen.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
OK, makes since. I get the login prompt, just cant pass the ctrl-alt-del, which is why i asked. I am only messing with it in lab environment.
In a command line environment, is there any purpose for CTRL-ALT-DEL? It doesn't do anything in a CLI environment, it is part of the GUI system.
Um, CAD absolutely does something. Because that is how Windows Core (and thus Hyper-V Server) requires you to access the system.. Always has.
Not in the terminal. Try using MeshCentral (or ScreenConnect.) There is no purpose for it and nowhere for it to go. It never asks for it and is never used. It is exclusive to the GUI screen.
Except it is not a terminal environment. It is MC/SC remote console, and the Windows console requires CAD.
-
SAM, if you look at my screen shot, that is from Desktop mode, and its asking for CAD. You would have to do CAD to go in (which is how I installed MC not sure if there was a way to do it in terminal, probably is, but did not want to figure it out). I haven't messed with it (Svr Core) nor power shell enough to know any more. I just was pointing out what I notices, that's all. I know I could use Win Admin Tools (Honolulu) to do stuff, which is cool so far.
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
I have a bug report open on their github for this problem. It also applies to 2016.
https://github.com/Ylianst/MeshCentral/issues/123Cool, at least I know I wasn't imaging stuff (or not doing something right)
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
SAM, if you look at my screen shot, that is from Desktop mode, and its asking for CAD.
I understand that. And my point was that you were using the wrong tool.
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
You would have to do CAD to go in (which is how I installed MC not sure if there was a way to do it in terminal, probably is, but did not want to figure it out).
You only need it because you are on the wrong tab. Switch to the terminal, rather than the desktop.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
You only need it because you are on the wrong tab. Switch to the terminal, rather than the desktop.
I am not command line nor linux person. So I don't want to have to look up every command, so having the sconfig screen helps.
There are certain things (in sconfig) that you need to be on the console (or use win admin tools). That will not work in Terminal (you prob can do it with commands, but I don't want to). I also do not like how terminal looks, there is no scrolling, and the font is kind of big. When I do an IP Config, I can't see part of whats there since it rolls off the page. I prefer the classic cmd look. Again, just my opinion. I'm not asking or saying how it looks should be changed.
Also, when I installed MC, I had to click install, so I needed the console (which brought up the MC gui install box). Now I know there is probably a better way to do it, I just didn't want to have to look it up. There is partial gui still in core from what I see, not a lot, but there is some. For a beginner in command line stuff, it helps fill the gaps and makes learning it a little easier
Reading the github that @JaredBusch linked , SC has no issues with it. I personally really don't care if it gets fixed as I was just seeing how core looked/worked with Windows Admin Center.
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
I am not command line nor linux person. So I don't want to have to look up every command, so having the sconfig screen helps.
Linux has absolutely no connection here. Nothing on the Windows command line has any association with anything on Linux, and Linux is no more or less "command line" than Windows is. This is a 100% Windows thing.
sconfig is a good point, have you tried that in the terminal? I'm assuming it is a no go?
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
Also, when I installed MC, I had to click install, so I needed the console (which brought up the MC gui install box).
Use the background, rather than the interactive, installer. MC has both a GUI required, and a non-GUI required installer for exactly that reason.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Linux has absolutely no connection here. Nothing on the Windows command line has any association with anything on Linux, and Linux is no more or less "command line" than Windows is. This is a 100% Windows thing.
sconfig is a good point, have you tried that in the terminal? I'm assuming it is a no go?I know, I was just saying I don't do command line whether it be linux or windows much, except for basic commands i've used all my life (I know your heavy in linux, which is why I mentioned linux. I know you love the command line
haha ).and I can run sconfig. but cant do anything with it.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Use the background, rather than the interactive, installer. MC has both a GUI required, and a non-GUI required installer for exactly that reason.
I'll give that a try later on my next test install
-
Getting TUIs working in the terminal would be amazing. That would solve the problem SO much better.
-
Just updated to 0.3.2-p
-
@scottalanmiller Apologies, what are TUIs?
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller Apologies, what are TUIs?
TUI... Textual User Interface.
A great example is sconfig on PowerShell. It's an app that gives GUI-like experience, but built out of ASCII characters.
vi or pine or joe are all TUIs on Linux.
-
I just released a JavaScript IDER server and added it to MeshCommander v0.7.5 and MeshCentral v0.3.2-p. Blog about this here. This is going to be really amazing for Intel AMT users. Now that this is done, I can go back to bug fixing.
-
@scottalanmiller Agreed. Thanks.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller Apologies, what are TUIs?
TUI... Textual User Interface.
A great example is sconfig on PowerShell. It's an app that gives GUI-like experience, but built out of ASCII characters.
vi or pine or joe are all TUIs on Linux.
But doens't sconfig launch into a new window process?
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller Apologies, what are TUIs?
TUI... Textual User Interface.
A great example is sconfig on PowerShell. It's an app that gives GUI-like experience, but built out of ASCII characters.
vi or pine or joe are all TUIs on Linux.
But doens't sconfig launch into a new window process?
It does not in the GUI when I use it, and if I launch it through MeshCentral terminal it launches, but does not display correctly. Seems to be in the same process.
-
@scottalanmiller On Windows terminal currently launches within the MeshAgent process and causes a bunch of issues. Bryan who works on the agent will be looking into spawning a separate process for the terminal shell / powershell that should help. One huge bug with the current model is that "ping -t 1.2.3.4" can't be halted and will keep running even after the agent is stopped. To summarize, the Windows terminal needs more work.
