CmdID / PowerShell / Cmdlets / Enable
Enable-PSRemoting
Configures the computer to receive remote commands. PowerShell reference
From the PowerShell reference 4 parameters
What it does
Configures the computer to receive remote commands. The Enable-PSRemoting cmdlet configures the computer to receive PowerShell remote commands that are sent by using the WS-Management technology. PowerShell remoting is enabled by default on Windows Server 2012 and higher. You can use Enable-PSRemoting to enable PowerShell remoting on other supported versions of Windows and to re-enable remoting if it becomes disabled. You need to run this command only one time on each computer that receive commands. You don't need to run it on computers that only send commands. Because the configuration starts listeners, it's prudent to run it only where it's needed. Beginning in PowerShell 3.0, the Enable-PSRemoting cmdlet can enable PowerShell remoting on client versions of Windows when the computer is on a public network. For more information, see the description of the SkipNetworkProfileCheck parameter. The Enable-PSRemoting cmdlet performs the following operations: - Runs the Set-WSManQuickConfig cmdlet, which performs the following tasks: - Starts the WinRM service. - Sets the startup type on the WinRM service to Automatic. - Creates a listener to accept requests on any IP address. - Enables a firewall exception for WS-Management communications. - Registers the Microsoft.PowerShell and Microsoft.PowerShell.Workflow session configurations, if it they're not already registered. - Registers the Microsoft.PowerShell32 session configuration on 64-bit computers, if it's not already registered. - Enables all session configurations. - Changes the security descriptor of all session configurations to allow remote access. - Restarts the WinRM service to make the preceding changes effective. To run this cmdlet on the Windows platform, start PowerShell by using the Run as administrator option. For more information about using PowerShell remoting, see the following articles: - about_Remote_Requirements - about_Remote
Enable-PSRemoting [-Force] [-SkipNetworkProfileCheck] [-WhatIf] [-Confirm] [<CommonParameters>]Configure a computer to receive remote commands
Enable-PSRemotingIdentifyConfigure a computer to receive remote commands without a confirmation prompt
Enable-PSRemoting -ForceIdentifyAllow remote access on clients
Get-NetFirewallRule -Name 'WINRM*' | Select-Object -Property NameIdentifyIts page in the reference: Enable-PSRemoting.
Parameters
-ForceForces the command to run without asking for user confirmation.-SkipNetworkProfileCheckIndicates that this cmdlet enables remoting on client versions of the Windows operating system when the computer is on a public network. This parameter enables a firewall rule for public networks that allows remote access only from computers in the same local subnet.
This parameter doesn't affect server versions of the Windows operating system, which, by default, have a local subnet firewall rule for public networks. If the local subnet firewall rule is disabled on a server version, Enable-PSRemoting re-enables it, regardless of the value of this parameter.
To remove the local subnet restriction and enable remote access from all locations on public networks, use the Set-NetFirewallRule cmdlet in the NetSecurity module.
This parameter was introduced in PowerShell 3.0.-ConfirmPrompts you for confirmation before running the cmdlet.-WhatIfShows what would happen if the cmdlet runs. The cmdlet isn't run.