PowerShell Remoting allows you to manage a remote computer from your local computer. You type commands on your local computer, and the changes are made on the remote computer. When you set up a PowerShell Remoting connection, you can execute commands remotely, and the changes will be made on the remote computer. The remote computer is the computer that you want to manage, and your local computer is the computer that you are using to manage the remote computer.

Here are some important points to keep in mind before setting up a PowerShell Remoting connection:

1. Both the local and remote computers must be in the same domain or workgroup. This is because PowerShell Remoting uses Windows Remote Management (WinRM), which is a feature of Active Directory.
2. Both computers must have PowerShell installed. PowerShell is a command-line shell and scripting language that is included with Windows.
3. AD-DS, DHCP, and DNS servers must be configured and running on your network. These servers are used by WinRM to authenticate users and resolve hostnames.
4. The IP address configuration on both computers must be correct. The remote computer’s IP address must be reachable from the local computer.
5. The network adapter connection type for all network adapters on both computers must be set to Private. If any of the network adapters are set to Public, you will receive an error when you try to connect to the remote computer.

Create PowerShell Remoting Sessions

Follow the steps below to set up a PowerShell Remoting connection.

1. Enable Powershell remoting on the remote computer by running the Enable-PSRemoting command.

2. Set up a remote connection by typing the Enter-PSSession -ComputerName [Name of the computer] command in the local computer. The name of the machine that you are connected to will add at the beginning of commands to show that you are running commands on that particular machine.

3. If you want to create multiple sessions, use the command New-PSSession [Computer Name]. Instead of [Computer Name] use the computer name of your own machine.

4. To see the list of created PowerShell sessions, type the command Get-PSSessions. As you can see, I have one PowerShell session in the list and it is available for connection.

5. Type the command Get-Command -Noun PSSession to see the list of PowerShell Remoting session commands.

You don’t have to use PowerShell Remoting for commands that have computer name parameters. You can execute commands that have computer name parameters on the target computer without setting up a PowerShell Remoting session.

PowerShell Remoting is much faster than other remoting tools because it uses commands and scripts to manage the target computer. You can create multiple remoting sessions without loading much on the CPU.

Check out this article to know more about PowerShell Remoting.

The post How to Set up a PowerShell Remoting Connection appeared first on TECHNIG.

PowerShell offers a quick way to manage computers remotely through scripting and cmdlets. You can enable Windows PowerShell Remoting to manage multiple computers remotely in Windows 11 and other latest windows.

While setting up a remote connection between computers, Windows Firewall blocks the request to the remote computer, so you have to allow the firewall features related to remote management in the Windows Firewall. Go to Control Panel, System and Security, Windows Defender Firewall, and click on Allow an app or feature through Windows Defender Firewall.

In order to be able to set up PowerShell remoting in Windows 11, allow the following features in the Windows Defender Firewall.

1. Remote Desktop
2. Remote Assistance
3. Remote Event Log Management
4. Remote Event Monitor
5. Remote Scheduled Tasks Management
6. Remote Service Management
7. Remote Shut-down
8. Remote Volume Management
9. Virtual Machine Monitoring
10. Windows Firewall Remote Management
11. Windows Management Instrumentation (WMI)
12. Windows Remote Management
13. Windows Remote Management (Compatibility)

It looks a long way and has a lot of things to configure. The quick way is to enable it through PowerShell. Open PowerShell as administrator and then type Enable-PSRemoting. If this command does not run successfully, then you have to allow the features mentioned above manually.

Sometimes you will receive an error message. If your computer’s network adapter is set up for a public network, then you have to change the connection type to private.

For more about PowerShell remoting, click here.

Change Network Profile Type Using PowerShell

To change the network profile type from public network to private network using PowerShell, follow the steps below.

4. When you type a command in PowerShell, and it runs without any error, then it means that the configuration is successful. To make sure that the Network type changed from Public to Private, type Get-NetConnectionProfile -InterfaceIndex 15command.

Now that the connection type changed from public to private try to enable PowerShell remoting.

PowerShell is a great tool to configure windows settings locally or remotely because there is no Graphical User Interface (GUI) involved, and it runs the command quickly. Another advantage of PowerShell is that you can manage multiple remote computers at the same time, and run one command on multiple computers.

The post Enable PowerShell Remoting in Windows 11 appeared first on TECHNIG.