• Contact
  • Homelab
Dimitris Tonias
  • Management
  • Monitoring
  • Cloud
  • Virtualization
  • Networking
  • Productivity
No Result
View All Result
  • Management
  • Monitoring
  • Cloud
  • Virtualization
  • Networking
  • Productivity
No Result
View All Result
Dimitris Tonias
No Result
View All Result

Enable PowerShell Remoting using Group Policy

Dimitris Tonias by Dimitris Tonias
December 23, 2017 - Updated on April 21, 2024
in Management
Reading Time: 2 mins read
A A
2
Share on FacebookShare on Twitter

PowerShell Remoting is a very powerful tool for each administrator, as it enables remote management of Windows Servers and Clients through PowerShell.

On Windows Server 2016 and Windows Server 2012 R2, PowerShell Remoting is enabled by default. However, in previous versions as well as in client versions of Windows, you will need to enable it by yourself. Since it is not wise to log on to each server and use the Enable-PSRemoting cmdlet interactively, we will use Group Policy to do it for us.

Since there is no specific policy to enable PowerShell Remoting, we will need to configure each parameter required to work properly. This means that we will create HTTP(S) Listeners, configure automatic start of the WinRM service and the set the appropriate rules in the Windows Firewall.

Enable PowerShell Remoting using Group Policy

First, open the Group Policy Management Console window and create a new Group Policy Object. You do not need to apply it to an OU yet, it would be better to test it before dropping it into production servers.

Configure WinRM Listeners

Follow the path: Computer Configuration \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service

Here, open Allow remote server management via WinRM and set the switch to Enabled. In the filter field, use the wildcard (*) to specify all IP addresses or use a specific IP address range for greater security and server lockdown.

Enable PowerShell Remoting using Group Policy

Set the WinRM service to start automatically

WinRM service runs automatically, by default, in the latest versions of Windows Server. However, this is not the case with Windows client computers. So, you can start the service through Group Policy. Let me point out that Group Policy will start the WinRM service on the next computer restart as it can not be done dynamically at any given time.

Follow the path: Computer Configuration \ Windows Settings \ Security Settings \ System Services

Here, double-click Windows Remote Management (WS-Management) to see its properties and set the start-up mode to Automatic, as shown in the figure below.

Enable PowerShell Remoting using Group Policy

Configure Windows Firewall

Follow the path: Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Windows Firewall with Advanced Security

Here, right-click on Inbound Rules and then in New Rule. In the window that appears, enable the Predefined type and select Windows Remote Management.

Enable PowerShell Remoting using Group Policy

Choose whether to allow access to Domain / Private networks and/or Public networks.

Enable PowerShell Remoting using Group Policy

Finally, leave Allow the connection enabled and click Finish to create the new rules in the Windows Firewall.

Enable PowerShell Remoting using Group Policy

That’s it!

Tags: PowerShellPowerShell RemotingWindows Server 2016WinRM
ShareTweetPin
Previous Post

Install Remote Server Administration Tools (RSAT) in Windows 10

Next Post

Enable Remote Desktop in Windows Server 2016

Related Posts

Approve updates in WSUS 2016
Management

Approve updates in WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016
Management

Configure Group Policy to deploy updates using WSUS 2016

Configure computer groups in WSUS 2016
Management

Configure computer groups in WSUS 2016

The initial configuration of WSUS 2016
Management

The initial configuration of WSUS 2016

Install WSUS in Windows Server 2016
Management

Install WSUS in Windows Server 2016

Error opening Report Viewer on WSUS 2016
Management

Error opening Report Viewer on WSUS 2016

Comments 2

  1. Steve Pence says:
    7 years ago

    I’m not in a domain environment. I can allow WinRM and set the firewall rules by local policy, but I don’t see a way via local policies to guarantee a service startup. Any suggestions?

    Reply
    • Xiakit says:
      7 years ago

      just go to services and rightclick on the winrm service and set the service to automatic startup.

      Or run this as admin:
      Get-Service -Name “winrm” | Set-Service -StartupType Automatic

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

No Result
View All Result
Zabbix server: More than 75% used in the trends cache
Monitoring

Zabbix server: More than 75% used in the trends cache

In Zabbix, "trends" are a type of data storage representing aggregated historical data. Zabbix monitors and collects a vast amount...

Read moreDetails
Check word count on Google Docs

Check word count on Google Docs

Zabbix server: More than 75% used in the configuration cache

Zabbix server: More than 75% used in the configuration cache

Approve updates in WSUS 2016

Approve updates in WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016

Configure Group Policy to deploy updates using WSUS 2016

Configure computer groups in WSUS 2016

Configure computer groups in WSUS 2016

The initial configuration of WSUS 2016

The initial configuration of WSUS 2016

Get more stuff

Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.

we respect your privacy and take protecting it seriously

  • Contact
  • Homelab

© 2024 Dimitris Tonias

No Result
View All Result
  • About
  • Contact
  • Free Tools
  • Home
  • Homelab

© 2024 Dimitris Tonias

This website uses cookies. By continuing to use this website you are giving consent to cookies being used.