Edit

Get-IISConfigCollectionElement

  • Reference
Module:
IISAdministration

Gets a configuration element object from an IIS configuration collection.

Syntax

Get-IISConfigCollectionElement
   [-ConfigCollection] <ConfigurationElementCollection>
   [[-ConfigAttribute] <Hashtable>]
   [<CommonParameters>]

Description

The Get-IISConfigCollectionElement cmdlet gets a ConfigurationElement object that is part of a given ConfigurationCollection. The returned element then can be used in further cmdlets that expect a ConfigurationElement.

Examples

Example 1: Get a configuration element for the default web site by passing the collection through a pipeline

PS C:\> Get-IISConfigSection -SectionPath "system.applicationHost/sites" | Get-IISConfigCollection | Get-IISConfigCollectionElement -ConfigAttribute @{"name"="Default Web Site"}

This command gets a configuration element for the default web site by passing the collection through a pipeline.

Example 2: Get a configuration element using a configuration collection as a parameter

PS C:\> $SiteCollection = Get-IISConfigSection -SectionPath "system.applicationHost/sites" | Get-IISConfigCollection
Get-IISConfigCollectionElement -ConfigCollection $SiteCollection -ConfigAttribute @{"name"="Default Web Site"}

This command gets a configuration element for the default web site and then stores the element into variable $SiteCollection.

Parameters

-ConfigAttribute

Specifies a hashtable of the attributes for the configuration element to be inserted. The cmdlet will fail if any required attributes are omitted from this table.

Type:Hashtable
Position:3
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False

-ConfigCollection

Specifies the ConfigurationCollection object for which the collection elements will be returned. If a ConfigurationCollection is previously obtained and assigned to a variable, you cannot pass it to this cmdlet through the pipeline because the pipeline engine will try to enumerate, passing ConfigurationElement objects instead. Try either passing the whole Get-IISConfigCollection cmdlet into the pipeline or use it as a parameter for correct results.

Type:ConfigurationElementCollection
Position:1
Default value:None
Required:True
Accept pipeline input:True
Accept wildcard characters:False

Inputs

Microsoft.Web.Administration.ConfigurationElementCollection, System.Collections.Hashtable

Outputs

ConfigurationElement