Port - What server OS to use
-
Oh, makes sense.
-
I think that ScreenConnect will do some of this, too. But that's not my department, so I might be imagining that.
-
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
-
@scottalanmiller said in Port - What server OS to use:
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds. I can use it to map drives for users because it runs as the system account, not as the user account that's logged in.
-
@scottalanmiller said in Port - What server OS to use:
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
I think the value of Screen connect would be to save you walking around the office as you connected to each machine and did it manually.
-
@mike-davis said in Port - What server OS to use:
@scottalanmiller said in Port - What server OS to use:
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
I think the value of Screen connect would be to save you walking around the office as you connected to each machine and did it manually.
Or even going into the office at all! But it's also that it would be fast. If you copy/pasted the command and already had the SC sessions in a group, which would be expected, it would be a matter of click... paste... run; click... paste... run...
Not perfect, but fast and easy.
-
@mike-davis said in Port - What server OS to use:
@scottalanmiller said in Port - What server OS to use:
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds. I can use it to map drives for users because it runs as the system account, not as the user account that's logged in.
Not sure. Mapping drives and adding printers seem reasonable. Installing MSIs, not so much.
-
@scottalanmiller said in Port - What server OS to use:
@mike-davis said in Port - What server OS to use:
@scottalanmiller said in Port - What server OS to use:
So, in theory, with ScreenConnect and its remote command execution options, it looks like a printer add command could be issued there to each of a series of clients and add printers without even needing to log into each one. Still not ideal, but not too bad.
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds. I can use it to map drives for users because it runs as the system account, not as the user account that's logged in.
Not sure. Mapping drives and adding printers seem reasonable. Installing MSIs, not so much.
Deploying MSI is pretty easy using PDQ Deploy.
-
This is one of the tasks that we hope that SodiumSuite will be addressing in the future, as well. It does not today, but we are watching these kinds of discussions with interest, because we see SS as a problem solver here.
-
I'd be comfortable doing a whole 15-20 fleet of Fedora 26 Cinnamon desktop and manage them with Salt. Local users. Share out a SMB2.1 share. Not sure about SMB3.x on Linux yet.
-
@tim_g said in Port - What server OS to use:
I'd be comfortable doing a whole 15-20 fleet of Fedora 26 Cinnamon desktop and manage them with Salt. Local users. Share out a SMB2.1 share. Not sure about SMB3.x on Linux yet.
Linux, sure. Hundreds of desktops with Salt no problem. Without Windows in the mix, scale and management is no problem.
-
@mike-davis said in Port - What server OS to use:
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds.
It is possible to run command that take a long time to finish. See example below. The first 2nd & 3rd line line is what you need. firs line is to say its powershell.
--------- paste below into ScreenConnect cmd windows ---
#!ps
#maxlength=50000
#timeout=300000
ping 127.0.0.1
etcYou can use this to launch batch files from network share etc.
BTW my first post ever on here
-
@360col said in Port - What server OS to use:
@mike-davis said in Port - What server OS to use:
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds.
It is possible to run command that take a long time to finish. See example below. The first 2nd & 3rd line line is what you need. firs line is to say its powershell.
--------- paste below into ScreenConnect cmd windows ---
#!ps
#maxlength=50000
#timeout=300000
ping 127.0.0.1
etcYou can use this to launch batch files from network share etc.
BTW my first post ever on here
Welcome to Mango! Thank you so much for the tip. I tried that and it worked.
-
@360col said in Port - What server OS to use:
@mike-davis said in Port - What server OS to use:
I'm not sure how effective Screen Connect would be. With my install commands that don't run within a few seconds time out. So I can't launch a .msi install unless it finishes in 2 seconds.
It is possible to run command that take a long time to finish. See example below. The first 2nd & 3rd line line is what you need. firs line is to say its powershell.
--------- paste below into ScreenConnect cmd windows ---
#!ps
#maxlength=50000
#timeout=300000
ping 127.0.0.1
etcYou can use this to launch batch files from network share etc.
BTW my first post ever on here
You win the internet today!
-
Hey @360col
Do us a favor and make a thread thread labeled ScreenConnect tips put some tags on it, and start with this tip. I want to see you get credit for providing this instead of me just posting on your behalf.
-
@mike-davis said in Port - What server OS to use:
@scottalanmiller said in Port - What server OS to use:
@mike-davis said in Port - What server OS to use:
I'm also having a hard time figuring out how powershell would work when you would have to feed each computer different credentials.
Why different credentials? I mean you sure could have different ones and that might make sense, but you can use a common account, too. Remember that with AD we are okay with shared creds, so we probably are here, too.
Isn't the username without AD computername\username ? So you would have to change the computername for each one even if you set the password the same.
you can use
.\usernamealways have been able to do this. -
@jaredbusch that's what I use all the time.
We have all machines set with a standard Admin user so if we need to work on it off the network or it's having AD issues to can.
Also saves time on finding what the machine is called -
Before you can get in to what OS to run the clients on, do you have to ask what apps the business needs to run? If they need some kind of CAD package and it's only offered on Windows, the linux client goes out the window. (pun intended)
