Parameters

Many organizations find it useful to keep an archive of all of the IM sessions that their users take part in; other organizations are legally required to keep such an archive. In order to archive IM sessions with Lync Server 2010, you must perform two steps. First, you need to enable archiving at the global and/or the site scope by using the Set-CsArchivingConfiguration cmdlet. This gives you the ability to archive IM sessions; however, it does not automatically begin archiving those sessions.

Instead, and to actually save transcripts of your IM sessions, you must complete step 2: create one or more archiving policies. These policies determine which users will have their IM sessions recorded, in addition to which type of IM sessions (internal and/or external) will be archived. Internal IM sessions are sessions where all the participants are authenticated users who have Active Directory accounts within your organization; external IM sessions are sessions where at least one participant is an unauthenticated user who does not have an Active Directory account within your organization. You can choose to archive only internal sessions, only external sessions, or both internal and external sessions.

Archiving policies can be assigned to the global scope or to the site scope. In addition, these policies can be assigned to the per-user scope and then applied to a specific user or a specific set of users. For example, suppose your global policy archives only internal IM sessions for all of your users. In that case, you might create a second policy, one that archives both internal and external sessions and apply that policy only to your sales staff. Because per-user policies take precedence over global and site policies, members of the sales staff will have all their IM sessions archived. Other users (users who are not part of the sales department and are not affected by the sales policy) will have only their internal IM sessions archived.

The Remove-CsArchivingPolicy cmdlet enables you to delete an archiving policy that has been created for use in your organization. If you delete a per-user policy, all of the users who have been assigned that policy will automatically fall under the jurisdiction of the relevant site policy. If there is no site policy, then those users will be governed by the global policy. If you remove a site policy, users who were affected by that policy will automatically fall under the jurisdiction of the global policy.

Note that you can also run Remove-CsArchivingPolicy against the global policy; however, the global policy cannot be removed. Instead, running Remove-CsArchivingPolicy against the global policy causes all the properties in that policy to be reset to their default values; that means that neither internal nor external IM sessions will be archived. That’s because the default value for both these properties (ArchiveInternal and ArchiveExternal) is False.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsArchivingPolicy 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 "Remove-CsArchivingPolicy"}

Microsoft.Rtc.Management.WritableConfig.Policy.IM.IMArchivingPolicy object. Remove-CsArchivingPolicy accepts pipelined input of archiving policy objects.

Remove-CsArchivingPolicy does not return a value or object. Instead, the cmdlet removes instances of the Microsoft.Rtc.Management.WritableConfig.Policy.IM.IMArchivingPolicy object.

-------------------------- Example 1 --------------------------

	Copy Code
Remove-CsArchivingPolicy -Identity site:Redmond

In the preceding example, Remove-CsArchivingPolicy is used to delete the policy with the Identity site:Redmond. Note that, when a policy configured at the site scope is deleted, users previously managed by the site policy will automatically be governed by the global archiving policy instead.

-------------------------- Example 2 --------------------------

	Copy Code
Get-CsArchivingPolicy -Filter site:* | Remove-CsArchivingPolicy

In Example 2, all of the archiving policies that have been configured at the site scope are removed. This is done by using Get-CsArchivingPolicy and the Filter parameter to retrieve a collection of all the archiving policies assigned at the site scope. This is done by using the filter value "site:*", which instructs Get-CsArchivingPolicy to return only those policies that have an Identity that begins with the string value "site:". After the collection has been returned, the data is piped to Remove-CsArchivingPolicy, which deletes all the policies in the collection.

-------------------------- Example 3 --------------------------

	Copy Code
Get-CsArchivingPolicy | Where-Object {$_.ArchiveExternal -eq $False} | Remove-CsArchivingPolicy

The preceding command deletes all the archiving policies where the ArchiveExternal property is set to False. To do this, Get-CsArchivingPolicy is first used to return a collection of all the archiving policies configured for use in the organization. That collection is then piped to the Where-Object cmdlet, which picks out those policies where the ArchiveExternal property is equal to False. The filtered collection is then passed to Remove-CsArchivingPolicy, which deletes each policy in the collection.

Other Resources