EXAMPLE 1

The command shown in Example 1 creates a new collection of privacy configuration settings that will be applied to the Redmond site (-Identity site:Redmond). The new settings enable privacy mode; this is done by adding the EnablePrivacyMode parameter and setting the parameter value to True. Note that this command will fail if the Redmond site already has a collection of privacy settings.

	Copy Code
New-CsPrivacyConfiguration -Identity site:Redmond -EnablePrivacyMode $True

EXAMPLE 2

Example 2 demonstrates how you can use the InMemory parameter to create a new collection of privacy configuration settings that initially exist only in memory. To do this, the New-CsPrivacyConfiguration cmdlet is called along with the Identity and InMemory parameters; the resulting object is stored in a variable named $x. At this point, the privacy settings exist only in memory; if you run the Get-CsPrivacyConfiguration cmdlet you will not see a listing for site:Redmond.

In the second command, the value of the EnablePrivacyMode property is set to True. Finally, the third command uses the Set-CsPrivacyConfiguration cmdlet to transform this virtual collection of privacy settings into an actual collection of settings applied to the Redmond site. Calling the Set-CsPrivacyConfiguration cmdlet is critical: if you fail to call this cmdlet then your new privacy settings will not be applied to the Redmond site, and will disappear when you end your Windows PowerShell session or delete the variable $x

	Copy Code
$x = New-CsPrivacyConfiguration -Identity site:Redmond -InMemory $x.EnablePrivacyMode = $True Set-CsPrivacyConfiguration -Instance $x

Lync Server gives users the opportunity to share a wealth of presence information with other people: they can publish a photograph of themselves; they can provide detailed location information; they can have presence information automatically made available to everyone in the organization (as opposed to having this information available only to people on their Contacts list).

Some users will welcome the opportunity to make this information available to their colleagues; other users might be more reluctant to share this data. (For example, many people might be hesitant about having their photo included in their presence data.) As a general rule, users have control over what information they will (or will not) share; for example, users can select or clear a check box in order to control whether or not their location information is shared with others. In addition, the privacy configuration cmdlets enable administrators to manage privacy settings for their users. In some cases, administrators can enable or disable settings; for example, if the property AutoInitiateContacts is set to True, then team members will automatically be added to each user’s Contacts list; if set to False, team members will not be automatically be added to each user’s Contacts list.

In other cases, administrators can configure the default values in Lync while still giving users the right to change these values. For example, by default location data is published for users, although users do have the right to stop location publication. By setting the PublishLocationDataByDefault property to False, administrators can change this behavior: in that case, location data will not be published by default, although users will still have the right to publish this data if they choose.

Privacy configuration settings can be applied at the global scope, the site scope, and at the service scope (albeit only for the User Server service). The New-CsPrivacyConfiguration cmdlet enables you to create new privacy configuration settings to be applied to a site or service. (New collections cannot be created at the global scope.) Note that each individual site or service can have, at most, a single collection of privacy configuration settings: if you try to create a new collection for the Redmond site and that site already has a collection of privacy settings then your command will fail.

Who can run this cmdlet: By default, members of the following groups are authorized to run the New-CsPrivacyConfiguration cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "New-CsPrivacyConfiguration"}

None. The New-CsPrivacyConfiguration cmdlet does not accept pipelined input.

The New-CsPrivacyConfiguration cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.PrivacyConfiguration object.