EXAMPLE 1

In Example 1, the user litwareinc\kenmyer is assigned a new auto-generated PIN. To assign an auto-generated PIN, leave off the Pin parameter when calling the Set-CsClientPin cmdlet. After the command completes, the new PIN assigned to Ken Myer will be displayed on the screen, and that information can then be relayed to the user.

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

EXAMPLE 2

The command in Example 2 assigns the PIN 18723834 to the user litwareinc\kenmyer. You can assign a specific PIN by using the Pin parameter followed by the number to be assigned.

	Copy Code
Set-CsClientPin -Identity "litwareinc\kenmyer" -Pin 18723834

EXAMPLE 3

Example 3 shows how you can auto-assign new PINs to all the users in a given Active Directory organizational unit (OU). To do this, the Get-CsUser cmdlet is used along with the OU parameter to return a collection of all the users who have accounts in the Finance OU. That collection is then piped to the Set-CsClientPin cmdlet, which generates a new PIN for each user in the collection.

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

EXAMPLE 4

The command shown in Example 4 assigns a new PIN to all the users who do not currently have a PIN assigned to them. To accomplish this task, the Get-CsUser cmdlet is used to return a collection of all the users who have been enabled for Lync Server. That collection is then piped to the Get-CsClientPin cmdlet and the Where-Object cmdlet; these two cmdlets are used to select only those users where the IsPinSet property is equal to False. The resulting collection, which contains only users who do not have a PIN, is then piped to the Set-CsClientPin cmdlet, which auto-generates a PIN for each user in the collection.

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

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 a problem 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.

Users are not assigned a PIN when they are enabled for Lync Server; that means that, by default, users cannot access the system by using PIN authentication. Users can obtain a PIN from the Dial-In Conferencing webpage; alternatively, administrators can assign each user a PIN by using the Set-CsClientPin cmdlet. With the Set-CsClientPin cmdlet you can either assign a user a specific PIN or you can allow Lync Server to generate a PIN for you. To auto-generate a PIN, simply omit the PIN parameter when calling the Set-CsClientPin cmdlet. If you do that, a new PIN will be generated, and the user’s Identity and his or her new PIN will be displayed on the screen when the command completes.

Note that the PINs you explicitly assign must meet the conditions specified in the PIN authentication policy governing the user in question; for example, the PIN must have at least as many digits as specified by the MinPasswordLength property. Also note that PINs can contain only numbers; letters or other non-numeric characters are not allowed.

When you set a client PIN using the Set-CsClientPin cmdlet, the PIN history count is not enforced. For example, suppose a user has a PIN number of 12345 and their client PIN policy prevents them from immediately reusing the same PIN number. If that user tries to renew his or her client PIN using the Dial-In Conferencing Web page, any attempt to reuse the same PIN number (12345) will be rejected. However, by using the Set-CsClientPin cmdlet an administrator can issue that user the PIN 12345. That’s because the Set-CsClientPin cmdlet is not bound by the PIN policy history count.

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 Set-CsClientPin 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 the Standard Edition server itself.) To run the Set-CsClientPin 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 Set-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 "Set-CsClientPin"}

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

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