Lync Provisioning

Question

I need to be able to change other settings related to the users that get provisioned in Lync. Specifically:
Conferencing Policy
PIN Policy
External Access Policy
Archiving Policy
Mobility Policy
Persistent Chat Policy.

I currently have this automated via a script that evaluates group membership and sets the properties via powershell. The issue I have with this script is it only runs as a scheduled task as a logged in user. I would like to move this to adaxes, but it looks like these options are not available via the SDK.

Is this something that can be accomplished?

Answer 1

Hello,

Currently, Adaxes ADSI API doesn't support assigning Lync Policies, however you can still use your script. To execute the script automatically as a part of the user provisioning process, you need to add the script to the Business Rule that you use for provisioning users. For this purpose, you need to use the Run a program or PowerShell script action that executes the script.

For information on how to add an action to a Business Rule, see Modifying Business Rule Actions And Conditions.

In your script, you need to create a remote session to your Lync Server before you can call Lync management cmdlets, for example:

$lyncServer = "lyncserver.domain.com" # TODO: Modify me

$sessionOptions = New-PSSessionOption -SkipRevocationCheck -SkipCACheck -SkipCNCheck
$session = New-PSSession -ConnectionUri https://$lyncServer/ocspowershell `
    -SessionOption $sessionOptions -Authentication NegotiateWithImplicitCredential

Import-PSSession -session $session

Grant-CsConferencingPolicy -identity "%userPrincipalName%" -PolicyName MyConferencingPolicy # Assign a Conferencing Policy
Grant-CsPinPolicy -Identity "%userPrincipalName%" -PolicyName MyPinPolicy # Assign a PIN Policy
Grant-CsExternalAccessPolicy -Identity "%userPrincipalName%" -PolicyName MyAccessPolicy # Assign an External Access Policy
Grant-CsArchivingPolicy -Identity "%userPrincipalName%" -PolicyName MyArchivingPolicy # Assign an Archiving Policy
Grant-CsMobilityPolicy -Identity "%userPrincipalName%" -PolicyName MyMobilityPolicy # Assign a Mobility Policy
Grant-CsPersistentChatPolicy -Identity "%userPrincipalName%" -PolicyName MyPersistentChatPolicy # Assign a Persistent Chat Policy

Remove-PSSession -Session $session

In the script, $lyncServer specifies the fully qualified domain name (FQDN) of your Lync Server.

If you need more help with adapting your script to use with a Business Rule, do not hesitate to ask.

Comments

Thanks!

Works perfectly. We actually have different levels of Lync access based on the policies specified in this script. If anyone else is trying to accomplish something similar, I'm using a value stored in a custom attribute to be evaluated by business rules on user create and on user update.