Jeong's Blog : Powershell

IIS Powershell User guide - Comparing representative IIS UI tasks

JeongHwan — Thu, 31 Jul 2008 00:59:00 GMT

1. [File System] Open Explorer window for Default Web Site's home directory

$path = $(get-item 'iis:\sites\default web site').physicalPath

$path = [system.environment]::ExpandEnvironmentVariables($path)

explorer $path

Related UI Task:"Explorer"

2. [File System] Open Explorer window for Default Web Site's home directory using "DirectoryName" property

$path = $(get-item 'iis:\sites\default web site\iisstart.htm').directoryName

explorer $path

Related UI Task:"Explorer"

3. [File System] Create File and set file content programmatically

$file = new-item demo.htm -type file

set-content $file.FullName "Hey, dude!"

Related UI Task:"Explorer"

4. [File System] Set "Deny" for administrator user account for 'iisstart.htm' file and grant access permission for NTAccount

$file = $(get-item "iis:\sites\Default Web Site\iisstart.htm ")

$dacl = $file.GetAccessControl()

$newRule = New-Object Security.AccessControl.FileSystemAccessRule Administrator, Modify, Deny

$modified = $false

$dacl.ModifyAccessRule("Add", $newRule, [ref]$modified)

$file.SetAccessControl($dacl)

$file.GetAccessControl().GetAccessRules($true, $true, [System.Security.Principal.NTAccount])

Related UI Task:"Edit Permissions..."

5. [Application Pool] Get the list of application pools

dir iis:\apppools

Related UI Task:"Application Pools" treeview

6. [Application Pool] Create a new pool

New-Item iis:\apppools\demoAppPool

Or, you can use other task-based cmdlet(s) instead:

New-AppPool demoAppPool

NOTE: New-AppPool cannot use full path name such as “iis:\appPools\demoAppPool” like other user-friendly-named cmdlets

Related UI Task:"Add Application Pool..."

7. [Application Pool] Rename an Application Pool

Rename-Item iis:\apppools\defaultapppool newAppPoolName

Related UI Task:"Rename "

8. [Application Pool] Remove an Application Pool

Remove-Item iis:\apppools\defaultapppool

Or, you can use other task-based cmdlet(s) instead:

Remove-AppPool defaultapppool

Related UI Task:"Remove "

9. [Application Pool] Stop/Start/Recycle Application Pool

Start-WebItem IIS:\AppPools\DefaultAppPoolStop-WebItem IIS:\AppPools\DefaultAppPoolRestart-WebItem IIS:\AppPools\DefaultAppPool

Or, you can use other task-based cmdlet(s) instead:

Start-AppPool DefaultAppPool

Stop-AppPool DefaultAppPool

Restart-AppPool DefaultAppPool

Related UI Task:"Stop/Start/Recycle"

10. [Application Pool] Get the current status of Application Pool

Get-WebItemState iis:\apppools\defaultapppool

Or, you can use other task-based cmdlet(s) instead:

Get-AppPoolState defaultapppool

Related UI Task:"Stop/Start/Recycle"

11. [Application Pool] Get the list of application which is belonged to an Application Pool

function ConvertFrom-ItemXPath($itemXpath)

{

$result = new-object psobject

$tempString = $itemXPath.substring($itemXPath.IndexOf("@name"))

add-member -in $result noteproperty Site $tempString.Split("'")[1]

$tempString = $itemXPath.substring($itemXPath.IndexOf("@path"))

add-member -in $result noteproperty Application $tempString.Split("'")[1]

return $result

}

$applications = get-webconfiguration //application[@applicationPool]

$applications | select itemXpath, applicationpool | foreach {if ($_.applicationPool -eq "DefaultAppPool") {ConvertFrom-ItemXPath ($_.itemXpath)}}

Related UI Task:"View Applications"

12. [Application Pool] Get Application Pool Default Settings

$subsections = get-webconfiguration //applicationPoolDefaults//. -PSPATH iis:\

$subsections | foreach { $_.attributes | select name,value }

PS IIS:\> $subsections = get-webconfiguration //applicationPoolDefaults//.PS IIS:\> $subsections | foreach { $_.attributes | select name,value } Name Value---- -----namequeueLength 1000autoStart Trueenable32BitAppOnWin64 FalsemanagedRuntimeVersion v2.0enableConfigurationOverride TruemanagedPipelineMode 0passAnonymousToken TrueidentityType 2userNamepasswordloadUserProfile FalsemanualGroupMembership FalseidleTimeout 00:20:00maxProcesses 1shutdownTimeLimit 00:01:30startupTimeLimit 00:01:30pingingEnabled TruepingInterval 00:00:30pingResponseTime 00:01:30disallowOverlappingRotation FalsedisallowRotationOnConfigChange FalselogEventOnRecycle 137memory 0privateMemory 0requests 0time 1.05:00:00value 11:59:00value 11:32:00loadBalancerCapabilities 1orphanWorkerProcess FalseorphanActionExeorphanActionParamsrapidFailProtection FalserapidFailProtectionInterval 00:05:00rapidFailProtectionMaxCrashes 5autoShutdownExeautoShutdownParamslimit 0action 0resetInterval 00:05:00smpAffinitized FalsesmpProcessorAffinityMask 4294967295

logEventOnRecyle property value shows number value, which is not human-readable. You can get the text enum value by querying the specific property instead such as shown in the following:

get-webconfiguration //applicationPoolDefaults/recycling/@logEventOnRecycle

PS IIS:\> get-webconfiguration //applicationPoolDefaults/recycling/@logEventOnRecycleTime,Memory

Related UI Task:"Set Application Pool Defaults..."

13. [Application Pool] Set Application Pool Default Settings

Case1: Setting queueLength, which is “property” type

set-webconfigurationproperty /system.applicationHost/applicationPools/applicationPoolDefaults[1]/failure[1] -name rapidFailProtectionMaxCrashes -value 10

# You could get the section path of the target property programmaticallyPS IIS:\> get-webconfiguration //*[@rapidFailProtectionMaxCrashes] | foreach {$_.itemXPath}/system.applicationHost/applicationPools/applicationPoolDefaults[1]/failure[1]/system.applicationHost/applicationPools/add[@name='DefaultAppPool']/failure[1]/system.applicationHost/applicationPools/add[@name='Classic .NET AppPool']/failure[1] # Set the property value with the section pathPS IIS:\> set-webconfigurationproperty /system.applicationHost/applicationPools/applicationPoolDefaults[1]/failure[1] -name rapidFailProtectionMaxCrashes -value 10 NOTE: “applicationPoolDefaults[1]/failure[1]” is equivalent to “applicationPoolDefaults/failure”.

Case2: Setting schedule, which is “element” type (shown as “Specific Times” in UI)

add-webconfiguration /system.applicationHost/applicationPools/applicationPoolDefaults/recycling/periodicRestart/schedule -value (New-TimeSpan -h 9 -m30)

# Add new ‘Add’ element with a new-timespan value and add-webconfiguration cmdletPS IIS:\> add-webconfiguration /system.applicationHost/applicationPools/applicationPoolDefaults/recycling/periodicRestart/schedule -value (New-TimeSpan -h 9 -m30) # Confirm the new value is addedPS IIS:\> get-webconfiguration /system.applicationHost/applicationPools/applicationPoolDefaults/recycling/periodicRestart/schedule/add | select value value-----09:30:00

Related UI Task:"Set Application Pool Defaults..."

14. [Application Pool] Get configuration settings for a specific application pool

$configSection = "/system.applicationHost/applicationPools/add[@name='DefaultAppPool']//."

$subsections = get-webconfiguration $configSection -PSPath iis:\

$subsections | foreach { $_.attributes | select name,value }

Or, you can use “*” instead of the full config section path:

$subsections = get-webconfiguration '//*[@name="DefaultAppPool"]//.' -PSPath iis:\

$subsections | foreach { $_.attributes | select name,value }

Related UI Task:"Advanced Settings..."

15. [Application Pool] Set configuration settings for a specific application pool

Case1: Setting logEventOnRecycle, which is “enum property” type

$configSection = "/system.applicationHost/applicationPools/add[@name='DefaultAppPool']/recycling"

set-webconfigurationproperty $configSection -name logEventOnRecycle -value 1 -PSPath iis:\

NOTE: The value could be set with "Time" in the next version instead of 1 for the above example

Related UI Task:"Advanced Settings..."

16. [Application Pool] Get the list of application pools

Dir iis:\sites

Related UI Task:"Sites" treeview

17. [Sites] Create a new Web Site

Case1: Create web site with single binding

$binding = @{protocol="http";bindingInformation="*:80:hostname"}

new-item "iis:\sites\demoSite" -type site –physicalPath c:\demoSite -bindings $binding

Case2: Create web site with multiple binding and specific id

$binding = (@{protocol="http";bindingInformation="*:80:hostname"},@{protocol="http";bindingInformation="*:80:hostname2"})

new-item "iis:\sites\demoSite" -type site -physicalPath c:\demoSite -bindings $binding -id 555

Or, you can use other task-based cmdlet(s) instead:

New-WebSite -Name DemoSite -Port 80 -HostHeader hostname –PhysicalPath c:\demoSite –ID 555

New-WebBinding -Site DemoSite -Port 80 -IPAddress * -HostHeader hostname2

Related UI Task:"Add Web Site..." wizard

18. [Sites] Set bindings

Case1: Create SSL Binding (127.0.0.1!443)

$certObect = get-item cert:\LocalMachine\My\E48803C3A6DDC8F2BFE3D8B7B7D56BBA70270F92new-item IIS:\SslBindings\127.0.0.1!443 -value $certObect

PS IIS:\> dir cert:\LocalMachine\My Directory: Microsoft.PowerShell.Security\Certificate::LocalMachine\My Thumbprint Subject---------- -------E48803C3A6DDC8F2BFE3D8B7B7D56BBA70270F92 CN=WMSvc-JHKIM-WTT3 PS IIS:\> $certObect = get-item cert:\LocalMachine\My\E48803C3A6DDC8F2BFE3D8B7B7D56BBA70270F92 PS IIS:\> new-item IIS:\SslBindings\127.0.0.1!443 -value $certObect IP Address Port Store Sites---------- ---- ----- -----127.0.0.1 443 My

Case2: Set 'Bindings' property with multiple binding information including the SSL binding which was created above.

$newBinding = (@{protocol="http";bindingInformation="127.0.0.1:80:normalSite"},@{protocol="https";bindingInformation="127.0.0.1:443:securedSite"})

Set-itemproperty "IIS:\Sites\Default Web Site" -name bindings -value $newBinding

Or, you can use other task-based cmdlet(s) instead:

New-WebBinding -Site "Default Web Site" -Port 443 -IPAddress 127.0.0.1 -HostHeader securedSite

NOTE: you can also use set-webconfiguration, set-webconfiguration or add-webconfigurationProperty.

Set-Webconfiguration '/system.applicationHost/sites/site[@name ="Default Web Site"]/bindings' -value $newBinding -PSPath iis:\

Set-WebconfigurationProperty '/system.applicationHost/sites/site[@name ="Default Web Site"]' -name bindings.collection -value $newBinding -at 0 -PSPath iis:\

Add-WebconfigurationProperty '/system.applicationHost/sites/site[@name ="Default Web Site"]' -name bindings.collection -value @{protocol="https";bindingInformation="127.0.0.1:443:securedSite"} -at 0 -PSPath iis:\

Case3: Change a certain value of existing 'Bindings' property using other task-based cmdlet.

Set-WebBinding -Site "Default Web Site" -Port 443 -IPAddress 127.0.0.1 -HostHeader securedSite -name Port -value 444

Case4: Removing binding information using other task-based cmdlet.

Remove-WebBinding -Site "Default Web Site" -Port 443 -IPAddress 127.0.0.1 -HostHeader securedSite

Or, you can use Remove-WebConfigurationProperty

Remove-WebconfigurationProperty '/system.applicationHost/sites/site[@name="Default Web Site"]' -name Bindings.collection -at @{protocol="https";bindingInformation="127.0.0.1:443:securedSite"} -PSPath iis:\

Case5: Clear all the binding information of a certain web site

Clear-Webconfiguration '/system.applicationHost/sites/site[@name="Default Web Site"]/bindings' -PSPath iis:\

NOTE: you can also use clear-itemproperty instead:

Clear-ItemProperty 'iis:\sites\Default Web Site' -name bindings

Related UI Task:"Bindings..."

19. [Sites] Rename an Web Site

Rename-Item "iis:\sites\default web site" newWebSiteName

Related UI Task:"Rename "

20. [Sites] Remove an Web Site

Remove-Item "iis:\sites\default web site"

Or, you can use other task-based cmdlet(s) instead:

Remove-WebSite " default web site"

Related UI Task:"Remove "

21. [Sites] Stop/Start/Restart Web Site

Start-WebItem "IIS:\Sites\Default Web Site"

Stop-WebItem "IIS:\Sites\Default Web Site"

Restart-WebItem "IIS:\Sites\Default Web Site"

Or, you can use other task-based cmdlet(s) instead:

Start-WebSite "Default Web Site"

Stop-WebSite "Default Web Site"

Restart-WebSite "Default Web Site"

Related UI Task:"Stop/Start/Restart"

22. [Sites] Get the current status of Web Site

Get-WebItemState "IIS:\Sites\Default Web Site"

Or, you can use other task-based cmdlet(s) instead:

Get-WebSiteState "Default Web Site"

Related UI Task:"Stop/Start/Recycle"

23. [Sites] Get Web Site Defaults Settings

$subsections = get-webconfiguration //siteDefaults//. -PSPATH iis:\

$subsections | foreach { $_.attributes | select name,value }

PS IIS:\> $subsections = get-webconfiguration //siteDefaults//. -PSPATH iis:\PS IIS:\> $subsections | foreach { $_.attributes | select name,value } Name Value---- -----nameid 0serverAutoStart TruemaxBandwidth 4294967295maxConnections 4294967295connectionTimeout 00:02:00logExtFileFlags 2215887customLogPluginClsidlogFormat 2directory %SystemDrive%\inetpub\logs\LogFilesperiod 1truncateSize 20971520localTimeRollover Falseenabled Trueenabled Falsedirectory %SystemDrive%\inetpub\logs\FailedReq...maxLogFiles 50maxLogFileSizeKB 512customActionsEnabled FalseallowUTF8 TrueserverAutoStart TrueunauthenticatedTimeout 30controlChannelTimeout 120dataChannelTimeout 30disableSocketPooling FalseserverListenBacklog 60minBytesPerSecond 240maxConnections 4294967295resetOnMaxConnections FalsemaxBandwidth 4294967295matchClientAddressForPort TruematchClientAddressForPasv TruemaxCommandLine 4096allowUnlisted TrueserverCertHashserverCertStoreName MYssl128 FalsecontrolChannelPolicy 1dataChannelPolicy 1clientCertificatePolicy 0useActiveDirectoryMapping FalsevalidationFlags 0revocationFreshnessTime 00:00:00revocationUrlRetrievalTimeout 00:01:00enabled FalseuserName IUSRpassworddefaultLogonDomain NT AUTHORITYlogonMethod 3enabled FalsedefaultLogonDomainlogonMethod 3enabled FalseimpersonationLevel 1exitMessagegreetingMessagebannerMessagemaxClientsMessagesuppressDefaultBanner FalseallowLocalDetailedErrors TrueexpandVariables FalsekeepPartialUploads FalseallowReplaceOnRename FalseallowReadUploadsInProgress FalseexternalIp4Addressmode 4adUserNameadPasswordadCacheRefresh 00:01:00showFlags 0virtualDirectoryTimeout 5logExtFileFlags 14716367directory D:\inetpub\logs\LogFilesperiod 1truncateSize 20971520localTimeRollover Falseenabled TrueselectiveLogging 7

Related UI Task:"Set Web Site Defaults..."

24. [Sites] Set Web Site Default Settings

Case1: Setting connectionTimeout

set-webconfigurationproperty "/system.applicationHost/sites/siteDefaults[1]/limits[1]" -name connectionTimeout -value (New-TimeSpan -sec 130)

# You could get the section path of the target property programmaticallyPS IIS:\> get-webconfiguration //*[@connectionTimeout] | foreach {$_.itemxpath}/system.applicationHost/webLimits/system.applicationHost/sites/siteDefaults[1]/limits[1]/system.applicationHost/sites/site[@name='Default Web Site' and @id='1']/limits[1] # Set the property value with the section pathPS IIS:\> set-webconfigurationproperty "/system.applicationHost/sites/siteDefaults[1]/limits[1]" -name connectionTimeout -value (New-TimeSpan -sec 130)

Related UI Task:"Set Web Site Defaults..."

25. [Sites] Get configuration settings for a specific web site

$configSection = "/system.applicationHost/sites/site[@name='Default Web Site']//."

$subsections = get-webconfiguration $configSection -PSPath iis:\

$subsections | foreach { $_.attributes | select name,value }

Or, you can use “*” instead of the full config section path:

$subsections = get-webconfiguration '//*[@name="Default Web Site"]//.' -PSPath iis:\

$subsections | foreach { $_.attributes | select name,value }

Related UI Task:"Advanced Settings..."

26. [Sites] Set configuration settings for a specific web site

Case1: Setting maxLogFiles

$configSection = "/system.applicationHost/sites/site[@name='Default Web Site' and @id='1']/traceFailedRequestsLogging"

set-webconfigurationproperty $configSection -name maxLogFiles -value 60 -PSPath iis:\

If you are trying to change basic properties, you could also use set-itemProperty as shown in the following:

Case2: 'Application Pool' property

Set-Itemproperty IIS:\Sites\DemoSite -name applicationPool -value demo

AppPool

Case3: 'Physical Path' property

set-itemproperty IIS:\Sites\DemoSite -name physicalPath -value c:\demoSite2

Case4: 'username' property

set-itemproperty IIS:\Sites\DemoSite -name userName -value newUserId

Case5: 'password' property

set-itemproperty IIS:\Sites\DemoSite -name password -value newPassword

Related UI Task:"Advanced Settings..."

27. [Sites] Set Failed Request Tracing for a specific web site

Case1: Enable Freb for a specific web site with setting maxLogFiles and directory

$configSection = "/system.applicationHost/sites/site[@name='Default Web Site' and @id='1']/traceFailedRequestsLogging"

set-webconfigurationproperty $configSection -name maxLogFiles -value 60 -PSPath iis:\

set-webconfigurationproperty $configSection -name directory -value c:\MyFailedReqLogFiles -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Enable-Freb -Site "default web site" -Directory "c:\MyFailedReqLogFiles" -MaxLogFileSize 555

Case2: Disable Freb for a specific web site

$configSection = "/system.applicationHost/sites/site[@name='Default Web Site' and @id='1']/traceFailedRequestsLogging"

set-webconfigurationproperty $configSection -name enabled -value false -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Disable-Freb -Site "default web site"

Case3: Clear Freb data for a specific web site

If you use Enable-Freb, it creates following default setting of Freb settings for the specified sites. We can clear them by this way.

<?xml version="1.0" encoding="UTF-8"?><configuration> <system.webServer> <tracing> <traceFailedRequests> <add path="*"> <traceAreas> <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module" verbosity="Verbose" /> <add provider="ASP" verbosity="Verbose" /> <add provider="ISAPI Extension" verbosity="Verbose" /> <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" /> </traceAreas> <failureDefinitions timeTaken="00:00:30" statusCodes="500" verbosity="Warning" /> </add> </traceFailedRequests> </tracing> </system.webServer></configuration>

Clear-WebConfiguration /system.webServer/tracing/traceFailedRequests -PSPath "iis:\sites\default web site"

Or, you can use other task-based cmdlet(s) instead:

Clear-FrebData -Site "default web site"

Related UI Task:"Advanced Settings..."

28. [Management] Read default feature Delegation settings

Case1: Dump all sectionGroups

get-webconfigurationproperty / -name sectiongroups

Case2: Dump specific sectionGroup such as "system.applicationHost"

get-webconfigurationproperty / -name sectiongroups["system.applicationHost"]

Case3: Dump all sections under "/" group

get-webconfigurationproperty / -name Sections

NOTE: You will see empty value because IIS configuration system does not have section under "root" level by default

Case4: Dump all sections under specific sectionGroup such as "system.webServer"

$sections = get-webconfigurationproperty /system.webserver -name Sections

$sections | select Name,OverrideModeDefault

PS IIS:\> $sections = get-webconfigurationproperty /system.webserver -name SectionsPS IIS:\> $sections | select Name,OverrideModeDefault Name OverrideModeDefault---- -------------------httpProtocol AllowhttpErrors DenyhttpRedirect AllowglobalModules Denycgi DenyserverRuntime DenydirectoryBrowse AllowurlCompression AllowhttpLogging Denymodules DenyodbcLogging Denyvalidation AllowfastCgi Denyhandlers DenyhttpTracing DenystaticContent AllowisapiFilters DenydefaultDocument Allowasp DenyhttpCompression DenyserverSideInclude Denycaching Allow

NOTE: Now you can see the default override mode for "ASP" config section is deny, which means we can configure ASP related properties only for 'server' level

Related UI Task:UI Feature: "Feature Delegation" page

29. [Management] Add/Remove customized IIS config section

Case1: Add "myGroup" sectiongroup under root

add-webconfigurationproperty / -name SectionGroups -value myGroup

Case2: Add "mySection" section under the myGroup sectiongroup which was created above

add-webconfigurationproperty /myGroup -name Sections -value mySection

Case3: Set OverrideModeDefault for the newly created section, "mySection"

set-webconfigurationproperty /myGroup -name Sections["mySection"].OverrideModeDefault -value Deny

Case4: Set AllowDefinition for the newly created section, "mySection"

set-webconfigurationproperty /myGroup -name Sections["mySection"].AllowDefinition -value AppHostOnly

Case5: Set AllowLocation for the newly created section, "mySection"

set-webconfigurationproperty /myGroup -name Sections["mySection"].AllowLocation -value false

Case6: Remove the "mySection" section which were created above

remove-webconfigurationproperty /myGroup -name Sections -at mySection

Case7: Remove the "myGroup" sectiongroup which were created above

remove-webconfigurationproperty / -name SectionGroups -at myGroup

Related UI Task:UI Feature: UI has no related task for this.

30. [Management] Configure Feature Delegation related settings

NOTE: Before changing delegation setting of a config section, you would need to remove previously configured properties and elements of the section and re-configure them again after the delegation setting is updated.

This is an example of how to remove ASP sections using clear-webconfiguration cmdlet:

clear-webconfiguration /system.webServer/asp -pspath MACHINE/WEBROOT/A

PPHOST/testSite

clear-webconfiguration /system.webServer/asp -pspath MACHINE/WEBROOT/A

PPHOST

# Get the list of previously configured items using -recurse optionPS IIS:\> get-webconfiguration //asp -Recurse SectionPath PSPath----------- ------/system.webServer/asp MACHINE/WEBROOT/APPHOST/system.webServer/asp MACHINE/WEBROOT/APPHOST/testSite # Clear those items using clear-webconfigurationPS IIS:\> clear-webconfiguration /system.webServer/asp -pspath MACHINE/WEBROOT/APPHOST/testSitePS IIS:\> clear-webconfiguration /system.webServer/asp -pspath MACHINE/WEBROOT/APPHOST

Case1: Read the current Delegation setting of ASP feature for 'server' level

get-webconfiguration //asp iis:\ | select OverrideMode

PS IIS:\> get-webconfiguration //asp iis:\ | select OverrideMode OverrideMode------------Inherit

NOTE: The value "inherit" means it uses the default override mode and it is actually "Deny" in the default IIS configuration

Case2: Set "Read-Write" for ASP feature for 'server' level

set-webconfiguration //asp -metadata overrideMode -value Allow -PSPath iis:\

Case3: Set "Not Delegated" for ASP feature for 'server' level

NOTE: "Not Delegated" task is only applicable to IIS UI world. Please use "Read Only" which is explained below.

Case4: Set "Read Only" for ASP feature for 'server' level

set-webconfiguration //asp -metadata overrideMode -value Deny -PSPath iis:\

Case5: Set "Reset to Inherited" for ASP feature for 'server' level

set-webconfiguration //asp -metadata overrideMode -value Inherit -PSPath iis:\

Case6: Change Delegation settings for 'site' level

set-webconfiguration //asp -metadata overrideMode -value Inherit -PSPath "iis:\sites\default web site"

Case7: Change Delegation settings for 'site' level using location

set-webconfiguration //asp -metadata overrideMode -value Inherit -PSPath "iis:\sites" -Location "default web site"

Related UI Task:UI Feature: "Feature Delegation" page

31. [IIS] Configure Clasic ASP properties

Case1: Read all ASP settings from 'server' level

$subsections = get-webconfiguration //asp//. -PSPATH iis:\

$subsections | foreach { $_.attributes | select name,value }

Case2: Read all ASP settings from 'web site' level such as "Default Web Site"

$subsections = get-webconfiguration //asp//. -PSPATH "iis:\sites\default web site"

$subsections | foreach { $_.attributes | select name,value }

Case3: Read all ASP settings from 'web application' level such as "DemoApplication "

$subsections = get-webconfiguration //asp//. -PSPATH "iis:\sites\default web site\demoapplication"

$subsections | foreach { $_.attributes | select name,value }

Case4: Read all ASP settings from 'file' level which is under an Web Site

$subsections = get-webconfiguration //asp//. -PSPATH "iis:\sites\default web site" -location iisstart.htm

$subsections | foreach { $_.attributes | select name,value }

Case5: Write an ASP setting, keepSessionIdSecure, for 'server' level

set-webconfigurationproperty "/system.webServer/asp/session[1]" -name keepSessionIdSecure -value true -PSPath iis:\

# You could get the section path of the target property programmaticallyPS IIS:\> get-webconfiguration //*[@keepSessionIdSecure] | foreach {$_.itemxpath}/system.webServer/asp/session[1] # Set the property value with the section pathPS IIS:\> set-webconfigurationproperty "/system.webServer/asp/session[1]" -name keepSessionIdSecure -value true -PSPath iis:\

Case6: Write an ASP setting, keepSessionIdSecure, for 'site' level

set-webconfigurationproperty "/system.webServer/asp/session[1]" -name keepSessionIdSecure -value true -PSPath "iis:\sites\default web site"

Case5: Write an ASP setting, keepSessionIdSecure, for 'file' level which is under an Web Site

set-webconfigurationproperty "/system.webServer/asp/session[1]" -name keepSessionIdSecure -value true -PSPath "iis:\sites\default web site" -location iisstart.htm

Related UI Task:UI Feature: "ASP" page

32. [IIS] Configure Authentication properties

Case1: List all of authentications and from 'server' level

get-webconfiguration /system.webServer/security/authentication/*[@enabled] -PSPath iis:\ | select ItemXPath,enabled

Case2: List all of authentications and from 'site' level

get-webconfiguration /system.webServer/security/authentication/*[@enabled] -PSPath "iis:\sites\default web site"| select ItemXPath,enabled

NOTE: You can also get from other levels adjusting the value -PSPath and -Location parameter values

Case3: Get all of Anonymous authentication properties from 'server' level

$attributes = (Get-WebConfiguration /system.webServer/security/authentication/anonymousAuthentication -PSPath iis:\).attributes

$attributes | select name,value

NOTE: You can also get from other levels adjusting the value -PSPath and -Location parameter values

Case4: Change userName property for Anonymous authentication properties from 'server' level

Set-WebConfigurationproperty system.webServer/security/authentication/anonymousAuthentication -name userName -value "" -PSPath iis:\

NOTE: You can also set for other levels adjusting the value -PSPath and -Location parameter values

Related UI Task:UI Feature: "Authentication" page

33. [IIS] Configure Module elements and properties which are configured in globalModules section

Case1: List all native modules

(Get-WebConfiguration //globalmodules).collection -PSPath iis:\

Case2: Add a new native modue at the bottom index of the existing modules

Add-WebConfigurationProperty //globalmodules -name collection -value @{name='testmodule';image='c:\test.dll'} -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

New-WebModule -Name testmodule -Image c:\test.dll -Precondition "integratedMode"

Case3: Add a new native modue at the top index of the existing modules

Add-WebConfigurationProperty //globalmodules -name collection -value @{name='testmodule';image='c:\test.dll'} -at 0 -PSPath iis:\

Case4: Remove a native modue with a number index value

Remove-WebConfigurationProperty //globalmodules -name collection -at 0 -PSPath iis:\

Case5: Remove a native modue with a hashtable index value

Remove-WebConfigurationProperty //globalmodules -name collection -at @{name='testmodule';image='c:\test.dll'} -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Remove-WebModule -Name testmodule

Case6: Get the attributes for a specific module

$modules = (get-webconfiguration //globalmodules -PSPath iis:\).collection

$modules | foreach {if ($_.name -eq "cgiModule") { $_.attributes | select name, value}}

Case7: Change an attribute value for a specific module

Get-Webconfigurationproperty '//globalmodules/add[@name="CgiModule"]' -name image -PSPath iis:\

Set-Webconfigurationproperty '//globalmodules/add[@name="CgiModule"]' -name image -value %windir%\System32\inetsrv\cgi.dll -PSPath iis:\

Related UI Task:UI Feature: "Modules" page

34. [IIS] Configure Module elements and properties

Case1: Enable/Disable a native modue

Add-WebConfigurationProperty //modules -name collection -value @{name='testmodule';lockItem='true'} -at 0 -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Enable-WebModule -Name testModule

Case2: Add a new managedModule

Add-WebConfigurationProperty //modules -name collection -value @{name='newManagedModule';type='Microsoft.IIS.DemoModule'} -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

New-Managedwebmodule -name newManagedModule -Type Microsoft.IIS.DemoModule

Case3: Disable module by removing the module element from the <modules> section

Remove-WebConfigurationProperty //modules -name collection -at @{name='testmodule';lockItem='true'} -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Disable-WebModule -Name testModule

Case4: List all of enabled modules from 'server' level

(get-webconfiguration //modules -PSPath iis:\).collection -PSPath iis:\

Or, you can use other task-based cmdlet(s) instead:

Get-WebModule -PSPath iis:\ -enabled

Case5: Get the attributes for a specific module

$modules = (get-webconfiguration //modules -PSPath iis:\).collection

$modules | foreach {if ($_.name -eq "cgiModule") { $_.attributes | select name, value}}

Case6: Change an attribute value for a specific module

Get-Webconfigurationproperty '//modules/add[@name="CgiModule"]' -name lockItem -PSPath iis:\

Set-Webconfigurationproperty '//modules/add[@name="CgiModule"]' -name lockItem -value true -PSPath iis:\

Related UI Task:UI Feature:"Modules" page

35. [IIS] Change order Module elements and Revert To Inherit for a site level

Case1: Move testmodule to bottom index

# remove the target item and then re-create the item

Remove-WebConfigurationProperty //modules -name collection -at @{name='testmodule';lockItem='true'} -PSPath iis:\

Add-WebConfigurationProperty //modules -name collection -value @{name='testmodule';lockItem='true'} -PSPath iis:\

Case2: Revert To Inherit for 'site' level

Clear-WebConfiguration //modules -name -PSPath 'iis:\sites\default web site'

Related UI Task:UI Feature:"Modules" page

36. [IIS] Get the list of worker processes and requests which is running on an Application Pool

get-webrequest -Process 3644 -AppPool defaultapppool

### Get the process information of DefaultAppPoolPS IIS:\AppPools\DefaultAppPool\WorkerProcesses> dir Process State Handles Start TimeId-------- ----- ------- ----------3644 Running 310 7/24/2008 4:23:22 PM ### Call Get-WebRequest to get the list of requests using the process informationPS IIS:\AppPools\DefaultAppPool\WorkerProcesses> get-webrequest -Process 3644 -AppPool defaultapppool requestId : fe00000080000466connectionId : fe00000060000463verb : GETurl : /long.aspxsiteId : 1 ### Or, you can use GetRequsts() method:PS IIS:\AppPools\DefaultAppPool\WorkerProcesses> (get-item 3644).getrequests($null) requestId : fe00000080000469connectionId : fe00000060000463verb : GETurl : /long.aspxsiteId : 1

Related UI Task:UI Feature: "Worker Processes" page

Learning IIS Powershell Provider (Step By Step)

JeongHwan — Tue, 22 Apr 2008 21:55:00 GMT

This article is for the users who have never experienced the Windows Powershell and want to use IIS Powershell Provider.
I tried to explain the basic feature of Powershell here for you to understand the Powershell and IIS Powershell Provider together with various examples. :-)

If you don't install IIS Powershell, I'd like to recommend you to do all the IIS Powershell walkthrough.
You will install IIS Powershell provider and you will see some big picture about what you can do using IIS Powershell provider

NOTE:

1. IIS Powershell Walkthroughs:
http://learn.iis.net/page.aspx/447/managing-iis-with-the-iis-70-powershell-provider/

2. We maintain a forum in this IIS.Net web site for IIS Powershell Provider, where you can ask any questions regarding IIS Powershell:
http://forums.iis.net/1151.aspx

How to start Powershell
=======================

You can launch Powershell.exe from Start/Run menu for Windows 2008 or Start Search menu for Vista SP1.
(IIS Powershell Provider can be installed only Vista SP1 and Windows 2008, not for Vista nor Windows 2003)

Most examples will be shown with the famous Powershell prompt "PS C:\ >". So, just run the examples in order and you will understand the usage of Powershell cmdlet.
(NOTE: I tried to put some explanation with "#" mark; you don't need to type those strings)

Let's start!!!

Let's learn Powershell with what you could not in DOS world
===========================================================

#. You can create list of numbers
PS C:\> 1,2,3,4,5

Or.
PS C:\> (1..5)

#. You can create string array
PS C:\> "a","b","c"

#. You can create a variable which should be started with "$" prefix
PS C:\> $a = "My First Variable"

#. Bind your data to Powershell cmdlet using pipeline
PS C:\> 1,2,3,4,5 | write-host

#. You can echo any string with different color easily
PS C:\> 1,2,3,4,5 | write-host -ForegroundColor Green

#. You can get the actual cmdlet name of alias command
PS C:\> get-command cd

CommandType     Name                            Definition
-----------     ----                            ----------
Alias           cd                              Set-Location

PS C:\> get-command md

CommandType     Name                            Definition
-----------     ----                            ----------
Function        md                              param([string[]]$paths); New...

(NOTE: We just learned that we can use new-item, which will be used below examples, for creating a folder)

#. You can get the help document
PS C:\> New-Item -?

PS C:\> Get-help New-Item -full

#. Of course you can create directory without using pipeline
PS C:\> new-item myDir -type directory

#. You can create file with the same command with specifying different type name
PS C:\> new-item myFile -type file

#. But you can't combine string value to new-item. You will see this kind of error message
PS C:\> "myDir2" | new-item -type directory
New-Item : The input object cannot be bound because it did not contain the information required to bind all mandatory parameters: Path
At line:1 char:17
+ "abc" | new-item <<<< -type directory

#. Let's look at what happens. With the -full option of Help-Command you can learn the detail information of Parameter information of the New-Item cmdlet

<snip>
PARAMETERS
    -path <string[]>
        Specifies the path to the location of the new item. Wildcards are permi
        tted.

        Required?                    true
        Position?                    1
        Default value                String.empty
        Accept pipeline input?       true (ByPropertyName)
        Accept wildcard characters? false
<snip>

(NOTE: See the Accept pipeline input? part)

Because -path has a condition of "(ByPropertyName)", that's why you could not bind the string value via pipeline operator.
Now, it is time how to create your first object data in which you add a new property with any property names

#. You can create your new object data using new-object cmdlet
PS C:\> $a = new-object psobject

(NOTE: PSObject is the built-in class in Powershell and it is good for creating powerful data)

#. You can add a new property onto an existing object using add-member cmdlet
PS C:\> add-member -inputObject $a noteproperty path "myDir2"

#. Bind your object data to Powershell cmdlets (Now you have learned how to bind object to Powershell cmdlet!!!)
PS C:\> $a | new-item -type directory

#. If you want to control the pipeline binding more programatically, use foreach cmdlet
PS C:\> $a | new-item -type directory

VS.

PS C:\> "dir1","dir2" | foreach {new-item -path $_ -type directory}

#. Even you can pipe conditionally using if statement

PS C:\> "dir1","dir2" | foreach { if ($_ -eq "dir1") {new-item -path $_ -type directory}}

#. If statement can be replaced with where-object cmdlet

PS C:\> "dir1","dir2" | foreach { if ($_ -eq "dir1") {new-item -path $_ -type directory}}

VS.

PS C:\> "dir1","dir2" | where-object {$_ -eq "dir1"} | foreach { new-item -path $_ -type directory}

#. I'd like to remind that foreach-object and where-object requires scriptblock which is a script inside of "{" and "}", not "(" and ")". The $_ means the current item in the array of items for Pipeline passes each element at a time.

PS C:\> 1,2,3 | foreach-object { echo $_}
PS C:\> 1,2,3 | where-object { $_ -eq 1}

#. where-object and foreach-object have alias which are commonly used in Powershell

PS C:\> 1,2,3 | foreach { echo $_}
PS C:\> 1,2,3 | where { $_ -eq 1}

#. Let's learn how to add method to your custom object also
PS C:\> add-member -inputObject $a scriptmethod HellowWorld {echo "hello world!!!" }

#. Let's learn how to look my object
PS C:\> $a

PS C:\> $a | format-list

(NOTE: You won't see all the properties and methods)
It is important to know the Powershell don't show all the properties and methods by default.
But we can customize the output with creating some xml files.

#. Let's learn to list all the properties and methods which were hidden in the default output
PS C:\> $a | get-member

TypeName: System.Management.Automation.PSCustomObject

Name             MemberType   Definition
----                 ----------            ----------
Equals            Method       System.Boolean Equals(Object obj)
GetHashCode Method       System.Int32 GetHashCode()
GetType          Method       System.Type GetType()
ToString          Method       System.String ToString()
path                NoteProperty System.String path=MyDir2
HellowWord      ScriptMethod System.Object HellowWord();

#. Let's learn even the values have members
PS C:\> 1 | get-member

PS C:\> "a" | get-member

PS C:\> "a","b","c" | get-member

#. It's time to think about objects in Powershell world
In file systems, you have already a lot of files and directories. You must be curious which object type was used for them.

(NOTE: In Powershell, we call the class name of an object as "TYPE" because the object was actually implemented from a type of managed code like creating object in C#)

# Let's get the object type using the built-in method of gettype()
PS C:\> $a.gettype()

# Let's browse the root directory of C: drive

PS C:\> get-item *

PS C:\> dir

#. Let's get an existing object for a single directory in file system using get-item cmdlet
PS C:\> get-item C:\Windows

#. Let's see which object type was used for the C:\WIndows directory object using the result of get-item cmdlet by wrapping the command execution using "(" and ")"
PS C:\> (get-item c:\Windows).gettype()

IsPublic IsSerial Name                                BaseType
--------    --------    ----                                     --------
True      True      DirectoryInfo                      System.IO.FileSys...

(NOTE: Now you know it is "DirectoryInfo")

#. Let's learn how to extract Name property only
PS C:\> (get-item c:\Windows).gettype() | Select-Object Name

PS C:\> (get-item c:\Windows).gettype() | Select-Object *

#. Let's learn the select-object is not that meaningful
PS C:\> 1 | Select-Object ??? => Not meaningful
PS C:\> 1 | get-member | select name => This becomes meaningful

#. Let's learn the select-object actually returns a new object, not the original object
PS C:\> ((get-item c:\Windows).gettype() | Select-Object Name).gettype()

IsPublic IsSerial Name                                     BaseType
--------    --------     ----                                          --------
True      False     PSCustomObject                    System.Object

(NOTE: the type name is "PSCustomObject", not "DirectoryInfo" anymore)

#. Let's extract the string value of Name property
PS C:\> (((get-item c:\Windows).gettype() | Select-Object Name).gettype()).Name

More tips
=========

When I started Powershell, I felt some inconvience because I was not able to do what I used to do easily in the DOS prompt.
Here is the list of examples I'd like to share with you for your information. With this tips, you will like Powershell more because you will learn the fact that you can do almost everything you did in DOS prompt.
Of course, you should read a good Powershell book to learn more skills or tools later. :-)

#. You can change the window size and back ground color of the IIS Management Console window.
1. Click the Powershell icon which is on the left-top corner and select "Properties" context menu.
2. Enable "QuickEdit Mode" checkbutton
3. Select Layout tab and adjust the width of the "windows size" group box with your favorite number. I use 120 for that.
4. Select Colors tab and set 1, 36, 86 for Red:, Green: and Blue: which is the same setting of Powershell prompt.

#. "Set" command. I was able to use "Set" command to show enviromnet variables in DOS but not in Powershell anymore.
You can use "Get-Command" instead or "Dir env:"

#. How to use environment variable in Powershell
You can use ENV: drive. Please note that you should add $ mark unlike other drive name and you should not add "\" after the drive name)
EX.)

dir "$env:Systemdrive\windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config"
dir "$env:Systemdrive\windows\Microsoft.NET\Framework\v2.0.50727\config\web.config"
dir "$env:Systemdrive\windows\system32\inetsrv\config\applicationHost.config"
dir "$env:Systemdrive\inetpub\wwwroot\web.config"

#. You can run DOS command easily from Powershell if you don't know corresponding cmdlet yet
Ex.)
cmd /c c:\windows\system32\notepad.exe
cmd /c set

#. When you capture screen of Powershell window, you will notice the table is not aligned in your word processor or mail.
Try to use the "Courier New" font to avoid the problem

#. You can use TAB command-line completion or get-command cmdlet when you don't remember the exact cmdlet names.
If you remember part of the cmdlet name, then try to use get-command. For the example, get-command *item* will return all the cmdlemt which contains "item" in their name.

#. Use "Get-Comand *keyword* when you forget the name of a certain command name.
Ex.) "Get-Command *web*" will return all the cmdlets which name contains web

#. Use "Get-Help <cmdletname> -full" as much as possible.
For the first time, I thought it provides too much information but I realize it is not that too much information soon. Now I complains the help document is not enought for many times.

#. Use "Get-Help <cmdletname> -full" to get the related cmdlets
It is very important to enlarge your knowledge about each cmdlet. The get-help cmdlet will be your friend to let you know all the insteresting cmdlet which is directly related to the specified cmdlet.

#. Please note, the Tech Preview 1 IIS Powershell release does not have enough information for each cmdlet which you can apply for IIS: drive and its contents such as sites/applications/virtual directoriesa and apppools.
We couldn't find the solution yet. Please use IIS.Net forum to get any kind of questions because you feel the help does not that helpful for your situation.

What does it mean to install IIS Powershell Provider?
=====================================================

Powershell.EXE has built-in providers such as registry key provider.
You can get the list of the providers which are installed in your machine with Get-PsProvider cmdlet.

With IIS provider, you can read files and directories under web contents such as web sites/appplications/virtual directories and you can browse physical files and directories as well.
IIS Provider is built as one single DLL file, which name is iisprovider.dll.
When you install Powershell provider, the dll file is copied to GAC directory and the dll file is registered to Powershell environment.
Even the dll is registered, you should know that whenever you open a Powershell window, which is powershell.exe shell, you need to add the registered provider to your newly opened shell environment.

#. How to add IIS Provider

1. Execute Powershell.exe to open a new powershell window
2. Run "add-pssnapin IIsProviderSnapIn"

NOTE: Inside of IISProvider.dll, the snapin name is decided as "IIsProviderSnapIn". Snapin is another name of Powershell dll file. IISProvider.dll has the IIsProviderSnapIn snapin where IIS Provider and IIS cmdlet are implemented.
Sometimes a single snapin can contain only custom cmdlets or only custom provider without custom cmdlets.

What kinds of objects are supported in IIS Powershell Provider?
===============================================================

After installing IIS Powershell provider, you can manage all the IIS configuration system objects. So, it is important to know which kind of objects you can manipulate with IIS Powershell provider.

#. All the items under the IIS: drive are ConfigurationElement except container nodes such as IIS:\, IIS:\Sites and IIS:\AppPools
For the example, let's see the type of "Default Web Site" and "DefaultAppPool" and they were made from the type ConfigurationElement object.
PS C:\> (get-item 'iis:\sites\default web site').gettype()

IsPublic IsSerial Name                                     BaseType
--------    --------    ----                                          --------
True      False    ConfigurationElement               System.Object

PS C:\> (get-item 'iis:\apppools\defaultapppool').gettype()

IsPublic IsSerial Name                                     BaseType
--------     --------    ----                                         --------
True       False    ConfigurationElement              System.Object

#. What's the type name of container node?
For the example, let's see the type of IIS:\Sites node; it is "PSCustomObject" and it is the same for AppPools container node and the root IIS:\ as well.
PS C:\> (get-item 'IIS:\Sites').gettype()

IsPublic IsSerial Name                                     BaseType
--------    --------     ----                                         --------
True      False    PSCustomObject                     System.Object

#. Let's look at all the methods and properties of each IIS node such as Default Web Site
PS C:\> get-item 'IIS:\Sites\Default Web Site'

Name                 ID   State      Physical Path                               Bindings
----                      --   -----      -------------                                          --------
Default Web Site 1    Started    %SystemDrive%\inetpub\wwwroot http *:80:

(NOTE: As I told before, it does not show all the properties or methods)

#. Let's use Get-Member instead to see all the methods and properties
PS C:\> (get-item 'IIS:\Sites\Default Web Site') | get-member

<snip>
applicationDefaults        NoteProperty          System.Management.Automatio...
applicationPool            NoteProperty          System.String applicationPo...
bindings                   NoteProperty          System.Management.Automatio...
enabledProtocols           NoteProperty          System.String enabledProtoc...
id                         NoteProperty          System.Int64 id=1
limits                     NoteProperty          System.Management.Automatio...
logFile                    NoteProperty          System.Management.Automatio...
name                       NoteProperty          System.String name=Default ...
password                   NoteProperty          System.String password=
physicalPath               NoteProperty          System.String physicalPath=...
PSChildName                NoteProperty          System.String PSChildName=D...
PSDrive                    NoteProperty          Microsoft.IIs.PowerShell.Pr...
PSIsContainer              NoteProperty          System.Boolean PSIsContaine...
PSParentPath               NoteProperty          System.String PSParentPath=...
PSPath                     NoteProperty          System.String PSPath=IIsPro...
PSProvider                 NoteProperty          Microsoft.IIs.PowerShell.Pr...
serverAutoStart            NoteProperty          System.Boolean serverAutoSt...
traceFailedRequestsLogging NoteProperty          System.Management.Automatio...
userName                   NoteProperty          System.String userName=
virtualDirectoryDefaults   NoteProperty          System.Management.Automatio...
As I explained, Let's look at all the method and properties of each IIS node such as Default Web Site
<snip>

(NOTE: I have shown only NoteProperty properties here on purpose because they are actually used to configure IIS configurations)

#. What is the type of each property then?
For the example, let's see what is it for the Binding property of Default Web Site
PS C:\> ((get-item 'IIS:\Sites\Default Web Site').Bindings).gettype()

IsPublic IsSerial Name                                     BaseType
--------     --------    ----                                          --------
True       False    ConfigurationElement               System.Object

(NOTE: It is "ConfigurationElement" again)

#. Why all the existing object in the IIS Powershell provider are instantiated from the same type?
The answer is because IIS Provider is built on top of MWA (Microsoft Web Administration) which is used by IIS UI. The MWA provides unique object hierachy for all the configurable IIS properties and items.
TP1 IIS Powershell provider utilize it and that's why we see the same object type from all the existing IIS Powershell world objects.
Now, let's learn about the MWA object hierachy more.

#. How to get the value of physicalPath property of Default Web Site
PS C:\> (get-item 'IIS:\Sites\Default Web Site').physicalPath
%SystemDrive%\inetpub\wwwroot

(NOTE: it returns string value and it is because the physicalPath is not a ConfigurationElement object)

#. How to get the value of Bindings property of Default Web Site
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings
Collection      : {binding}
Attributes      : {}
ChildElements   : {}
ElementTagName : bindings
IsLocallyStored :
Methods         :
RawAttributes   : {}
Schema          : Microsoft.Web.Administration.ConfigurationElementSchema

(NOTE: BTW, Bindings property is shown differently considering the format of what we see for the Default Web Site which was from the same object type. It is becasue we have maintain some xml files to handle sites node)

#. How to get the properties values inside of Bindings object then?
We should follow the same way. First look at all the properties and methods of the object

PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings | get-member

<snip>
Collection NoteProperty System.Management.Automation.PSObj...
<snip>

(NOTE: In the same way, I showed only NoteProperty properties here because they are only configurable items in the IIS Powershell Provider world)

# Let's see the type of the Collection object again

PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection.gettype()

IsPublic IsSerial Name                                BaseType
--------    --------    ----                                     --------
True      True      PSObject[]                         System.Array

(NOTE: it is PSObject array,not a single PSObject object and now it is time to learn how to manipulate array object in the Powershell world)

# How to know the number of items in a certain array object?
Answer is to use Length or Count property
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection.length
1
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection.count
1

# What is the type of each entry of the array object? (You should use "[" and "]" operatoer to specify the index of array here)
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection[0].gettype()

IsPublic IsSerial Name                                BaseType
--------    --------    ----                                     --------
True      False    ConfigurationElement          System.Object

We get "ConfigurationElement" again!!! Let's see all the methods and properties of the 1st element.

PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection[0] | get-member

<snip>
bindingInformation NoteProperty System.String bindingInformation=*...
protocol NoteProperty System.String protocol=http
<snip>

(NOTE: I show only NoteProperty properties again because we can use them for modifying configuration)

# Now, let's try to get the value of bindingInformation and protocol
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection[0].bindingInformation
*:80:
PS C:\> (get-item 'IIS:\Sites\Default Web Site').Bindings.collection[0].protocol
http

Finally we reached the final leaf node, string values!!! It is a long journey right? But you can apply the same rule for all the IIS properites and you will realize this is not that complicated job soon.

Let's learn about the Filter parameter
======================================
NOTE: Filter is the 1st parameter for most of IIS cmdlets

#. Learn the fact that some Cmdlets accept XFilter parameter as well as PSPATH.
XFilter is used to specify a certain section element. In order to understand the IIS sections, you should understand the IIS configuration architecture.
In my opinion, the best way to learn the section is to use the Configration Editor of Admin Pack, which is available in the web site, www.IIS.Net.
If you go to the Configuration Editor page of Inetmgr.exe, you will see "Section:" dropdown control in UI. It shows the list of IIS Sections and you can expand them to see whole config section informations.
Because IIS Powershell provider uses the same engine on which the Configuraion Editor is based to manipulate the config sections, if you fully understand the configuration editor, you can use the IIS Powershell provider more effectively.
So, if you don't know well about IIS section informations, please try to use the configuration editor and you will learn how the IIS config system should be managed.
And each IIS Config sections should be mapped to a certain commit path.
In IIS Powershell provider, the commit path is actually considered as PSPATH, which is explained below again.
I will explain about this more with sample scripts below.

Let's learn what the PSPath means in IIS Powershell provider world
==================================================================
NOTE: PSPATH is the second parameter for most of IIS cmdlets

#. There are two types of PSPATH and they are 100% equivalent each other
If you have experienced to use AppCmd.exe, it would make sense to you. If not, it just looks complicated.
I will explain why there are two types of PSPATH here.

Type1: 'MACHINE/WEBROOT/APPHOST/iisstart.htm'
Type2: 'iis:\Sites\Default Web Site\iisstart.htm'
Type3: '..\Default Web Site' Or "."

The Type1 was used first for AppCmd.exe and the MWA world. IIS Powershell provider was invented at last. So, it had to use the same format for users.
The Type2 is a newly introduced one with IIS Powershell. It looks very similar to the File system path and most of users will like it because it is easy to use.
If Type2 is an absolute path, the Type3 is non-absolute path. You can use that kind of relative path as you do for DOS directory path.

#. For a certain case, we must use the Type1 PSPATH.
It is the case when you want to manipulate the IIS configuration settings in the web.config under %windir%\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG directory.
And the value for the PSPATH parameter should be MACHINE/WEBROOT.

Location Parameter and Metadata Parameter
=========================================
NOTE: Location and Metadata are optional parameters for most of IIS cmdlets

Finally, you need to know understand IIS config files can be configured using "Location" tag.
By default, Configuration sections will be saved without using Location information.
If you want to manipulate sections under location path and some locking attributes, you should use the location parameter and the metadata parameter as well.
I will explain about this more with sample scripts below.

#. Filter parameter value samples

1) //* => All the elements in IIS Configuration XML system
2) //*[@attributename] => All the elements which contains a certain attribute

#. Filter parameter Examples

Ex.1) In order to dump all the sections
PS C:\> get-webconfiguration //* machine/webroot/apphost | where {$_.gettype().tostring() -eq "Microsoft.Web.Administration.ConfigurationSection"} | select SectionPath | sort SectionPath

FYI, IIS Config system has three types and those types has this relationship:
Microsoft.Web.Administration.SectionGroup > Microsoft.Web.Administration.ConfigurationSection > Microsoft.Web.Administration.ConfigurationEntry

Ex.2) Dump all the sections which contains enabled attribute
PS C:\> get-webconfiguration //*[@enabled] machine/webroot/apphost

Ex.3) Dump all the sections which contains name attribute and its value should be "Default Web Site"
PS C:\> get-webconfiguration '//*[@name="Default Web Site"]' machine/webroot/apphost

Ex.4) Dump all the sections for Default Web Site using absolute path
PS C:\> get-webconfiguration '/system.applicationHost/sites/site[@name="Default Web Site" and @id=1]' machine/webroot/apphost

Ex.5) Dump all the sections for Default Web Site using "//"
PS C:\> get-webconfiguration '//site[@name="Default Web Site" and @id=1]' machine/webroot/apphost

#. Location, Metadata parameter Samples

1) Clear appSettings section under "iisstart.htm" location section
PS C:\> clear-webconfiguration /appSettings 'iis:\sites\default web site' -location iisstart.htm

2) Add an appsetting key under "iisstart.htm" location section and set overrideMode attribute with "Deny"
PS C:\> add-webconfiguration /appSettings 'iis:\sites\default web site' -value @{key="test";vale="test"} -at 0 -location iisstart.htm
PS C:\> set-webconfiguration /appSettings 'iis:\sites\default web site' -location iisstart.htm -metadata overrideMode -value Deny

3) Get the appSettings section under iisstart.htm; By this way, you can get the current metadata property values for the section as well
PS C:\> get-webconfiguration /appSettings 'iis:\sites\default web site' -location iisstart.htm | select *

#. Advanced Filter parameter Examples (FYI, I've learned this from William Moy)

Ex.1) Let's prepare the work environment
PS C:\> add-webconfiguration /appSettings 'iis:\sites\default web site' -value @{key="test";value="test"} -at 0
PS C:\> add-webconfiguration /appSettings 'iis:\sites\default web site' -value @{key="test2";value="test2"} -at 0

Ex. 2) You can get two "add" element nodes
PS C:\> get-webconfiguration /appSettings/add 'iis:\sites\default web site'

Ex. 3) You can get use [] to specify the index inside of XPATH like this and you will get 1st add element
PS C:\> get-webconfiguration /appSettings/add[0] 'iis:\sites\default web site'

Ex. 4) You can get use [@attributename="value"] to meet the specific attribute value
PS C:\> get-webconfiguration '/appSettings/add[@key="test"]' 'iis:\sites\default web site'

Ex. 5) You can even use != operator instead of "=" and you will get the other "add" element node
PS C:\> get-webconfiguration '/appSettings/add[@key!="test"]' 'iis:\sites\default web site'

Ex. 6) You can even get each property by specifying @attribute after the section path
PS IIS:\> get-webconfiguration /appSettings/add/@key 'iis:\sites\default web site' | select *

Ex. 7) You can even get all the attributes using @*
PS IIS:\> get-webconfiguration /appSettings/add/@* 'iis:\sites\default web site' | select *

Ex. 8) You can get all "site" elements with a virtual directory that starts with "C:\" string
PS C:\> get-webconfiguration "/system.applicationHost/sites/site[application/virtualDirectory[starts-with(string(@physicalPath),'C:\')]]" IIS:\

Ex. 9) You can get all "application" elements with a virtual directory that starts with "C:\" string by adjusting the location of "["
PS C:\> get-webconfiguration "/system.applicationHost/sites/site/application[virtualDirectory[starts-with(string(@physicalPath),'C:\')]]" IIS:\

Ex. 10) Get Image path information of StaticFileModule
PS C:\> get-webconfiguration "/system.webServer/globalModules/add[@name='StaticFileModule']/@image" IIS:\
%windir%\System32\inetsrv\static.dll

Ex. 11) You can get all the "add" elements which contains 'Authentication' in its name property that comes before WindowsAuthentication or BasicAuthenticationModule items
PS C:\> get-webconfiguration '/system.webServer/modules/add[@name="WindowsAuthentication"]//preceding-sibling::*[contains(string(@name),"Authentication")]' IIS:\
OR
PS C:\> get-webconfiguration '/system.webServer/modules/add[@name="BasicAuthenticationModule"]//preceding-sibling::*[contains(string(@name),"Authentication")]' IIS:\

Ex. 12) You can get all the "application" elements which contains cerain application pools. The application pools were obtained with a nested xpath query.
PS C:\> get-webconfiguration '/system.applicationHost/sites/site/application[@applicationPool=/system.applicationHost/applicationPools/add[@managedPipelineMode="0"]/@name]' IIS:\

Let's look at which kind of Powershell cmdlets exist
====================================================
Let's categorize all the cmdlets using required parameters first.
FYI, I am going to write another blog with the detail information for each cmdlet later.

#. PSPATH only
Get-item
New-Item
Set-Item
Copy-Item
Move-Item
Remove-Item
Rename-Item
Clear-Item
Get-WetItemState
Start-WebItem
Stop-WebItem

#. Filter + PSPATH
Get-WebConfigurationItem
Set-WebConfigurationItem
Add-WebConfigurationItem
Clear-WebConfigurationItem
Get-WebConfigurationItemProperty
Set-WebConfigurationItemProperty
Add-WebConfigurationItemProperty
Remove-WebConfigurationItemProperty

#. Nothing
Start-Transaction
End-Transaction

Now, let's categorize the common cmdlet names which are applicable to other provider such as File system and Registry key providers

#. Cmdlets only applicable only to IIS world
Get-WetItemState
Start-WebItem
Stop-WebItem
Get-WebConfigurationItem
Set-WebConfigurationItem
Add-WebConfigurationItem
Clear-WebConfigurationItem
Get-WebConfigurationItemProperty
Set-WebConfigurationItemProperty
Add-WebConfigurationItemProperty
Remove-WebConfigurationItemProperty

#. Cmdlets which can be used for other providers
Get-item
New-Item
Set-Item
Copy-Item
Move-Item
Remove-Item
Rename-Item
Clear-Item

References
==========

1) Learn more XPATH examples:
http://msdn2.microsoft.com/en-us/library/ms256086.aspx

2) Learn more Powershell programming knowledge by following Powershell SDK walkthrough:
http://msdn2.microsoft.com/en-us/library/ms714469.aspx

3) Powershell Home page. You can get more useful information here.
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx