PowerShell Remoting (Enable-PSRemoting) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable PowerShell remoting on the local computer.

PowerShell

Enable-PSRemoting -[1]

Drag options to blanks, or click blank then click option'

AStop

BDisable

CForce

DRemove

Attempts:

3 left

💡 Hint

Common Mistakes

Using parameters that disable or stop remoting instead of enabling it.

Omitting the parameter and expecting no prompts.

The -Force parameter runs the command without asking for confirmation, enabling remoting immediately.

2fill in blank

medium

Complete the code to check the status of the WinRM service.

PowerShell

Get-Service -Name [1]

Drag options to blanks, or click blank then click option'

AWinRM

Bwuauserv

CSpooler

DBITS

Attempts:

3 left

💡 Hint

Common Mistakes

Checking unrelated services like Windows Update or Print Spooler.

Using incorrect service names.

The WinRM service is responsible for PowerShell remoting. Checking its status helps verify if remoting is enabled.

3fill in blank

hard

Fix the error in the command to enable remoting without confirmation prompts.

PowerShell

Enable-PSRemoting -[1]

Drag options to blanks, or click blank then click option'

ASkip

BConfirm

CNoConfirm

DForce

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent parameters like -NoConfirm or -Skip.

Using -Confirm which actually asks for confirmation.

The correct parameter to suppress confirmation prompts is -Force. Other options are invalid and cause errors.

4fill in blank

hard

Fill both blanks to create a firewall rule that allows PowerShell remoting.

PowerShell

New-NetFirewallRule -Name 'PSRemoting' -DisplayName 'PowerShell Remoting' -[1] TCP -LocalPort [2] -Action Allow

Drag options to blanks, or click blank then click option'

AProtocol

BUDP

C5985

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using UDP instead of TCP for the protocol.

Using wrong port numbers like 80.

The -Protocol parameter specifies the protocol type, which is TCP for PowerShell remoting. The -LocalPort should be set to 5985, the default WinRM port.

5fill in blank

hard

Fill all three blanks to create a session to a remote computer named 'Server01'.

PowerShell

$session = New-PSSession -ComputerName [1] -Credential [2] -Authentication [3]

Drag options to blanks, or click blank then click option'

AServer01

BGet-Credential

CDefault

DLocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Localhost' instead of the remote computer name.

Passing credentials as a string instead of using Get-Credential.

Using incorrect authentication methods.

Server01 is the remote computer name. Get-Credential prompts for user credentials. Default is the common authentication method for remoting.