Export (0) Print
Expand All

Export-JournalRuleCollection

Applies to: Exchange Server 2010

Topic Last Modified: 2011-03-19

Use the Export-JournalRuleCollection cmdlet to export journal rules to an XML file.


Export-JournalRuleCollection [-Identity <RuleIdParameter>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-ExportLegacyRules <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]

Parameter Required Type Description

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that retrieves data from Active Directory.

ExportLegacyRules

Optional

System.Management.Automation.SwitchParameter

The ExportLegacyRules switch specifies whether to export Exchange 2007 journal rules.

Identity

Optional

Microsoft.Exchange.MessagingPolicies.Rules.Tasks.RuleIdParameter

The Identity parameter specifies the name of a journal rule.

Organization

Optional

Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter

The Organization parameter is reserved for internal Microsoft use.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

You can use the Export-JournalRuleCollection cmdlet to export journal rules from a Microsoft Exchange Server 2010 organization, or export legacy journal rules from Exchange Server 2007 and import them to Exchange 2010 using the Import-JournalRuleCollection cmdlet.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Journaling" entry in the Messaging Policy and Compliance Permissions topic.

Error Description

 

This example exports journal rules on an Exchange 2010 Hub Transport server in a two-step process. In the first step, the Export-JournalRuleCollection cmdlet is used to export journal rules to the array $file.

$file = Export-JournalRuleCollection

In the second step, the Set-Content cmdlet is used to save the exported data to the XML file JournalRules.xml.

Set-Content -Path "C:\MyDocs\JournalRules.xml" -Value $file.FileData -Encoding Byte

This example exports legacy journal rules to an XML file using the two-step process similar to the preceding example. In the first step, the Export-JournalRuleCollection cmdlet is used with the ExportLegacyRules switch to export legacy rules to the array $file.

$file = Export-JournalRuleCollection -ExportLegacyRules

In the second step, the exported data is saved to the XML file Ex2007-JournallRules.xml.

Set-Content -Path "C:\MyDocs\Ex2007-JournalRules.xml" -Value $file.FileData -Encoding Byte
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft