Parameters

Lync Server 2010 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 a problem if you are using a phone that does not have an alphanumeric keypad. Because of that, Lync Server 2010 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.

This is true, however, only if the user's PIN is unlocked. If a PIN has been locked (either because the user repeatedly failed to log on or because an administrator explicitly locked the PIN), the user will not be able to access the system or join a conference by using PIN authentication. (However, that user will still be able to use an application such as Microsoft Lync 2010 to log on to the system by supplying a user name and password.) If a PIN has been locked, there is only one way to restore the user's ability to access the system by using PIN authentication: the locked PIN must be unlocked by an administrator. This can be done by using the Unlock-CsClientPin cmdlet.

Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Lync Server 2010. That means that you will not be able to run Unlock-CsClientPin 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 the Standard Edition server itself.) To run Unlock-CsClientPin 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 Unlock-CsClientPin 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 "Unlock-CsClientPin"}

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

Unlock-CsClientPin does not return a value or object. Instead, the cmdlet configures one or more instances of the Microsoft.Rtc.Management.UserPinService.PinInfoDetails object.

-------------------------- Example 1 ------------------------

	Copy Code
Unlock-CsClientPin -Identity "litwareinc\kenmyer"

In Example 1, Unlock-CsClientPin is used to unlock the PIN belonging to the user litwareinc\kenmyer.

-------------------------- Example 2 ------------------------

	Copy Code
Get-CsUser | Get-CsClientPinInfo | Where-Object {$_.IsLockedOut -eq $True} | Unlock-CsClientPin

In the preceding example, Unlock-CsClientPin is used to unlock all the PINs that are currently locked. To do this, Get-CsUser is first used to return a collection of all the users who have been enabled for Lync Server 2010. That collection is then piped to Get-CsClientPinInfo, which is used in conjunction with the Where-Object cmdlet to select only those users where the IsLockedOut property is equal to (-eq) to True ($True).

The resulting filtered collection is then piped to Unlock-CsClientPin, which unlocks the PIN for each user whose PIN was previously locked.

Other Resources