Alternatives to LMI
-
@aaronstuder said in Alternatives to LMI:
@Jason @JaredBusch and I did a session just a few weeks ago and I didn't install anything.
So you and @JaredBusch are on the same network? That's the only way that would work
-
@Jason said in Alternatives to LMI:
@aaronstuder said in Alternatives to LMI:
@Jason @JaredBusch and I did a session just a few weeks ago and I didn't install anything.
So you and @JaredBusch are on the same network? That's the only way that would work
No...
-
@aaronstuder said in Alternatives to LMI:
@Jason said in Alternatives to LMI:
@aaronstuder said in Alternatives to LMI:
@Jason @JaredBusch and I did a session just a few weeks ago and I didn't install anything.
So you and @JaredBusch are on the same network? That's the only way that would work
No...
Then you either have something installed or ran the agent
-
@Jason check this gif from screenconnect, the end user machine doesn't have an agent, just enter the code, same way done on LMI, and it connects to the session. Once the session is completed, the screenconnect session gets cleared up
-
@Ambarishrh said in Alternatives to LMI:
@Jason check this gif from screenconnect, the end user machine doesn't have an agent, just enter the code, same way done on LMI, and it connects to the session. Once the session is completed, the screenconnect session gets cleared up
Guys, this is not at all what we we talking about. @JaredBusch you understand what we mean right?
-
I understand what you mean - and you could do this with Screen connect, but not as cleanly as the SC agent is suppose to be install and left there. Apparently LMI has created an agent that just runs, and then deletes itself after it is shutdown.
The LMI solution most likely works by sending a file to the remote computer through the administrative share on the remote computer, or puts an execute command into the remote machine's registry, which then executes and sucks the exe in from someplace on the network and starts it.
But I gotta ask, if you are on a local network, why not deploy an agent?
-
@Jason said in Alternatives to LMI:
@Ambarishrh said in Alternatives to LMI:
@Jason check this gif from screenconnect, the end user machine doesn't have an agent, just enter the code, same way done on LMI, and it connects to the session. Once the session is completed, the screenconnect session gets cleared up
Guys, this is not at all what we we talking about. @JaredBusch you understand what we mean right?
I understand perfectly what you are talking about. You are 100% correct. It is most certainly a nice feature and not one that ScreenConnect has by default. I can think of a way to sort of emulate this LMI feature, but it would need testing.
-
@Dashrender said in Alternatives to LMI:
I understand what you mean - and you could do this with Screen connect, but not as cleanly as the SC agent is suppose to be install and left there. Apparently LMI has created an agent that just runs, and then deletes itself after it is shutdown.
ScreenConnect "Support" sessions work like this, but require user interaction. Which breaks one of his other criteria.
-
@JaredBusch Right, but if the user isn't on the computer, why can you just push the agent to the computer with something like PDQ Deploy? That's basically with LMI is doing, more a less.
-
@aaronstuder said in Alternatives to LMI:
@JaredBusch Right, but if the user isn't on the computer, why can you just push the agent to the computer with something like PDQ Deploy? That's basically with LMI is doing, more a less.
There is no one time agent to push that the administrator has easy access to. When the user is sent a link to the session, it downloads and the user has to run it.
I am sure I could work around that. But it is not in the design. It would be a hack. LMI has it in the design.
