: Is it possible to have permanent remote access to several Win11 computers?
: Is it possible to have permanent remote access to several Win11 computers?
An alternative method is connecting to one machine via RDP and then connecting to the remaining devices using RDP.
It seems like most PCs would be handling trading bots, with around 30% focused on games and the rest acting as rendering stations for me. In short, I’d have to treat the computer like a VM—just open the desktop when needed. Most tasks are automated, but I’d still need to connect to them and reach the desktop whenever errors or bugs occur. I’d likely need to do this 3-5 times a day just to troubleshoot issues. Nothing else.
It seems like most PCs are likely running trading bots, with around 30% being mostly bot-based and the rest serving as rendering stations for my work. In short, I’d have to treat the computer like a VM—just open the desktop when needed. Most tasks are automated, but I’d still need to connect to them and access the desktop whenever errors or bugs occur. I’d probably need to do this 3-5 times a day just to troubleshoot issues. That’s essentially my requirement.
There are numerous issues and errors happening frequently. The VM's restart script isn't functioning correctly, driver usage is problematic, and performance problems persist. As mentioned earlier, the PC's game and rendering tasks require a dedicated machine due to high demands.
The need is to resolve issues on any PC without having to physically be there. Virtual machines, RDP, etc., might work but could become too complicated and troublesome in isolation. You might conceptually rely on PowerShell Remoting to carry out management tasks. Alternatively, a more direct approach using PSSession with the computer name is possible. You can also craft PowerShell scripts for common repair needs and direct them to any specific machine in the network. It’s quite straightforward to ask for the target computer’s name and run the appropriate script.
Just a note:
https://learn.microsoft.com/en-us/powers...rshell-7.4
Using PowerShell is likely to simplify things and make implementation easier. It offers flexibility, allowing you to create custom cmdlets on demand. You could perform basic tests with minimal effort—such as restarting the computer or retrieving event logs.
It’s probable that around 20% of PowerShell commands/scripts will address 80% of the problems. Be open to making compromises. It’s better to avoid building overly complex automated processes when a direct fix on the affected machine can resolve the issue quickly, within minutes.
That said, I’ll leave it to those with more hands-on experience managing remote systems across multiple PCs and LANs. Start simple.