Tag: Exchange 2010

Configure MailTips in Exchange Server 2010

MailTips is a one of the new features of Exchange Server 2010. When a Sender composing a message, MailTips gives the some status information of the recipient and that helps to reduces unnecessary and undeliverable e-mails, as well as reduce some embarrassing things done by senders. MailTips are hosted as an Exchange Web Services on the Client Access Server.

MailTips are work with the Scenarios given below.

  1. If one of the recipients is out of office.
  2. When the recipient’s mailbox is full
  3. Message size exceeds sender’s send limit.
  4. If The Message quota exceeds of the recipient.
  5. When Sending email to a large number of recipients.
  6. When trying to send email to restricted recipients.
  7. When a booking a room with exceeded invitees.
  8. When sending to External and invalid domains.
  9. When trying to send to moderated recipients.
  10. Attaching more attachments than allowed.

Configuring MailTips

Gather Organization wide configuration MailTips settings.

Run below CMDlets on Exchange Management Shell to gather ORG settings. See figure 1.

Get-OrganizationConfig | fl *mailtips*


Figure 1

Enable or Disable MailTips.

You must use “Set-OrganizationConfig” CmdLet to enable or disable mailTips. Mailtips are enabled by default. See figure 2.

Set-OrganizationConfig -MailTipsAllTipsEnabled $true


Figure 2

Configure the large audience size for MailTips.

You must use “Set-OrganizationConfig” Cmdlet to configure large audience size. With a fresh Exchange Server 2010 installation it would be 25 by default. If we decrease it to 15, then Mailtip would be display to sender if sender add more than 15 recipients. See figure 3.

Set-OrganizationConfig -MailTipsLargeAudienceThreshold 15


Figure 3

Large Audience Threshold MailTip will display after adding more than 15 recipients . See figure 4.


Figure 4

Enable or disable the External Recipients MailTips

We have some embarrassing experiences of sending some internal information to external parties. However company doesn’t want to restrict sending emails to outside domains. With MailTips  at least we can give a alert to the sender before click send button. See figure 5.

Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $True


Figure 5

External Recipients MailTips displays when trying to send to an external domains. See figure 6.


Figure 6

Enable or disable MailTips that rely on mailbox data

Mailbox based MailTips are rely on the mailbox data. There are two Mailbox based Mailtips, The Recipient Out of Office and Mailbox Full MailTips, rely on the mailbox data. See figure 7,8 and 9 .

Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $true


Figure 7

The Recipient Out of Office. You can get to know if whether the recipient is out of the office before you send the email. See figure 8.


Figure 8

Mailbox Full. If recipient’s Mailbox is full, you can know that before sending the email. See figure 9.


Figure 9

Configure Group Metrics

MailTIps relies on Group Metrics data to provide information on the the size of distribution groups and dynamic distribution groups. Exchange  server normally query a lot of LDAP requests to the Active Directory to get group membership information for each message.This could affect the the performance experienced by the users. To eliminate these issues Exchange server uses the Group Metric data. Group Metric data can be scheduled to run during office hours. You should use Set-MailboxServer CmdLet to configure Group metric Data. See figure 10.

Set-MailboxServer EX10-MB01 -GroupMetricsGenerationEnabled $true


Technorati Tags: ,,

Configuring Client Access Array for Exchange 2010 – Walkthrough

In the previous post we configured the Database Availability Group of Exchange 2010. In this post I will show you how to configure Exchange 2010 RPC Client Access Array. Previous Exchange versions (Exchange 2000/2003) did not support to the use the front-end server by internal MAPI clients. They were connected directly to internal Back-End servers via MAPI over RPC. With the introduction of Exchange server 2007 this limitation has decreased significantly. Client Access Server worked for most protocols except MAPI clients.

With Exchange Server 2010 all protocols should go through the Client Access Server and cannot connect to Mailbox servers by MAPI clients directly. This has been done by introducing a new Client Access Server(CAS) service known as the RPC Client Access service.

To configure Exchange Server 2010 CAS array, you should follow the five steps mentioned bellow.

  1. You must configure internal DNS entry for the name of the CAS array. This name must be unique for the internal network.
  2. You must configure Network Load Balancing. In this case i use Windows Network Load Balancing technology.
  3. Create the new Client Access Array.
  4. Configure a mailbox database to use Cas Array 
  5. Verify the Autodiscover services is working with CAS Array. (This step is optional, but it would be good to verify this)



Architecture of Clients connecting through a CAS array to a mailbox database

Step 1 – Configure Internal DNS

1) Open DNS services manager in Administrative tools and add new a “A Record(Host)” for the Client Access Server array. I used “Client” as CAS Array name and as IP Address of CAS Array. See figure 1.


Figure 1

Step 2 – Configure Network Load Balancing for the Client Access Server Array.

2.1) You must install Windows Network Load balancing feature in CAS servers, where you are supposed to configure CAS array. Run below commend in Powershell. See figure 2 and 3.

Import-Module ServerManager

Add-WindowsFeature NLB


Figure 2: Running “Import-Module ServerManager


Feature 3: Running “Add-WindowsFeature NLB

You will see the screen below after successful NLB installation. See figure 4.


Figure 4.

2.2) Start Network Load Balancing Manager by following – Start / All Programs / Administrative Tools/ Network Load Balancing Manager. See figure 5.


Figure 5: Network Load Balancing Manager.

2.3 ) Click Cluster –> New to create a new NLB Cluster. In the Host section add Netbios name or ip address of the first Client Access Server. In this scenario first CAS Netbios name is “EX10-CAHT”. Then click Next. See figure 6.


Figure 6.

2.4) Here you can see the parameters of the NLB cluster. Leave it as default. Click Next. See figure 7.


Figure 7: New Cluster: Host Parameters

2.5) Then you should add the IP Address of the CAS array. All clients should connect via this ip address and you must give the IP Address that you added in DNS manager during A Record creation. In this scenario it was Then click ok and next. See figure 8.



Figure 8: Adding IP Address for CAS Array.

2.6) In this screen you must add Full Internet Name and Select Cluster Operation Mode. Give the internal FQDN for the Full Internet Name and Select Multicast as shown below. See Figure 9.


Figure 9:- Adding FIN and selecting operating mode.

2.7) Then appears the Port Rules screen. Leave it as default. Click Finish. See figure 10.


Figure 10: Port Rules.

2.6) At this point we have created a new NLB cluster. Then we must add the next Client Access Server(S) to the NLB. Right click the cluster name and click Add Host to Cluster. In this scenario our second CAS server is EX10-CAHT02. Then click Next and Finish. See figure 11 and 12.


Figure 11


Figure 12: Adding Second node’s Netbios name.

Now you can see Windows NLB has been created. See Figure 13.


Figure 13: NLB Manager

Step 3 – Create Client Access Server Array

3.1) We don’t have any pre-Created CAS arrays in this Organization. But would be better to check is there are any pre-created CAS Arrays. Run below command. if you didn’t create a CAS Array before, you will get nothing .  See figure 14.



Figure 14.

3.2) Then you should create new Client Access Array. Run below Cmdlet in EMS. See Figure 15.


Figure 15: Creating new CAS Array.

Now we have finished creating an NLB and a CAS array. Then we must associate databases with this CAS Array.

Step 4 – Adding Mailbox Databases to Client Access Server Array

Now we have come to the final step, that is need to add mailbox database to the Client access server array.

4.1) Use below CMDLet to add mailbox database to CAS array. Here we can add all mailbox databases at once as shown as shown  below. See Figure 16.

Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “Client.msglab.local”


Figure 16 : Adding MailBox databases to the CAS Array.

Step 5 – Configuring Outlook 2010 using Auto Discover

Now when Outlook connects to the Exchange Server, the CAS Array name Appears as client.msglab.local. See figure 17.


Figure 17: Account Information of Outlook

You can see below actual connections made by Outlook. See figure 18.


Figure 18: Connection Status


Note- Client Access Array is only used by MAPI Clients to connect MailBox ,Public Folders and Active Directory only. You must use Windows NLB or another 3rd party NLB solution to load balance Active Sync, AutoDiscover and Availability Services.

Installing Exchange Server 2010 Beta1-part2

This is the second part of the Installing exchange 2010 article. If you have missed first part,I suggest you to read Exchange 2010 pre-requests and system requirements post. In this post I suppose to describe how to install exchange 2010 on the windows 2008 server.

Exchange 2010 setup process added some improvements to install exchange in different languages. You will see bunch of language folders in exchange 2010 source file folder. When we run setup.exe the setup will identify the current language of the operating system and display initial screen and introduction page by current language. In the second step we have to select download language file or use English as a default language.

Please bear in mind once the operating system has been install, you must be install all pre-requisites as mentioned in previous post. After that good to run Microsoft update for any additional update that might be needed. Then restart the server before install exchange 2010.

After setting up everything properly we should able to install exchange 2010.i am not going to guide how to prepare active directory in here. For more information regarding that please refer Prepare Active Directory and Domains TechNet article. Ok I think everything is clear. Let’s back to work.

Now we are ready to install Exchange 2010, you can use either GUI or command line to install. In this article I’ll use the GUI.

I lunch the Setup.exe in the extracted folder. Now you can see Exchange 2010 splash screen.


You can see exchange 2010 Splash screen is very similar to Exchange 2007 one and it’s detect required pre-requisites and those are grayed. So we can proceed to next step.

Click Install Microsoft Exchange link on the Splash screen. Then you will see copying setup files.


After completed the file processing step, Setup appears introduction page.


Click next, then you see language selection page


Currently I don’t have any additional language pack, so I’ll continue English as a Default language pack. Then you see language pack confirmation screen. Click next and continue.

Then license agreement page appears


Accept it and click next. After that error reporting page appears. Select as your choose and click next.

Then Exchange installation type page appears


Click custom and next. Then custom role selection page appears


If you see carefully custom exchange server installation, you will see there is no Clustered mail box server component. Because exchanges 2010 have new feature called incremental Deployment. you can configure high availability option after install exchange 2010.also there is a another feature called Database High availability Group(DAG).if you use DAS it’s created failover clustering for you, no need to create windows failover clustering manually. It makes configuring High availability easy.

Select Mailbox server role, Client access server role, Hub transport server roles. Management tools will select automatically.

Then Exchange organization page appears. Give organization name as a Demolab.


Then client settings page appears


If your organizations have client’s outlook 2003 or earlier versions you must select yes. Because Outlook 2003 and earlier version use public folders to access system data such as Free/Busy. Outlook 2007 and later versions use CAS server to access system data.

Then Exchange Customer Experience Improvement Program appears and joins as your wish.

Then readiness check page appears.


All readiness checks must be successfully passed as below.


AT this point setup is ready for exchange 2010 installation. So I click on the Install button. Then installation screen appears.


After installation Uncheck the Finalize installation using the Exchange Management Console checkbox, and click Finish completing setup. Then reboot the server.


Now Exchange 2010 installation has completed.

Exchange 2007 SP1 update rollup 9 has been released

Microsoft Exchange product team has been release update rollup 9(KB 970162) for exchange 2007 SP1.the release of the rollup via Microsoft update will -happen on July 28.According to Microsoft team blog majority of changes in this rollup are bug fixes.I would like to present some of those fixes.


KB 969911 –This bug is affect customers who is using Messaging Record    Management feature and have specified storage limit for managed folder.after move mailbox,the property which marks the folder as a managed is not preserved.

KB 968621 – Information store stop responding during online maintenance or when schedule backup is canceled.

KB 945877 – Performance improvements to esutil when it vitrifies the checksum of transactions logs.

– Supports for Windows 2008 R2 domain controllers.However that doesn’t mean it supports install exchange 2007 on Windows 2008 R2 Os.

KB 968715 – This bug is mostly effects for clients who have deployed CAS-CAS proxying.


KB 970162-have more details about this release


More Information

Update Rollup 9 for Exchange Server 2007 Service Pack 1 has been released

Description of Update Rollup 9 for Microsoft Exchange Server 2007 Service Pack 1