Question Permanent Remote access to multiple win11 computers?

[wckdg32516]

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.

 

[wckdg32516]

That... actually makes a lot of sense. I was trying to overcomplicate things through desktop remote control. It would be posible to run the scripts and programs without using any of the UI, just with commands

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.

ur right ig.... i think i can ran everything through another scripts or commands without actual desktop, but it would be more comfortable with desktop type remote access

 

[USAFRet]

That... actually makes a lot of sense. I was trying to overcomplicate things through desktop remote control. It would be posible to run the scripts and programs without using any of the UI, just with commands

This is why more info and requirements up front are almost always a good idea.

We don't care what you're wanting to do (as long as its not illegal or against Forum rules).

Knowing the what and why often leads to a better how.

We could have dispensed with the suggestions of multiple user accounts or VMs.

 

[Ralston18]

Agree, in general, with comfortable.

Just imagine your computers being all over the country. 😱

However, if you start simple, use a local test pc or two dedicated/designated for testing , then you can make it all work.

General work flow:

Use a Get cmdlet to check the target system's configuration/status etc..

Run the necessary Powershell cmdlet/script to make a change.

Run the Get cmdlet a second time to confirm the change.

Specific details will vary.

And you are free to RDP into to the system or physically visit (at least initially) the target PC to confirm changes.

Key is to test beforehand and, as should be being done anyway, have the network computers backed up. Just in case.

Your comfort level will evolve....

 

[USAFRet]

additionally, have one or two systems set up as test boxes.
To test and verify whatever updates or fixes you want to propagate to all the others.

If something goes wrong with one of these test boxes, no harm no foul. Just rebuild completely from the backup.

Once a specific script or procedure is finalized and tested working on the test box, then you deploy out to the others.

 

[lantis3]

Don't know what kind of tech difficulty OP was facing. Still think VM (or multi users if desktop not required) is the way to go.

There are VMware/ESXi, VirtualBox, Hyper-V, Proxmox, UnRAID, etc. can be tried. The remote control will be much easier.

 

[wckdg32516]

hmm okay thank you all, i 've got all answers i needed.