PowerShell Remoting (Enable-PSRemoting) - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of enabling PowerShell remoting on a fresh Windows machine?

You run the command Enable-PSRemoting -Force on a Windows machine that has never had remoting enabled before. What is the expected output?

PowerShell

Enable-PSRemoting -Force

A WinRM service is started and set to automatic. Firewall rules for WS-Management are enabled. Output: "WinRM has been updated to receive requests."

B WinRM service is started and set to automatic. Firewall rules for WS-Management are enabled. Output: "WinRM is already set up to receive requests."

C Error: "Access Denied" because administrator privileges are required.

D No output and no changes because remoting is disabled by default and must be enabled in Group Policy.

💡 Hint

Think about what Enable-PSRemoting does when run with -Force on a fresh system.

Enable-PSRemoting -Force starts the WinRM service, sets it to automatic, and enables firewall rules. It outputs a confirmation message that WinRM has been updated to receive requests.

🧠 Conceptual

intermediate

Which firewall rules does Enable-PSRemoting enable by default?

When you run Enable-PSRemoting, which firewall rules are enabled to allow remote PowerShell sessions?

A Rules for WS-Management (WinRM) inbound traffic on ports 5985 (HTTP) and 5986 (HTTPS).

B Rules for HTTP (port 80) and HTTPS (port 443) inbound traffic.

C Rules for SMB (port 445) inbound traffic.

D Rules for RDP (port 3389) inbound traffic.

💡 Hint

WinRM uses specific ports for remoting.

Enable-PSRemoting enables firewall rules for WS-Management, which uses ports 5985 for HTTP and 5986 for HTTPS to allow remote PowerShell sessions.

🔧 Debug

advanced

Why does this Enable-PSRemoting command fail with an access denied error?

You run Enable-PSRemoting -Force in a PowerShell window but get an "Access Denied" error. What is the most likely cause?

A The WinRM service is already running and cannot be restarted.

B You are running PowerShell without administrator privileges.

C The firewall is blocking outbound traffic.

D PowerShell remoting is disabled in Group Policy and cannot be enabled manually.

💡 Hint

Think about what permissions are needed to change system services and firewall rules.

Enable-PSRemoting requires administrator privileges because it starts services and modifies firewall rules. Running without admin rights causes access denied errors.

🚀 Application

advanced

How to enable PowerShell remoting only for the current user?

You want to enable PowerShell remoting but only for your current user account, not system-wide. Which command achieves this?

A Enable-PSRemoting -Force -Scope CurrentUser

B Enable-PSRemoting -Force -SessionOption CurrentUser

C Enable-PSRemoting -Force (no parameter supports user-only scope)

D Enable-PSRemoting -Force -UserScope

💡 Hint

Check the official parameters of Enable-PSRemoting.

Enable-PSRemoting does not support enabling remoting scoped to a single user. It configures system-wide settings.

💻 Command Output

expert

What is the output of running Enable-PSRemoting on a machine where remoting is already enabled?

You run Enable-PSRemoting -Force on a machine where remoting was enabled previously and no changes are needed. What output do you get?

PowerShell

Enable-PSRemoting -Force

A No output, command runs silently.

B "WinRM has been updated to receive requests."

C Error: "Remoting already enabled, cannot run Enable-PSRemoting again."

D "WinRM is already set up to receive requests on this machine."

💡 Hint

Think about idempotent commands and their output.

When remoting is already enabled, Enable-PSRemoting outputs a message stating WinRM is already set up to receive requests.