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.

As a security measure, Lync Server 2010 enables you to lock a user’s PIN. When a PIN is locked, the user will no longer be able to use that PIN to access the system or join a conference. (However, that user will still be able to access the system and join conferences by using an application such as Microsoft Lync 2010 and by supplying a user name and password.) After a PIN has been locked, the only way to restore the PIN (and the user's access privileges) is for an administrator to unlock the PIN. This can be done by using the Unlock-CsClientPin cmdlet.

Lock-CsClientPin enables administrators to temporarily disable the ability of a user to access the system by using PIN authentication. PINs can also be locked by the system: if a user repeatedly fails to log on to the system, their PIN will automatically be locked and, again, will require unlocking by an administrator.

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 Lock-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 Lock-CsClientPin remotely 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 Lock-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 "Lock-CsClientPin"}

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

Lock-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
Lock-CsClientPin -Identity "kenmyer@litwareinc.com"

In Example 1, Lock-CsClientPin is used to lock the PIN belonging to the user kenmyer@litwareinc.com.

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

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

The preceding command uses Lock-CsClientPin to lock the PINs for all users who currently have a PIN assigned to them. This is done by using Get-CsUser to return a collection of all the users who have been enabled for Lync Server 2010. That collection is piped to Get-CsClientPinInfo, which is used, in conjunction with the Where-Object cmdlet, to return a collection of users where the IsPinSet property is equal to True. That filtered collection is then piped to Lock-CsClientPin, which locks the PIN for each user in the collection.

-------------------------- Example 3 ------------------------

	Copy Code
Get-CsUser | Get-CsClientPinInfo | Where-Object {$_.PinExpirationTime -lt (Get-Date)} | Lock-CsClientPin

In Example 3, Lock-CsClientPin is used to lock the PINs for all the users who have expired PINs. To carry out this task, Get-CsUser is first called in order to return a collection of all the users who have been enabled for Lync Server 2010. This collection is then piped to Get-CsClientPinInfo, which is used, in conjunction with the Where-Object cmdlet, to limit the collection to users who have expired PINs. To determine which users have expired PINs, the Where-Object cmdlet checks for accounts where the PinExpirationTime property (which indicates the date that the PIN number expires) is less than the current date. (The current date is retrieved using the Get-Date cmdlet.) If the expiration date (for example, September 1, 2010) is less than the current date (for example, September 2, 2010), that means that the PIN has expired. After that, Lock-CsClientPin is used to lock each of the expired PINs.

Other Resources