Assigns a conferencing policy at the per-user scope. Conferencing policies determine the features and capabilities that can be used in a Web conference; this includes everything from whether or not the meeting can include IP audio and video to the maximum number of people who can attend a meeting.
Syntax
Grant-CsConferencingPolicy -Identity <UserIdParameter> [-PolicyName <String>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-PassThru <SwitchParameter>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Identity |
Required |
User ID parameter |
Indicates the Identity of the user account the policy should be assigned to. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user's Universal Principal Name; 3) the user's domain name and logon name, in the form domain\logon (e.g., litwareinc\kenmyer); and, 4_ the user's Active Directory display name (for example, Ken Myer). Note that the SamAccountName cannot be used as an identity; that's because SamAccountNames are not necessarily unique in a forest. Note that you can use the asterisk (*) wildcard character when specifying the user Identity. For example, the Identity "* Smith" would return all the users with a display name that ends with the string value " Smith". |
|
PolicyName |
Required |
String |
"Name" of the policy to be assigned. The PolicyName is simply the policy Identity minus the policy scope (the tag: prefix). For example, a policy with the Identity tag:Redmond has a PolicyName equal to Redmond; a policy with the Identity tag:RedmondConferencingPolicy has a PolicyName equal to RedmondConferencingPolicy. To assign the global policy to a user, set the -PolicyName parameter to $Null when calling Grant-CsConferencingPolicy. |
|
DomainController |
Optional |
String |
Enables you to specify the full qualified domain name of a domain controller to be contacted when assigning the new policy. If this parameter is not specified then Grant-CsConferencingPolicy will contact the first available domain controller. |
|
PassThru |
Optional |
Switch Parameter |
Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsConferencingPolicy cmdlet does not pass objects through the pipeline. |
|
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
|
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
Conferencing is an important part of Microsoft Communications Server 2010: conferencing enables groups of users (as few as 2 people to as many as 1,000 people) to come together online to view slides and video, share applications, exchange files, and otherwise communicate and collaborate.
Needless to say, 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 wreak havoc on 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, wanting to manage conferencing settings is one thing; how you manage these settings is another. In Communications Server 2010 conferences are managed 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 Web 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 Grant-CsConferencingPolicy to explicitly assign per-user conferencing policies to a user or set of users.
Return Types
Grant-CsConferencingPolicy does not return a value or object. Instead, the cmdlet is used to assign instances of the Microsoft.Rtc.Management.WriteableConfig.Policy.Meeting.MeetingPolicy object to a user or group of users.
Examples
-------------------------- Example 1 --------------------------
 Copy Code |
|
|---|---|
Grant-CsConferencingPolicy -identity "Ken Myer" -PolicyName SalesConferencingPolicy |
|
In Example 1, Grant-CsConferencingPolicy is used to assign the policy SalesConferencingPolicy to the user with the Identity "Ken Myer".
-------------------------- Example 2 --------------------------
| Copy Code |
|
|---|---|
Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Grant-CsConferencingPolicy -PolicyName FinanceConferencingPolicy |
|
In the preceding example, 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 OU, the Get-CsUser cmdlet is used to retrieve all the accounts in that OU. (Note the syntax used to specify the OU.) After all the user accounts have been retrieved that information is then piped to the Grant-CsConferencingPolicy cmdlet, which proceeds to assign the FinanceConferencingPolicy policy to each user in the collection.
-------------------------- Example 3 --------------------------
| Copy Code |
|
|---|---|
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, the global conferencing policy is assigned to all the users in the Finance OU. To assign the global conferencing policy to users previously assigned a per-user policy, simply call Grant-CsConferencingPolicy and specify a null value ($Null) as the parameter value for the parameter –PolicyName.
-------------------------- Example 4 --------------------------
| Copy Code |
|
|---|---|
Get-CsUser -LDAPFilter "Department=Human Resources" | Grant-CsConferencingPolicy -PolicyName HRConferencingPolicy |
|
In the preceding command, the policy HRConferencingPolicy is assigned to all the users who work in the Human Resource Departments. To do this, Get-CsUser and the -LDAPFilter parameter are first called to retrieve the appropriate set of users; the parameter value "Department=Human Resources" limits the returned items to accounts where the Department attribute has been set to "Human Resources". After the user accounts have been retrieved the entire collection is piped to Grant-CsConferencingPolicy, which, in turn, assigns the policy HRConferencingPolicy to each user in the collection.