Export (0) Print
Expand All
Expand Minimize

Set-WebConfiguration

Published: February 29, 2012

Updated: August 15, 2012

Applies To: Windows Server 2012

Set-WebConfiguration

Sets the value of an IIS configuration element.

Syntax

Parameter Set: InputPSObject
Set-WebConfiguration [-Filter] <String[]> [[-PSPath] <String[]> ] -Value <PSObject> [-Clr <String> ] [-Force] [-Location <String[]> ] [-Metadata <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: InputObject
Set-WebConfiguration [-Filter] <String[]> [[-PSPath] <String[]> ] -InputObject <Object> [-Clr <String> ] [-Force] [-Location <String[]> ] [-Metadata <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]




Detailed Description

The Set-WebConfiguration cmdlet changes the value of an IIS configuration element. The element can be specified as a configuration section or an XPath query.

Parameters

-Clr<String>

Version of the .NET framework in the form vn.n, such as v4.0 or v2.0. The default is v4.0. This parameter is used only when PSPath is set to either Machine or Machine/Webroot. If PSPath is not set to one of these values and the Clr parameter is set, PowerShell ignores the value of Clr and returns a warning.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Filter<String[]>

Specifies the IIS configuration section or an XPath query that returns a configuration element.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-Force

When theForceparameter is used, it causes the configuration setting to be set at a level in the configuration hierarchy above a lock in the configuration.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-InputObject<Object>

Specifies an object that contains values to set for configuration elements.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByValue, ByPropertyName)

Accept Wildcard Characters?

false

-Location<String[]>

The location of the configuration setting. Location tags are frequently used for configuration settings that must be set more precisely than per application or per virtual directory. For example, a setting for a particular file or directory could use a location tag. Location tags are also used if a particular section is locked. In such an instance, the configuration system would have to use a location tag in one of the parent configuration files.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-Metadata<String>

If this parameter is specified, configuration metadata such as encryption or locking settings can be changed.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-PSPath<String[]>

Specifies the configuration path. This can be either an IIS configuration path in the formatcomputer name/webroot/apphost, or the IIS module path in this format IIS:\sites\Default Web Site.


Aliases

none

Required?

false

Position?

2

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-Value<PSObject>

The value of the configuration setting to change.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.


Required?

false

Position?

named

Default Value

false

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.

Inputs

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

  • PSObject

Outputs

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

  • PSObject

Examples

-------------- EXAMPLE 1: Setting new Bindings on an existing Web site --------------

TheSet-WebConfigurationcmdlet is used to replace the existing bindings of the Web site named DemoSite with new bindings.


IIS:\>Set-WebConfiguration -filter '/system.applicationHost/sites/site[@name=" DemoSite"]/bindings' -PSPath IIS:\ -value (@{protocol="http";bindingInformation=”*:80:DemoSite1”},@{protocol="http";bindingInformation="*:80:DemoSite2"})

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft