EXAMPLE 1

The command shown in Example 1 returns a collection of all the archiving configuration settings in use in your organization.

	Copy Code
Get-CsArchivingConfiguration

EXAMPLE 2

In Example 2, the Identity parameter is used to limit the returned collection of archiving configuration settings to those settings that have the Identity site:Redmond.

	Copy Code
Get-CsArchivingConfiguration -Identity site:Redmond

EXAMPLE 3

In Example 3, the Filter parameter is used to limit the returned collection of archiving configuration settings to settings that have been configured at the site scope. The parameter value "site:*" limits the returned items to those that have an Identity that starts with the string value "site:".

	Copy Code
Get-CsArchivingConfiguration -Filter site:*

EXAMPLE 4

This example uses the Get-CsArchivingConfiguration cmdlet to return a collection of all the archiving configuration settings that have been enabled for use in your organization. To do that, the command first calls the Get-CsArchivingConfiguration cmdlet without any parameters in order to return a collection of all your archiving configuration settings. That collection is then piped to the Where-Object cmdlet, which applies a filter that limits the returned data to those collections where the EnableArchiving property is not equal to "None". If EnableArchiving is set to "None", archiving has been disabled. If this property is set to any other value (either "IMOnly" or "ImAndWebConf") that means that archiving has been enabled.

	Copy Code
Get-CsArchivingConfiguration | Where-Object {$_.EnableArchiving -ne "None"}

Many organizations find it useful to keep a transcript of all the IM sessions carried out by their users (or a selected subset of users). For other organizations, it’s mandatory to keep such transcripts. For example, many organizations in the financial world are required by law to keep copies of all their electronic communications.

Lync Server gives you flexibility when it comes to archiving IM and web conferencing sessions. If you have deployed Archiving Server, you can use the various CsArchivingConfiguration cmdlets to enable and disable instant message archiving and to manage your archiving database. You can also suspend IM should archiving fail; this helps to ensure that you keep a record of all your electronic communications.

In order to archive IM sessions, you must set up at least one Archiving Server. After the Archiving Server is set up, you must perform two additional steps. First, you need to enable archiving at the appropriate scope (for details, see the Set-CsArchivingConfiguration cmdlet help topic). This might be the global scope; however, you can also configure custom archiving settings for different sites.

Second, you must use archiving policies to indicate which users will have their IM sessions archived. What happens if you enable archiving but do not assign any users a policy that specifies that their IM sessions should be archived? Literally, nothing happens: IM sessions will not be archived unless a policy is in force that requires IM sessions to be archived.

With the Get-CsArchivingConfiguration cmdlet, you can determine how IM session archiving has been configured in your organization.

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

None. The Get-CsArchivingConfiguration cmdlet does not accept pipelined input.

The Get-CsArchivingConfiguration cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.Archiving.ArchivingSettings object.