EXAMPLE 1

Example 1 retrieves information for all your Lync Server sites.

	Copy Code
Get-CsSite

EXAMPLE 2

In Example 2, information is returned for a single site: the site with the Identity Redmond.

	Copy Code
Get-CsSite -Identity "Redmond"

EXAMPLE 3

The command shown in Example 3 returns information for your central site. To carry out this task, the command first calls the Get-CsSite cmdlet in order to return a collection of all the sites configured for use in your organization. This collection is then piped to the Where-Object cmdlet, which picks out the one site where the SiteType property is equal to "CentralSite".

	Copy Code
Get-CsSite | Where-Object {$_.SiteType -eq "CentralSite"}

EXAMPLE 4

Example 4 displays the list of pools found in the Redmond site. To do this, the command first retrieves complete information for the Redmond site, and then pipes that data to the Select-Object cmdlet. In turn, the Select-Object cmdlet uses the ExpandProperty parameter to "expand" the value of the Pools property. Expanding a property value means that all the values stored in that property will be displayed on the screen in an easy-to-read format.

	Copy Code
Get-CsSite -Identity "Redmond" | Select-Object -ExpandProperty Pools

Lync Server 2010 introduced a new concept to the Lync Server topology: sites. Sites (which should not be confused with Active Directory sites or Microsoft Exchange Server sites) are a collection of Lync Server pools and servers that are typically organized according to geography and network bandwidth. For example, if all your computers in Redmond are located on the same local area network with high-speed, low-latency connections, you might designate a Redmond site that encompasses those computers. If your computers in Dublin are located on their own local area network, and share high-speed, low-latency connections, then you might create a separate Dublin site as well. Sites play a key role in Lync Server management: most policies and settings can be configured at the site scope, making it easy to do such things as apply one set of dial plans to users in Redmond and a completely different set of dial plans to users in Dublin.

The Get-CsSite cmdlet enables you to return information about all the sites in your organization, including information about the pools that make up each of those sites.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsSite cmdlet locally: RTCUniversalUserAdmins, RTCUniversalServerAdmins, RTCUniversalReadOnlyAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsSite"}

None. The Get-CsSite cmdlllettt does not accept pipelined input.

The Get-CsSite cmdlet returns instances of the Microsoft.Rtc.Management.Deploy.Internal.Site+CentralSite object.