Grant-CsConferencingPolicy

Syntax

Grant-CsConferencingPolicy
     [-PolicyName] <String>
     [-Tenant <Guid>]
     [-DomainController <Fqdn>]
     [-Identity] <UserIdParameter>
     [-PassThru]
     [-WhatIf]
     [-Confirm]
     [<CommonParameters>]

Description

Conferencing is an important part of Skype for Business Server : conferencing enables groups of users to come together online to view slides and video, share applications, exchange files, and otherwise communicate and collaborate.

It's important for administrators to maintain control over conferences and conference settings. In some cases, there might be security concerns: by default, anyone, including unauthenticated users, can participate in meetings and save any of the slides or handouts distributed during those meetings. In other cases, there might be bandwidth concerns: having a multitude of simultaneous meetings, each involving hundreds of participants and each featuring video feeds and file sharing, has the potential to cause problems with your network. In addition, there might be occasional legal concerns. For example, by default meeting participants are allowed to make annotations on shared content; however, these annotations are not saved when the meeting is archived. If your organization is required to keep a record of all electronic communication, you might need to disable annotations.

Of course, needing to manage conferencing settings is one thing; actually managing these settings is another. In Skype for Business Server conferences are managed by using conferencing policies. (In previous versions of the software, these were known as meeting policies.) As noted, conferencing policies determine the features and capabilities that can be used in a conference, including everything from whether or not the conference can include IP audio and video to the maximum number of people who can attend a meeting. Conferencing policies can be configured at the global scope, at the site scope, or at the per-user scope. This provides administrators with enormous flexibility when it comes to deciding which capabilities will be made available to which users.

When you create a site policy that policy is automatically assigned to the appropriate site at the time of creation. This is not the case with per-user policies: per-user policies are not assigned to anyone at the time they are created. Instead, you must use the Grant-CsConferencingPolicy cmdlet to explicitly assign per-user conferencing policies to a user or set of users.

Examples

-------------------------- EXAMPLE 1 --------------------------

Grant-CsConferencingPolicy -identity "Ken Myer" -PolicyName SalesConferencingPolicy

In Example 1, the Grant-CsConferencingPolicy cmdlet is used to assign the policy SalesConferencingPolicy to the user with the Identity "Ken Myer".

-------------------------- EXAMPLE 2 --------------------------

Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Grant-CsConferencingPolicy -PolicyName FinanceConferencingPolicy

In Example 2, the conferencing policy FinanceConferencingPolicy is assigned to all the users who have accounts in the Finance organizational unit. To assign the same policy to all the users in a given organizational unit (OU), the Get-CsUser cmdlet is used to retrieve all the accounts in that OU. After the user accounts have been retrieved, that information is then piped to the Grant-CsConferencingPolicy cmdlet, which assigns the FinanceConferencingPolicy policy to each user in the collection.

-------------------------- EXAMPLE 3 --------------------------

Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Grant-CsConferencingPolicy -PolicyName $Null

Example 3 represents a variation of Example 2: in this case, however, any per-user conferencing policies previously assigned to the users in the Finance OU are unassigned from these users. To do this, the command calls the Grant-CsConferencingPolicy cmdlet and specifies a null value ($Null) as the parameter value for the parameter PolicyName.

-------------------------- EXAMPLE 4 --------------------------

Get-CsUser -LdapFilter "Department=Human Resources" | Grant-CsConferencingPolicy -PolicyName HRConferencingPolicy

In Example 4, the policy HRConferencingPolicy is assigned to all the users who work in the Human Resource Departments. This is done by calling the Get-CsUser cmdlet and the LdapFilter parameter to retrieve the appropriate set of users; the parameter value "Department=Human Resources" limits the returned items to user accounts where the Department attribute has been set to "Human Resources". After the user accounts have been retrieved, that collection is piped to the Grant-CsConferencingPolicy cmdlet, which, assigns the policy HRConferencingPolicy to each user in the collection.

Parameters

-Confirm

-DomainController

-Identity

-PassThru

-PolicyName

-Tenant

-WhatIf

Inputs

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

Microsoft.Rtc.Management.AD.UserIdParameter

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

Outputs

By default, Grant-CsConferencingPolicy returns no objects or values. However, if you include the PassThru parameter, the cmdlet will return instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSUserOrAppContact object.

System.Object

By default, the Grant-CsConferencingPolicy cmdlet returns no objects or values. However, if you include the PassThru parameter, the cmdlet will return instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSUserOrAppContact object.

Related Links

• Get-CsConferencingPolicy
• New-CsConferencingPolicy
• Remove-CsConferencingPolicy
• Set-CsConferencingPolicy