Add-WebConfigurationLock
Published: February 29, 2012
Updated: August 15, 2012
Applies To: Windows Server 2012
Add-WebConfigurationLock
Syntax
Parameter Set: Default Add-WebConfigurationLock [-Filter] <String[]> [[-PSPath] <String[]> ] -Type <String> [-Force] [-Location <String[]> ] [-Passthru] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
Locks an IIS configuration section, element, or attribute.
Parameters
-Filter<String[]>
An XPath filter expression.
|
Aliases |
none |
|
Required? |
true |
|
Position? |
1 |
|
Default Value |
none |
|
Accept Pipeline Input? |
true (ByPropertyName) |
|
Accept Wildcard Characters? |
false |
-Force
Forces the configuration lock.
|
Aliases |
none |
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-Location<String[]>
The location at which the configuration lock is applied.
|
Aliases |
none |
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
true (ByPropertyName) |
|
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 |
-Passthru
Passes an object that represents the configuration lock to the pipeline.
|
Aliases |
none |
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-Type<String>
Specifies the type of configuration lock to add.
|
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.
Examples
-------------- EXAMPLE 1: Adding and removing configuration locks --------------
This example demonstrates how to add and remove inclusive and exclusive locks using a filter.
IIS:\>Add-WebConfigurationLock -Type general -Filter //asp Remove-WebConfigurationLock -Filter //asp Add-WebConfigurationLock -Type inclusive -Filter //asp/@lcid Remove-WebConfigurationLock -Filter //asp/@lcid Add-WebConfigurationLock -Type exclusive -Filter //asp/@lcid
Related topics
