Managing Windows Local Users with Net User
-
@JasGot said in Managing Windows Local Users with Net User:
Oh, man...... How true! I don't think I could get through my days anymore without net user and net accounts from a remote shell. They are the first things I do when someone says anything at all about "login issues".
Yeah, I use these constantly. We use them through remote command execution so the PowerShell stuff doesn't work, so net commands are our friends.
-
@scottalanmiller said in Managing Windows Local Users with Net User:
@JasGot said in Managing Windows Local Users with Net User:
Oh, man...... How true! I don't think I could get through my days anymore without net user and net accounts from a remote shell. They are the first things I do when someone says anything at all about "login issues".
Yeah, I use these constantly. We use them through remote command execution so the PowerShell stuff doesn't work, so net commands are our friends.
You certainly can, if you setup the command line right and don't rely on independent connections.
We run multiline powershell commands through ScreenConnect sessions all the time to add and remove printers. You just have to paste it all into the windows at once, then hit send.
-
@JaredBusch said in Managing Windows Local Users with Net User:
You certainly can, if you setup the command line right and don't rely on independent connections.
We run multiline powershell commands through ScreenConnect sessions all the time to add and remove printers. You just have to paste it all into the windows at once, then hit send.
That's what we do too. If you can do it one line at a time, you can do it through ScreenConnect command. Just need to bump the #maxlength=100000 and
#timeout=90000 as appropriate! (values will differ)I have to say though, I'm using backstage more and more for the things I used to do in a command.
-
@JasGot said in Managing Windows Local Users with Net User:
@JaredBusch said in Managing Windows Local Users with Net User:
You certainly can, if you setup the command line right and don't rely on independent connections.
We run multiline powershell commands through ScreenConnect sessions all the time to add and remove printers. You just have to paste it all into the windows at once, then hit send.
That's what we do too. If you can do it one line at a time, you can do it through ScreenConnect command. Just need to bump the #maxlength=100000 and
#timeout=90000 as appropriate! (values will differ)I have to say though, I'm using backstage more and more for the things I used to do in a command.
I have not looked at that. I know that they added it. But I haven't tried it yet.
-
@JasGot said in Managing Windows Local Users with Net User:
I have to say though, I'm using backstage more and more for the things I used to do in a command.
MeshCentral does well, too.
-
@JasGot said in Managing Windows Local Users with Net User:
I'm using backstage more
I assume that this is a component of another product?
-
@JaredBusch said in Managing Windows Local Users with Net User:
I have not looked at that. I know that they added it. But I haven't tried it yet.
It was love at first use!
-
@scottalanmiller said in Managing Windows Local Users with Net User:
@JasGot said in Managing Windows Local Users with Net User:
I'm using backstage more
I assume that this is a component of another product?
Part of ConnectWiseControl. (or ScreenConnect as we still call it around here.)
It's at the bottom of the View tab when attached to a guest. Takes you to a new sessions as a System account with a command prompt and powershell window already open. No limit to what you can accomplish there. many gui apps will run in backstage too.
