Exxhange SQL And IIS- P73 pptx

TIP To create a transport rule via the Exchange Management Shell, you need to use the New-TransportRule cmdlet.. For example, to create a rule similar to the one we generated using the

Figure 6.16 The New Transport Rule Wizard Actions Page

7 In the Disclaimer text box, type the disclaimer you want to be appended to messages

inside your organization When fi nished, click OK, as shown in Figure 6.17.

8 Click Next

9 On the Exceptions page, click Next.

10 Click New on the Create Rule (Confi guration Summary) page.

11 On the Completion page, click Finish.

Figure 6.17 The Specify Disclaimer Text Box

Now, any message sent from a user within the organization will have a disclaimer appended to each outgoing message, like the one shown in Figure 6.18

Figure 6.18 A Test Message with Disclaimer Appended

Any time after a transport rule has been created, you can modify it as required You do this by

selecting the rule and clicking Edit Rule in the Action pane.

TIP

To create a transport rule via the Exchange Management Shell, you need to use the

New-TransportRule cmdlet For example, to create a rule similar to the one we

generated using the GUI wizard, you would need to run the following command:

New-TransportRule –Name “Corporate Disclaimer” –Comments “This corporate

disclaimer is appended to all messages sent throughout the organization.” –Conditions

“Microsoft.Exchange.MessagingPolicies.Rules.Tasks.FromScopePredicate” –Actions

“Microsoft.Exchange.MessagingPolicies.Rules.Tasks.ApplyDisclaimerAction”

–Exceptions –Enabled $true –Priority “0”

Journaling

Exchange Server 2003 natively supported journaling on a per mailbox store level This functionality is also included in Exchange Server 2007, and is known as standard journaling Standard journaling allows you as an Exchange administrator to enable journaling on a per mailbox database level There’s not

much to say about standard journaling, other than that it is enabled on the property page of a

Mailbox database It then simply works

Although standard journaling is suffi cient for some, it’s too basic for most organizations today

Keeping up with increasing regulatory and compliance regulations requires a much richer archival

solution Therefore, Exchange 2007 also includes premium journaling, a Hub Transport server

feature based on a new journaling agent that can be confi gured to match the specifi c needs of an

organization Premium journaling lets you create journal rules for single mailbox recipients or for

entire groups within the organization

NOTE

Premium journaling, also known as per-recipient journaling, requires an Exchange

Enterprise Client Access License (CAL)

Rules can apply to inbound or outbound messages, or both In addition, the scope can apply

to global, internal or external messages The messages can be archived to any SMTP address, meaning you are not forced to archive to an Exchange mailbox anymore, but can archive to an Exchange-hosted archive solution You can even archive to a third-party archive solution

In order to create a journal rule, perform the following steps:

1 With the Journaling tab selected, click New Journal Rule.

2 In the New Journal Rule wizard (Figure 6.19), enter a descriptive name.

Figure 6.19 The New Journal Rule Wizard

3 Click Browse and select the recipient who should receive the journal reports.

4 Choose the scope you want the journal rule to apply to

5 If the rule should apply to a single mailbox, check Journal message for recipient, then

click Browse and select the recipient.

6 Click New to create the rule On the Completion page, click Finish.

NOTE

If you don’t tick Journal messages for recipient, the Journal rule will archive all

messages sent by all users throughout the Exchange organization

TIP

To create a Journal rule via the Exchange Management Shell, you need to use the

New-JournalRule cmdlet For example, to create a rule similar to the one we

generated using the GUI wizard, you would need to run the following command:

New-JournalRule –Name “Journal all messages to and from Benjamin’s mailbox” –JournalEmailAddress “exchangedogfood.dk/users/Archive” –Scope “Global”

–Enabled $True –Recipient “BWK@exchangedogfood.dk”

When the user Benjamin sends an e-mail message, a journal report will be sent to the specifi c

Journal report e-mail address, as shown in Figure 6.20 As you can see, the journal report includes the message sent by Benjamin as an attachment, as well as information such as sender, subject, and

message-ID

Send Connectors

Send connectors are used to control how Hub Transport servers send messages using SMTP That is, how it handles connections to other e-mail servers This means that a Hub Transport server requires a Send

connector in order to successfully deliver messages to their destination It’s important to note that an explicit

Send connector isn’t created during the installation of a Hub Transport server However, internal Hub

Transport servers use SMTP when delivering messages to each other, and although an explicit Send