Topic Last Modified: 2012-09-24
A per-user policy can only impact individual users, groups, and contact objects. To deploy a per-user policy, you must explicitly assign the policy to one or more users, groups, or contact objects. For details, see Assign a Per-User Hosted Voice Mail Policy.
For details about working with per-user hosted voice mail policies, see the Lync Server Management Shell documentation for the following cmdlets:
To create a per-user hosted voice mail policy
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.
Run the New-CsHostedVoicemailPolicy cmdlet to create the policy. For example, run:
New-CsHostedVoicemailPolicy -Identity ExRedmond -Destination ExUM.fabrikam.com -Description "Hosted voice mail policy for Redmond users." -Organization "corp1.litwareinc.com, corp2.litwareinc.com"
The previous example creates a hosted voice mail policy with per-user scope, and sets the following parameters:
Identity specifies a unique identifier for the policy, which includes the scope. For a policy with per-user scope, this parameter value is specified as a simple string, for example, ExRedmond.
Destination specifies the fully qualified domain name (FQDN) of the hosted Exchange UM service. This parameter is optional, but if you attempt to enable a user for hosted voice mail and the user’s assigned policy does not have a Destination value, the enable will fail.
Description provides optional descriptive information about the policy.
Organization specifies a comma-separated list of the Exchange tenants that home Lync Server 2013 users. Each tenant must be specified as the FQDN of that tenant on the hosted Exchange UM service.