Question Permanent Remote access to multiple win11 computers?

Toggle sidebar Toggle sidebar
wckdg32516

wckdg32516

Mar 9, 2024
10
0
10
Hello, I have few computers... let's say 50. I'd need to be able to access any of them (remote access, desktop, run software etc) on all of them from my main computer. What are my options? Are there any free options? or only paid? etc. I'd want to be able to access all of them like when you have multiple VM's running in Vmware etc. Just switching between them, connecting whenever i need and disconnecting whenever too.
 
Sort by date Sort by votes
USAFRet said:
"50" is more than a few.

What is the Win 11 version?

How are these all connected?

What is the need for this? (knowing why may lead to how)
Click to expand...
They aren't connected, they are separate computers, just on same internet. I'll just use them for separate tasks, on few i'll run script's for few of my things. some will be used for personal AI and tasks sent to it, some for rendering Queues etc.
 
Upvote 0 Downvote
Because those script's wouldn't work well in VM's. Those script's and software doesn't really like Virtualization. Also it's win 11 home, but upgrading to pro wouldn't be problem i think
 
Upvote 0 Downvote
Free solution: you need a Linux machine or VM/Docker running Apache Guacamole as a remote access gateway

Apache Guacamole®

guacamole.apache.org guacamole.apache.org

https://www.youtube.com/results?search_query=Apache+Guacamole


With general Windows RDP you have to open 50 different ports on the router/firewall in total for all machines or VMs and modify Windows registry for each machine (VM) so each one listens on different port (3389, 3390, 3391,...), and you have to specify different port for each machine when you are connecting them with RDP client. It's not feasible.
 
Last edited:
Upvote 0 Downvote
VNC remote control use graphics compression data transmission between machines IIRC, that takes a lot of traffic.

Yet Microsoft RDP use graphics API calls which execute on the local machine, no graphics/video transmitted, that makes a big difference.

If local machine and remote machine on on the same LAN, of course the difference will not be that large.
 
Upvote 0 Downvote
lantis3 said:
VNC remote control use graphics compression data transmission between machines IIRC, that takes a lot of traffic.

Yet Microsoft RDP use graphics API calls which execute on the local machine, no graphics/video transmitted, that makes a big difference.
Click to expand...
Which, due to the limited information we have about the actual use case, may or may not be an issue.

"running scripts" doesn't need a whole lot of real time graphics traffic.
 
Upvote 0 Downvote
Regarding:

"Those script's and software doesn't really like Virtualization."

What is meant by"doesn't really like"?

What scripts and software? Examples?

Specifically what are all those computers (virtually or otherwise) doing?

It would help to know the functional requirements....

As best I can understand, the immediate requirement is to able to quickly switch the main computer to remote into one of the other 50 computers.

May all be moot because the human is going to be slowest link in the process.

What is driving the need to switch computers?
 
Upvote 0 Downvote
Ralston18 said:
Regarding:

"Those script's and software doesn't really like Virtualization."

What is meant by"doesn't really like"?

What scripts and software? Examples?

Specifically what are all those computers (virtually or otherwise) doing?

It would help to know the functional requirements....

As best I can understand, the immediate requirement is to able to quickly switch the main computer to remote into one of the other 50 computers.

May all be moot because the human is going to be slowest link in the process.

What is driving the need to switch computers?
Click to expand...

Okay, looks like i won't escape answering this, so... most of those PC's would be running trading bots, about 30% bot's with few games and rest are rendering stations of mine.

In short I'd need to access the computer as if it would be a VM. simply open any of the computer's desktop when needed. Most of the processes are automatized but I'd need to connect to them and get to desktop whenever some error,bug or mistake would happen. So i expect like... needed to connect to 3-5 pc daily to fix problems. Nothing else
 
Upvote 0 Downvote
lantis3 said:
If OP is just running scripts, then it definitely wouldn't matter.

If OP wants to control the whole desktop, then it matters a lot.


Maybe OP just needs 50 users on one machine running different scripts.
Click to expand...
Okay, looks like i won't escape answering this, so... most of those PC's would be running trading bots, about 30% bot's with few games and rest are rendering stations of mine.

In short I'd need to access the computer as if it would be a VM. simply open any of the computer's desktop when needed. Most of the processes are automatized but I'd need to connect to them and get to desktop whenever some error,bug or mistake would happen. So i expect like... needed to connect to 3-5 pc daily to fix problems. Nothing else. So yeah i need access to desktop.
 
Upvote 0 Downvote
Ralston18 said:
Regarding:

"Those script's and software doesn't really like Virtualization."

What is meant by"doesn't really like"?

What scripts and software? Examples?

Specifically what are all those computers (virtually or otherwise) doing?

It would help to know the functional requirements....

As best I can understand, the immediate requirement is to able to quickly switch the main computer to remote into one of the other 50 computers.

May all be moot because the human is going to be slowest link in the process.

What is driving the need to switch computers?
Click to expand...
What is meant by"doesn't really like"?
Click to expand...
Too many problems and bugs occuring, VM's restarting script not working perfectly, usage of drivers etc. And as i said in next replies, the pc's running game's and renders need their separate computer since they need a lot of performance
 
Upvote 0 Downvote
The requirment being to fix problems on any given pc without needing to physically visit that pc.

VM's,. RDP etc. could be viable but I believe those tools would also prove cumbersome and problematic just on their own merits.

Conceptually you may be able to use Powershell Remoting to perform the required management functions.

Much more direct via PSSsession " -Computer Name" etc..

Plus you can write Powershell scripts for the most frequent "repair" requirements and target any given script to a selected computer in the network. Very straight forward to solicit the input of the Computer's Name and thus invoke the necessary script on that computer.

= = = =

Just FYI as a starting point:

https://learn.microsoft.com/en-us/p...g/running-remote-commands?view=powershell-7.4

Using Powershell is likely to be both simpler and easier to implement. Flexible and you will probably be able to create and apply ad hoc cmdlets etc. if and when needed.

You could do some basic testing using Powershell with little effort: I.e., "Restart Computer", "Get-EventLog".

Very likely that 20% of the Powershell cmdlets/scripts and so forth will fix 80% of the encounted problems.

And be willing to make trade-offs. No point in developing some cumbersome automated script/process that constantly needs tinkering and revisions when you can go directly to the problem computer and directly fix some rare issue within a couple of minutes.

That said, I will defer to those with more direct experience and knowledge regarding remotely managing 50 PC LANs.

Start simple.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom