Export (0) Print
Expand All

Set-WSManQuickConfig

Updated: December 3, 2014

Applies To: Windows PowerShell 4.0

Set-WSManQuickConfig

Configures the local computer for remote management.

Syntax

Parameter Set: Default
Set-WSManQuickConfig [-Force] [-SkipNetworkProfileCheck] [-UseSSL] [ <CommonParameters>]




Detailed Description

The Set-WSManQuickConfig cmdlet configures the computer to receive Windows PowerShell remote commands that are sent by using the Web Services for Management (WS-Management) technology.

The cmdlet performs the following:

-- Checks whether the WinRM service is running. If the WinRM service is not running, the service is started.

-- Sets the WinRM service startup type to automatic.

-- Creates a listener to accept requests on any IP address. By default, the transport is HTTP.

-- Enables a firewall exception for WinRM traffic .

To run this cmdlet, start Windows PowerShell with the "Run as administrator" option.

Parameters

-Force

Sets the configuration without first prompting the user.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-SkipNetworkProfileCheck

Configures client versions of Windows for remoting 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 has no effect on server versions of Windows, which, by default, have a local subnet firewall rule for public networks. If the local subnet firewall rule is disabled on a server version of Windows, 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 is introduced in Windows PowerShell 3.0.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-UseSSL

Specifies that the Secure Sockets Layer (SSL) protocol should be used to establish a connnection to the remote computer. By default, SSL is not used.

WS-Management encrypts all Windows PowerShell content transmitted over the network. The UseSSL parameter lets you specify that the additional protection of using HTTPS instead of HTTP should be used. If you specify this parameter, but SSL is not available on the port used for the connection, the command fails.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see  about_CommonParameters (http://go.microsoft.com/fwlink/p/?LinkID=113216).

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • None

    This cmdlet does not accept any input.


Outputs

The output type is the type of the objects that the cmdlet emits.

  • None

    This cmdlet does not generate any output.


Examples

-------------------------- EXAMPLE 1 --------------------------

This command sets the required configuration to enable remote management of the local computer. By default, this command creates a WS-Management listener on HTTP.


PS C:\> Set-WSManQuickConfig

-------------------------- EXAMPLE 2 --------------------------

The command sets the required configuration to enable remote management of the local computer. The UseSSL parameter makes the command create a WS-Management listener on HTTPS.


PS C:\> Set-WSManQuickConfig -UseSSL

Related topics



Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft