Return the Effective Policy Assignments for a User - Lync PowerShell - Site Home

You say you want to know which Microsoft Lync Server 2010 policies have been assigned to the user Ken Myer? Well, that’s easy enough; all you have to do is run the following command:

Get-CsUser "Ken Myer"

In return, Windows PowerShell should show you information similar to this:

VoicePolicy                       : RedmondVoicePolicy
ConferencingPolicy                :
PresencePolicy                    :
DialPlan                          :
LocationPolicy                    :
ClientPolicy                      : RedmondClientPolicy
ClientVersionPolicy               :
ArchivingPolicy                   :
PinPolicy                         : RedmondPinPolicy
ExternalAccessPolicy              :
HostedVoiceMail                   :
HostedVoicemailPolicy             :

As you can see, Ken has been assigned three different per-user policies: RedmondVoicePolicy; RedmondClientPolicy; and RedmondPinPolicy. Any other questions?

Oh, right: what about all those other policies? Take conferencing policy, for example. There’s nothing listed next to conferencing policy; does that mean Ken is under no restrictions whatsoever when it comes to conferencing?

In a word: no. With Lync Server 2010 you are always under the jurisdiction of a policy of some kind; if you haven’t been assigned a per-user conferencing policy that means that you’re either under the sway of a conferencing policy configured for your site or, if there is no such site policy, the global conferencing policy. No user account ever goes unmanaged.

So then why doesn’t anything show up next to ConferencingPolicy? Well, as it turns out, Get-CsUser only shows you per-user policies; that’s because that information is stored in Active Directory and is readily available. What the cmdlet doesn’t do is try to resolve the so-called “effective policy;” in other words, it doesn’t try to determine whether Ken’s conferencing behaviors are managed by a site policy or by a global policy. All we know is that those behaviors aren’t managed by a per-user policy.

Which simply means this: if you want to determine the effective policy assignments for a user, well, you’re going to have to do that yourself. In the case of a conferencing policy, that means determining the site where Ken Myer’s user account is homed and checking to see if there’s a conferencing policy assigned to that site. If there is, you must then report back the Identity of the site policy; if not, you need to report back the Identity of the global policy. And then you have to repeat this same process for voice policies, dial plans, client version policies, archiving policies, etc., etc.

You know, that does sound like an awful lot of work, doesn’t it? Which is why you might want to run this script instead:

$y = @()

$user = Get-CsUser $args[0]
$site = (Get-CsSite | Where-Object {$_.Pools -contains $user.RegistrarPool}).Identity

if ($user.ClientPolicy -eq $Null)
{
$x = Get-CsClientPolicy

foreach ($i in $x)
{$y += ($i.Identity)}

                if ($y -contains "site:$site")
                    {"Client Policy            : site:$site"}
                else
                   {"Client Policy            : Global policy"}
    }
else
   {"Client Policy            : " + $user.ClientPolicy}

$y = @()
if ($user.LocationPolicy -eq $Null)

{
$x = Get-CsLocationPolicy