I am sorry I have not written many posts lately, what you may not know is that I just had my first child a few weeks ago and have been living the new baby life.  The good news is I now have a little assistant that I have already begun his training to assist with the site.  Let me introduce you to my new little helper and Exchange Genie Jr.

The next Exchange Genie

Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB 972076) to the download center.

 In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.

KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out:

1. KB 972705: This one is for all the IT pros and anyone who has ever had to explain abnormal database size/log file growth in a short period of time. We have added three new registry entries to help speed up troubleshooting the issue:
   • BytesLogWarningThreshold
   • BytesLogErrorThreshold
   • BytesLogCheckPeriodInMinutes

   More information on the values to set in the above registry keys is documented in KB 972705.

2. KB 975404: Accepting meeting requests sent via an application using CDO like Blackberry devices sometimes results in rendering an embedded message attached to the meeting request inaccessible.
3. KB 976137: We have made a change to the behavior of the Unified Messaging Auto attendant when it plays the greeting for callers on a holiday. Currently when callers call on a holiday, they hear the non-business hours greeting followed by the holiday greeting. In this rollup we have made a change so that the callers calling on a holiday will only hear the holiday greeting. If your greetings are configured such that they would make sense to callers calling on a holiday only if they hear both the non-business hours greeting and the holiday greeting, then you need to re-configure them when you install this update rollup.
4. KB 971177: Another change in the UM Auto Attendants configuration in the Exchange Management Console. It is now aware if your time zone follows Daylight Saving Time.
5. KB 975165: In an environment using self-signed certificates and CAS-CAS proxying, Exchange Web Services requests proxied may start failing after the Availability Service has made a proxy request.
6. A bug where the OWA Virtual Directory cannot be accessed via the Exchange Management Console in an environment coexisting with Exchange 2010 if the Exchange 2007 server was upgraded from Exchange 2007 SP1 to SP2.

KB 972076 has more details about this release and a complete list of all fixes included in this rollup. Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB 972076) to the download center.

In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.

KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out:

1. KB 972705: This one is for all the IT pros and anyone who has ever had to explain abnormal database size/log file growth in a short period of time. We have added three new registry entries to help speed up troubleshooting the issue:
   • BytesLogWarningThreshold
   • BytesLogErrorThreshold
   • BytesLogCheckPeriodInMinutes

   More information on the values to set in the above registry keys is documented in KB 972705.

2. KB 975404: Accepting meeting requests sent via an application using CDO like Blackberry devices sometimes results in rendering an embedded message attached to the meeting request inaccessible.
3. KB 976137: We have made a change to the behavior of the Unified Messaging Auto attendant when it plays the greeting for callers on a holiday. Currently when callers call on a holiday, they hear the non-business hours greeting followed by the holiday greeting. In this rollup we have made a change so that the callers calling on a holiday will only hear the holiday greeting. If your greetings are configured such that they would make sense to callers calling on a holiday only if they hear both the non-business hours greeting and the holiday greeting, then you need to re-configure them when you install this update rollup.
4. KB 971177: Another change in the UM Auto Attendants configuration in the Exchange Management Console. It is now aware if your time zone follows Daylight Saving Time.
5. KB 975165: In an environment using self-signed certificates and CAS-CAS proxying, Exchange Web Services requests proxied may start failing after the Availability Service has made a proxy request.
6. A bug where the OWA Virtual Directory cannot be accessed via the Exchange Management Console in an environment coexisting with Exchange 2010 if the Exchange 2007 server was upgraded from Exchange 2007 SP1 to SP2.

KB 972076 has more details about this release and a complete list of all fixes included in this rollup.

Get-MailboxDatabase -Status | fl name,databasesizes

Name         : DB001

DatabaseSize : 141.8 GB (152,220,270,592 bytes)

 Name         : DB002

DatabaseSize : 98.17 GB (105,412,362,240 bytes)

One of the biggest advantages to RU1 is allowing functionality with RIMs BES servers, however RIM is suppose to release an MR1 soon for Exchange 2010 intergration that will be required on the BES servers

Changes http://support.microsoft.com/?kbid=976573

RIM information to configure Exchange 2010 and BES

http://na.blackberry.com/eng/services/server/exchange/2010support.jsp

One of the major changes with Exchange 2010 is related to the mapi end point. In all previous versions of Exchange the Outlook client (using mapi) would connect directly to an Exchange mailbox server, with Exchange 2010 the Outlook client will connect to an Exchange server running the CAS role as its mapi end point for all connection except public folder access which will go direct to the mailbox server.

As you will discover later in this blog a common issue that user experience if they are running Outlook 2003 is related to the default configuration requiring encryption to be enabled on the Outlook client or connections will fail. I will go into more detail later on this topic.

When a user opens Outlook today a number of items occur but the main one I am going to talk about is the connection from the client directly to the mailbox server to retrieve their mail via mapi-rpc. 

How clients connected pre Exchange 2010

Some of the issues with this configuration even when using an SCC or CCR cluster is during a failover the client connection point will be disrupted even if only for a few moments. This also means that clients are making a direct connection to the server which is limited to 60k connections to the information store. This does not mean 60k users, as client makes a number of connections to the system.

As the Exchange team looked at how they can better scale Exchange 2010 one of the new techniques was to move the client connection endpoint to the CAS server instead of the mailbox server. This allows for a number of things to happen.

1. During a database move/failover the client end point does not go down and makes the move seamless to the user
2. If you reach the 60k port limit you just add an additional CAS server to the rpc array

Let’s take a look at our Exchange settings….

How do I know what my mapi end point is?

At first thought you may think this is configured per user however that is not the case. To find out what your rpc client end point is you need to run the following command get-mailboxdatabase “yourdatabase” | fl  name,rpc* the output of this command will show you each  RpcClientAccessServer associated with each database.

By default there is no rpc array configured, the name of a random CAS server in the same AD site will be directly associated with each database.

Let’s run our command and see what settings we have  get-mailboxdatabase | fl  name,rpc*

You can see that our  RpcClientAccessServer points to my CAS server

Let’s create a new mailbox database in EMC:

Open EMC -> Organization Configuration -> mailbox

Right click and select New Mailbox database

I am going to call my database rpcservercheck and specify the server as E14Ex1

Specify the logs and database path

C:\db\db and c:\db\logs

**note I dont recommend these location but this is just a lab **

Click New to complete the database

Now that we create the new database lets run our command again:

You can see the new database also shows the CAS server, since I only have one CAS in this environment they are configured the same.

Outlook Profile

After setting up an Outlook profile let’s take a look at see that our mapi end point is now the CAS server

With Outlook 2007 click Tools – Accounts Settings

Select the profile and click Change

We can see that our Microsoft Exchange Server information points to the CAS  fqdn and not our mailbox server

If we hold down CTR and right click the Outlook system tray icon we can bring up our connection status

You can see that all Directory and mail connections are now going to the CAS server with 1 exception, public folders. Yes, public folders calls are still direct connections from the client to the mailbox server hosting the public folder.

WireShark

If we use a network sniffer  to capture traffic from our client 192.168.1.59 we can see that NSPI and MAPI requests from Outlook are all directed to the CAS

How does this work?

On each CAS server there is a new service that runs called the MSExchangeRPC which runs as  Microsoft.Exchange.RpcClientAccess.Service.exe and listens on port 6001 for HTTP connection and uses dynamic ports by default for tcp/ip connections

By default when you install Exchange 2010 the files that makeup this service will be located in  C:\Program Files\Microsoft\Exchange Server\V14\Bin

When connections are made to the CAS server by the mapi client, the CAS server then creates a channel to the mailbox server to retrieve the mailbox data.  The CAS server will create a maximum of 100 Rpc connections to the mailbox server

Encryption

As I briefly mentioned in the introduction by default Exchange requires the client to connect with encryption enabled.  This is not set on each database but on each rpc server and can be found with the following command  Get-RpcClientAccess | fl server,encrypt*

 [PS] C:\>Get-RpcClientAccess | fl server,encrypt*

Server             : E14-EX1

EncryptionRequired : True

Server             : E14-EX2

EncryptionRequired : True

 Server             : E14CAS1

EncryptionRequired : True

After running the command you can see that each CAS and Mailbox server has this configuration. You may ask why would the mailbox server require this is all the client connections are direct to the CAS? You may recall that I stated above that the clients still connects direct to the mailbox server  for public folder access.

How do I know if my Outlook client is setup to use encryption?

Let’s look in our Outlook client to see this setting:

Using the same steps as before open your Outlook settings -> click More Settings

Select the Security Tab

We can see that Outlook 2007+ defaults to having encryption enabled however Outlook 2003 does not

 If you have a large number of Outlook 2003 users you have a few options:

1. Use Group Policy to enable this setting
2. Disable this settings on the Exchange Server with the  Get-RpcClientAccess | Set-RpcClientAccess -EncryptionRequired:$false

**Recommended configuration is to keep encryption enabled**

1. Have users manually enable this setting
2. script

**Note this will also affect Outlook Anywhere users (formerly Rpc.https) **

Configuring an Rpc Array

Now that we have a basic understanding of how MOMT is used lets configure our first Rpc Array. You can use NLB or a hardware Load Balancer like F5 for the rpc array as either is supported however you cannot use NLB if your server is multi roled and a member of a DAG.

The dns entry for the array should not use a public dns name and only needs to be resolvable to the internal network.

Lets start with the Get-ClientAccessArray command just to show that we do not currently have an array

1. Create a DNS entry for your array name (I am going to use Site1Array.ExchangeGenie.local)

a. Open the DNS administration tool

b. Select the appropriate DNS Zone (for me .ExchangeGenie.local)

c. Right click and create a new host record (a cname would work as well)

d. Input the name and Ip for the record

e. Click Add Host

F. Click Done

G. Validate the record had been created

 H. Lets use Nslookup to validate the record is seen

Create an RPC Array

From an EMS window we will use the new-clientaccessarray command if you use the help …. get-help new-clientaccessarray, we can see the command takes in 2 require parameters FQDN and Site

If you dont know your AD site information you can use the get-ADSite command to get that information

As you can see I have renamed my default site to GenieSite1

New-ClientAccessArray -Name Site1Array.ExchangeGenie.Local -fqdn Site1Array.ExchangeGenie.Local -Site GenieSite1

As you can see we now have a new array called Site1Array.ExchangeGenie.Local

**Note the memeber paramenter will show every Exchange 2010 CAS in the AD site of the Array, which CAS server actually participate are based on the NLB nodes **

Does this mean you are done?

No,  creating an array but its self does nothing we have 2 additional steps 1. create the NLB for the Array and 2. associate the array to our database.

Creating an NLB for our Array

I am going to use WNLB for this blog which is a viable option however for large organization a hardware load balancer is advised.

If NLB is not installed on your CAS server you will need to do that first.

1. Open Server Manager

2.  Select Features

3.  Select Network Load Balancing

4. Click Next

5. Click Install

 6. Click close after the installation completes successfully

7. Launch NLB Manager

8.  From the file menu click Cluster -> New

9. Input the IP address or hostname of the CAS server and click Connect

10.  Select Next

11. Select Next unless you need to add an additional dedicated ip to the server

12. Click Add to add the VIP for the cluster ** this should match the ip that we used to create our dns record for the array**

13.  Enter the IP asscociated with the array and click OK

14.  Click Next

15.  Enter an FQDN that will be associated with the NLB, I have selected Mulicast for my cluster mode however please select the method that best fits your environment.

16.  Click Next

17. Click Remove to delete the default listening ports

 You can choose to listen on all ports however lets use the minimum required for the array which we will later scope down even lower. The minimum ports required will be 135, 1024-65535

a.   Click Add

b.  Remove the check box “All” so that we can scope which IP the ports listens on

c.  Add port 135 – 135 TCP and click OK

d. Report for port 1024 -65535 TCP and click OK

18.  Click Finish to complete building the NLB

Validate the NLB has been created properly

 Associating the Array with databases

 The final step for us is to associate the client array with our existing databases.  Any new databases will be automatically associated with the array in that site.

Lets open our Outlook client so we can see our current settings

Let’s use the following command to set our new array on all the current databases we have created 

Get-MailboxDatabase | Set-MailboxDatabase -RpcClientAccessServer site1array.exchangegenie.local

**Please note the above command would do all databases you can use the –server switch to scope the databases returned you can use something like this to scope the site

C:\>Get-ExchangeServer | where {$_.isMailboxServer -eq $true -and $_.Site -eq ‘ExchangeGenie.Local/Configuration/Sites/GenieSite1′} | Get-MailboxDatabase **

We can validate the array association with the following command  Get-MailboxDatabase | fl rp*

***Please note it could take a few minute for this information to get updated for clients do to the store cache**

If we look at our client setting, they will get updated with autodiscover if the client is Outlook 2007+, for Outlook 2003 the client should be redirected after connecting to the current configured server.

You can see that all communication (except pf) is now connecting to our new client array

Scoping the Mapi Ports

By default when you open your Outlook client it attempts to make a connection to the rpc port ( 135) on the server andnegotiate a dynamic port above 1024 for usage.  If there are no firewalls between the clients and servers then you dont mind all the traffic however in many scenarios there are firewalls between the client network and servers.  To keep from the requirement of open port 135 and 1024 – 65535 you can make a few simple modifications to your CAS server to reduce the number of ports that are required to be open on the firewall.

There are 3 modifications you must make 1. Mapi which is a registry key change 2. Addres Book (NSPI) which is modifed in the config file and 3. Referral Service (RFR) modified in the config file.

We can restrict Rpc Client Access Array to a single port for each of the following settings Mapi,Address Book, and Referral Service let’s take a look at the default configuration below:

Key:HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem

Value:TCP/IP Port

Type:DWORD

*Note you will need to modify the same registry key on mailbox servers that host the public folder role

Earlier you saw the network wireshark data with the server making connections to the CAS on radom high number ports, in this section we are going to scope the port range down to 3 ports of our choosing.  Please note the client will still need access to port 135 for the initial connection.

Scoping the CAS server ports

1. Open the regsitry editor (start -> run -> regedit

2. browse to HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeRPC

3. Create a new key ParametersSystem (Right click new-> key)

4. Create a new Dword TCP/IP Port

5. Input a port I have selected 50000

6. Restart the Microsoft Exchange RPC Client Access Service

7.  Open a command window and run NetStat -na

We can see that we are connecting the CAS server on port 50,000 and 135

**You will need to repeat these steps for any mailbox server this is hosting a public folder database**

8.  Open Microsoft.Exchange.AddressBook.Service.Exe.config  with notepad (default location is C:\Program Files\Microsoft\Exchange Server\V14\Bin)

*** This option has changed in  Exchange 2010 SP1 and is now configured via a registry key

• Address book Registry change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeAB\Parameters\ RpcTcpPort

9.  Modify the section “RpcTcpPort” to the port you desire, I am going to use 50,001 since I used 50,000 for the mapi port

10. Restart the Microsoft Exchange Active Directory Topology Service (note this will stop all the Exchange services)

11. Open a command window and run NetStat -na

You can see we are now listeing on port 50,000 for map and port 50,001 for Address Book

If we open Outlook again and run a netstat -na from our client we can see that we are connecting to the CAS server on port 50,001 and 50,001 and to our mailbox on port 50,000

CAS IP 192.168.1.60 and Mailbox 192.168.1.57 and CAS Array 192.168.1.61

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4c4bd2a3-5e50-42b0-8bbb-2cc9afe3216a

Whats new:

http://msexchangeteam.com/archive/2009/05/11/451281.aspx

http://msexchangeteam.com/archive/2009/05/13/451311.aspx

When a user accesses the  ECP directory https://mailurl.com/ecp or clicks the options button in the top right of OWA the below view is what the users will see.

one item I would like to point out, is the links “shortcuts to things you can do“. Most of these links take the user to other sections of the ECP however if you click “connect Outlook to this account” they will be directed to http://help.outlook.com .  In the current builds its unsupported to attempt to modify this information to point to internal faq’s

Accounts

The default page a users lands on is the Account sections, which by default will allow a user to update a number of their AD properties like Address, Phone Number, etc..

1. click edit at to bottom of the page

2. Modify attribute and click SAVE

Organize E-Mail

The next section Organize E-mail has 3 features that we can use 1. inbox rules, 2. automatic replies, and 3. delivery reports.

Inbox Rules

This is similar to the rules we had in Exchange 2007 however there are some new features available to us.

1. click New

2. Select create a new rule for arriving messages

3. On the menu select the drop down under the  section “When the message arrives, and:”

4. I am going to select apply to all messages

5. Under the “Do the following:” sections  I am going to pick “Redirect the message to”

6. When the address picker windows open I am going to select Jodie (if you want to redirect to an address not in the GAL just type the address in)

7. click OK

8.Click  More Options

9. Select move,copy, or delete and then Delete the message

10.  If you want to add an exceptions, select the Add Exception button

.

11. Select the exception that applies

12. Now that we have created the rule we want click the save button

Now we can see we have a rule that will redirect all messages to Jodie

Automatic Replies

The Automatic Replies section does not bring any new feature from Exchange 2007 but is the section that we use to set an Out Of Office message or for the old school exchange advocates OOF (Out of Facility)

The first section is set to internal away messages, this is determined by the Accepted Domains that are configured in your Exchange Org.

1. Click the button to Send automatic replies

2. Specify the date range you want to use

3. Enter the message

4. If you wish to set a message for external senders repeat steps 1.-3 for the External Senders section

5. Click the Save button

Delivery Reports

One of my personal favorite features is Delivery Reports which allows a users to perform self message tracking on messages to them or send by them. If enabled the user will also see that the message has been read even if a read reciept was not sent with the message.

* to enable the read tracking use Set-OrganizationConfig -ReadTrackingEnabled $true more can be found at   http://msexchangeteam.com/archive/2009/06/25/451680.aspx

Unfortunately you must use the user picker feature and cannot just type in either  of the first two fields

Lets search for the 2 test messages that I sent out

1.  Click the radius button “Search for messages I have receieved from”

2.  When the address picker opens select the user (or just type in the address) and click OK

3. Click the Search button

4.  You can see I have 2 messages in the report, you can either double click the message or highlight it and click the details button

5. You can see in this report the date and time the message was submitted , that is was delivered and marked as read

Groups

A nice feature that was been made available is the ability for users to join groups that have been created. If you also choose to enable another feature users have the ability to create distribution groups from ECP as well.

1. Clikc the Join button

*I have created 3 groups Demo-Open, Demo-closed,Demo-ManagerApproval *

2.  A windows will open showing all the available groups that can be joined

3. Lets select the first group which is set to be closed and attempt to join it

You see we get a message stating we cannot join this group because its closed

4.  Lets select the next group which requires manager approval

You see we get a message back stating that we have to wait for the manager approval

As the group Owner you will get a message to approve the user

5.  Lets select the remain group which is open to everyone can join

You can see what receieved a message stating we have joined the group

6. Lets now leave the open group that we have joined, select the group Demo-OpenMember and click the Leave button

7. You are now presented with a validation that you want to leave the group, click Yes

Settings

Mail

The first section under the settings tab is Mail,  which is broken up into 5 subsections – 1. E-Mail Signature 2.Read Receipts 3.Reading Pane 4. Conversations 5.Message Format and 6. Message Options

                 Read Receipts

The Read Receipts section provide us 3 options on how to hande Read Receipts on messages

1. Ask me before snding a response <Default>

2. Always send a response

3. Never send a response

            Reading Pane

The next section is the Reading Pane section, which allows a user to configure how to handle a message that is viewed in the reading pane and provides us 3 options

1. Mark the item displayed in the Reading Pane as Read

2. Mark the item as Read when the selection changes <Default>

3.  Do not automatically mark the item as Read

  Conversations

By default in the OWA UI messages are placed into the new conversation view which does take a bit of getting user too.  This section controls how the conversation view is displayed

This section is broken up into 2 parts

1. Sort messages in the conversation Reading Pane in this order:

Choose how to sort the messages in List View in an expanded conversation.

E-Mail Signature

There is nothing really new in this section but provides a user a location to input an email signature, if you want this signature added to each out going message you need to select the check box at the bottom Automatically include my signature on messages I send

 Message Format

 The Message Format section allows us to modify the following

1. Always show Bcc

2. Always show From

If either of the above are selected when creating a new message you will see the from and BCC fields on each message

3.  Compose messages in this format allows us to set the default message type of HTML or Plaint Text

4. We can configure the default font type and size of messages 

6. Empty the Deleted Items folder when I sign out

Spelling

The spelling section allows us to configure a number of options for spell checking.  The ability to configure a custom dictionary is still not there however we do have the same options as Exchange 2007.

 Calendar

General

The General section allows us to configure two options

1. E-Mail name resolution

2. Accessibilty

Once common issue I have found over the years is a user enabling the accessibility options when they first logon to thier mailbx which will then force OWA Light.

Regional

Reginal settings allow a user to configure the following

1. Language

2. Date format

3. Time format

4.  Current time zone

Password

The password section allows a user to change thier current password however you must know the old password when using this feature.

S/MIME

The S/MIME button will only be avaiabled with IE7+ and is not a feature that is supposed with Firefox or Safari since this uses an active X control. When attempting to install this control you will need to have local Admin rights to the machine.

The S/MIME control allows a user to be able to digitally sign or encrypt a message

*Note : currently the control requires the user to have thier certificate published to the directory however there is no feature in the web UI that allows a user to publish thier certificate and there for an Outlook profile or automatic provisioning will be required to use send digitally signe or encrypted messages.

Phone

The phone section is broken down into 3 sub sections Voice Mail (only if your account has been UM enabled), Mobile Phones and Text Messaging.

Voice Mail

Exchange 2007 introduced a new server role called Unified Messaging which intergrates Exchange into systems like OCS and telephony devices.  The OWA web UI now allows a users the ablity to managed settings.

There are 4 sections that can be managed

1. Call Answering Rules

2. Outlook Voice Access

3. Notifications

4. Voice Mail Preview

Mobile Phones

Text Messaging

Another new feature of  Exchange 2010 is the ability to use text messages to send notification to your phone. If you are already using a phone like Windows Mobile, Iphone, Palm Pre etc.. that can sync with Exchange this is most likely not a feature that you would be using however for those users who do not have a phone that is capable of syncing with the system this feature provides you notification for email, calendar, and voicemail.  By default this feature is disabled.

Enabling Notifications

Click “Turn on Notifications”

Next we will be ask to select our country and cell phone provider

You may note if you carrier is not listed there is a link that will take you to the following information page http://help.outlook.com/en-us/beta/ms.exch.ecp.configureregionandmobileoperator.aspx?r=ia&l=0

Click Next

Now you are ask to input your cell phone number

Click Next

A text message will now be sent to your cell phone with a  pin code that will be used to complete the next section

Input the pin that was sent to you phone and click Finish

Once this process has been completed you will find a new rule that has been created to send copies of information to your phone.

Block or Allow

 Exchange provides users with a simple interface to allow user to configure junk filters for thier mailbox.

The first section that we come across is the ability to turn off or on the junk mail filtering

By enabling this feature you  allow the system to move messages into our junk email folder that meet your configuration. Please note that the system can be configured to move messages to the junk folder as well.

Under the Safe Senders and Recipients section we can add users to our safe list to these users to not get placed into our junk mail foler

We also have the option of trusting anyone in our contact list

After the allow section we find the Blcoked Senders information. If a user is added to this section it will not block email from them but tag this message to be listed as junk and move the message to the junk folder.

We can also specify to that all email is considered junk unless the users is explicity listed in our safe list.

If you attempt to add a user that is apart of  your email organization you will receive an error stating you cannot perform this action

http://msexchangeteam.com/archive/2009/08/17/451974.aspx

One of the major product enhancements is the ability to share ones calendar from the new OWA UI and easily consume a calendar in a side by side view.

 Open Shared Calendar

As we know in the past you could open a shared calendar with a url string however  there is a nice easy to use user interface now the provides simple access to another shared calendar.

Share Calendar

One of the exciting scenarios about this feature is if you have enabled federation calendaring you will be able to share your calendar with users on your mail system or other users who are located on Exchange 2010.

1. From the Calendar page select – Share – Share Calendar-Calendar

2. A new message page appears and you can select from 3 options to share your calendar

 A. Free/Busy info  B. Free/Busy with Subject and Location and C. All information

I have selected Free/Busy with Subject and Location

3. You can see that Jodie now gets an email with sharing invite

4. Jodie then clicks the Add this calendar  

5. Now when we go to Jodies calendar there in side by side view she can see Brian’s calendar

Change Permission on calendar

Another new feautre allows a users to remove permission(s) from thier calendar

1. From the Calendar page select – Share – Change Sharing Permissions -Calendar

2. In this view you can see who has what permission to the calendar and delete them if you choose

side by side view

Another nice feature that we have had in Outlook since 2007 is the ability to have side by side calendar views, this feature has now been exposed to the OWA UI allowing users to view shared calendars togethor.

Quite often users send emails and do not know what happens after they click the send button, did the message queue on the server, and was the message delivered.

Exchange 2010 has provided users the ability to view delivery reports and track what has happened to their messages.

1. Once you have logged onto the web UI Select Options in the top right
   

    

   
   

    

    

    

2. From the Exchange Control Panel (ECP) menu select ORGANIZE E-MAIL
   

   
   

    

    

    

3. Select Delivery Reports from the menu
   

   
   

    

    

    

    

4. You currently have 3 fields the can receive input
   

   
   

    

    

5. For this example I am putting TEST in the search subject line
   

   
   

    

6. Click the SEARCH button or hit enter
   

   
   

    

    

    

    

    

7. If the search returns data select the message and click DELIVERY REPORT
   

   
   

    

    

    

8. The report shows the message was submitted and delivered