Cmdlets in Lync Online that use only the global scope
Topic Last Modified: 2013-07-05
A number of Lync Online settings are available only at the global scope. This means that there is a single collection of settings that applies to all the users who are assigned to that tenant. (Each tenant has its own unique collection of global settings.) When you are using cmdlets that are limited to the global scope, the Identity parameter is optional. For example, to retrieve meeting configuration settings, you can use this command:
Get-CsMeetingConfiguration -Identity "global"
Alternatively, you can omit the Identity parameter and use this simpler command instead:
Because there is only one global collection of meeting configuration settings, the two commands return the exact same information. The Identity parameter can also be omitted when using one of the Set-Cs cmdlets. These two commands are identical:
Set-CsMeetingConfiguration -Identity "global" -AdmitAnonymousUsersByDefault $False Set-CsMeetingConfiguration -AdmitAnonymousUsersByDefault $False
The two commands are identical because, by default, Windows PowerShell will modify the global collection if you do not include the Identity parameter.
The following cmdlets operate only at the global scope:
Note that the Remove-CsVoicePolicy cmdlet is something of an anomaly. First, this cmdlet does require you to include the Identity parameter:
Remove-CsVoicePolicy -Identity "global"
Second, the Remove-CsVoicePolicy cmdlet does not actually delete the global voice policy; Lync Online does not allow you to delete global policies or configuration settings. What the cmdlet does do is enable you to reset all the properties in the global voice policy to their default values. For example, by default, the AllowCallForwarding property is set to False. However, AllowCallForwarding may have been modified, with the value now set to True. When you run the Remove-CsVoicePolicy cmdlet, the AllowCallForwarding property will revert to its default value: False. The following table summarizes this scenario:
After the global policy has been modified
After Remove-CsVoicePolicy cmdlet has been run