EXAMPLE 1

Example 1 returns PIN information for all the users who have been enabled for Lync Server. To do this, the command first calls the Get-CsUser cmdlet to return all users who have been enabled for Lync Server. That collection is piped to the Get-CsClientPinInfo cmdlet, which displays PIN information for each user in the collection.

	Copy Code
Get-CsUser | Get-CsClientPinInfo

EXAMPLE 2

In Example 2, the Get-CsClientPinInfo cmdlet is used to display PIN information for a single user: the user with the Identity litwareinc\kenmyer.

	Copy Code
Get-CsClientPinInfo -Identity "litwareinc\kenmyer"

EXAMPLE 3

Example 3 returns PIN information for all the users with accounts in the Finance organizational unit (OU). To do this, the Get-CsUser cmdlet and the OU parameter are used to return a collection of all the users in the Finance OU. That collection is then piped to the Get-CsClientPinInfo cmdlet, which displays PIN information for each user in the collection.

	Copy Code
Get-CsUser -OU "OU=Finance,DC=litwareinc,DC=com" | Get-CsClientPinInfo

EXAMPLE 4

The command shown in Example 4 displays PIN information for all the Managers in the organization. To retrieve a collection of all the Managers, the command uses the Get-CsUser cmdlet and the LdapFilter parameter; the filter value "Title=Manager" limits the returned collection to users who have "Manager" as their job title. The Get-CsClientPinInfo cmdlet is then used to display PIN information for each of these users.

	Copy Code
Get-CsUser -LdapFilter "Title=Manager" | Get-CsClientPinInfo

Lync Server enables users to connect to the system or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be an issue if you are using a phone that does not have an alphanumeric keypad. Because of that, Lync Server enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password.

Administrators can retrieve the PIN settings for a user, or a group of users, by running the Get-CsClientPinInfo cmdlet. Note that there is no way for an administrator to retrieve the PIN that has been assigned to a user. If a user forgets his or her PIN, that user will not be able to use PIN authentication to access the system until an administrator has assigned them a new PIN or the user has obtained a new PIN from the Dial-In Conferencing webpage.

Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Lync Server. That means that you will not be able to run the Get-CsClientPinInfo cmdlet from a remote instance of Windows PowerShell; that’s because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on Standard Edition server.) To run the Get-CsClientPinInfo cmdlet remotely against a Standard Edition server you will need to manually enable the firewall exceptions for SQL Server Express.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsClientPinInfo cmdlet locally: RTCUniversalServerAdmins. 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-CsClientPinInfo"}

String value or Microsoft.Rtc.Management.ADConnect.Schema.ADUser object. The Get-CsClientPinInfo cmdlet accepts pipelined input of string values representing the Identity of a user account. The cmdlet also accepts pipelined input of user objects.

The Get-CsClientPinInfo cmdlet returns one or more instances of the Microsoft.Rtc.Management.UserPinService.PinInfoDetails object.