OS Level Anti-Virus Scanning Exclusions for Exchange Servers

In this article we will discuss about how to exclude the File Level Anti-virus scanning on a Exchange server 2010


File Level Anti-Virus Scanning some times cause you problem with Applications, So better way to Exclude some of the Files which used by application.


If they are not correctly configured it might cause problems for Exchange 2010.


Let’s discuss how we can Exclude the files from our Anti-Virus scanning for several Exchange services.


As per recommendation from Microsoft, Exchange Databases, Logs Files, Extensions and other related directories will be excluded from AV Scanning.


Directory Exclusion Sub-Directory Exclusion
C:\Windows\System32\Inetsrv All
E:\Program Files\Microsoft\Exchange Server\V14\Mailbox All

E:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs

E:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Data\Queue All
E:\Program Files\Microsoft\Exchange Server\V14\Logging All
E:\Program Files\Microsoft\Exchange Server\V14\Mailbox All
E:\Program Files\Microsoft\Exchange Server\V14\Mailbox All
Extensions Exclusion Process Exclusions
.EDB, .LOG, .STM, .CHK Msexchangetransport.exe, Microsoft.Exchange.Monitoring.exe, Microsoft.Exchange.Search.Exsearch.exe, Microsoft.Exchange.Servicehost.exe


List of Process Exclusions

Cdb.exe Microsoft.Exchange.Search.Exsearch.exe
Cidaemon.exe Microsoft.Exchange.Servicehost.exe
Clussvc.exe MSExchangeADTopologyService.exe
Dsamain.exe MSExchangeFDS.exe
EdgeCredentialSvc.exe MSExchangeMailboxAssistants.exe
EdgeTransport.exe MSExchangeMailboxReplication.exe
ExFBA.exe MSExchangeMailSubmission.exe
GalGrammarGenerator.exe MSExchangeRepl.exe
Inetinfo.exe MSExchangeTransport.exe
Mad.exe MSExchangeTransportLogSearch.exe
Microsoft.Exchange.AddressBook.Service.exe MSExchangeThrottling.exe
Microsoft.Exchange.AntispamUpdateSvc.exe Msftefd.exe
Microsoft.Exchange.ContentFilter.Wrapper.exe Msftesql.exe
Microsoft.Exchange.EdgeSyncSvc.exe OleConverter.exe
Microsoft.Exchange.Imap4.exe Powershell.exe
Microsoft.Exchange.Imap4service.exe SESWorker.exe
Microsoft.Exchange.Infoworker.Assistants.exe SpeechService.exe
Microsoft.Exchange.Monitoring.exe Store.exe
Microsoft.Exchange.Pop3.exe TranscodingService.exe
Microsoft.Exchange.Pop3service.exe UmService.exe
Microsoft.Exchange.ProtectedServiceHost.exe UmWorkerProcess.exe
Microsoft.Exchange.RPCClientAccess.Service.exe W3wp.exe


You can refer also the following KB article



Configure Client Access Server Array Exchange 2010 using WNLB

In this blog im going to configure client access server array, Previously MAPI Clients used to connect to direct Mailbox Server. But with Microsoft Exchange 2010 all the MAPI Users are now connected to Client Access Server.

Every Mailbox database is associated with Client Access Server service called RPC Client Access

Microsoft Recommends for CAS array Load Balancing with WNLB or Hardware NLB.

Note: You cannot do WNLB with DAG Failover cluster  on the same server

As you can refer the following KB article



We have option to use either WNLB or Hardware Load Balancers. In this scenario im going to configure CAS Server with Windows Network Load balancing Feature in Windows 2008 R2.

Actually Windows Network Load Balance come with the OS so its very reasonable and easy to configure, It can be a good solution for mid-sized companies wanting a cheap load balancing solution.

Before we start the WNLB we should make sure the IP settings in the server

Each Cas server should have minimum 2 Network Connections connected to LAN,

Configure the network adapter with Static Ips


Next Step to install and configure WNLB.

  1. Add the roles from Server Manager WNLB

Now we need to create the cluster in WNLB.

Create New Cluster


In New cluster wizard we need to enter the Cluster name , In host section we need to enter the ip of our Exchange Client access server node 1 click connect , The network adapters will be displayed select NLB adapter next.


Note: Priority value should be configured as 1 for the first Exchange server member

Same settings we need to configure for Second Exchange server to add NLB adapter as 2 priority.

Enter the Full Server Name:  for Ex : outlook.myexchangeserver.com

Note: This is Virtual Name where all outlook users are going to connect to use since we have created FQDN for CAS array

 Cluster operation mode:

Unicast mode

The unicast mode changes the cluster adapter’s MAC address to the cluster MAC address. This cluster address is the same MAC address that is used on all cluster hosts. When this change is made, clients can no longer address the cluster adapters by their original MAC addresses.

 Multicast mode

When using multicast mode, NLB will add a multicast MAC access to the cluster adapters on all of the cluster hosts. At the same time, the cluster adapters retain their original MAC addresses. This way each host could be addressed individually

By using the multicast method with Internet Group Membership Protocol (IGMP), you can limit switch flooding, if the switch supports IGMP snooping. IGMP snooping allows the switch to examine the contents of multicast packets and associate a port with a multicast address. Without IGMP snooping, switches might require additional configuration to tell the switch which ports to use for the multicast traffic. Otherwise, switch flooding occurs, as with the unicast method.

For more info you can refer TechNet


Well, a best practice recommendation is to install two network adapters and use unicast mode, so that the host and cluster network traffic are separated on their own respective network interface. However, if you only have the option of installing one NIC in each CAS server or if you’re forced to using multi-cast mode because of the switches used in your organization, you should pick multicast mode.

Next step

Default  Settings for Ports rules,


To improve the security we should edit port and rules for certain protocols to allow access to Client access server.


Once we are done we need to add the host machines in the existing cluster.

Imp Note : By Default windows 2008 disable Ip forwarding so it will cause problem for WNLB we can enable by using

Refer this article for enabling the IP forwaring.


netsh interface ipv4 set interface “NLB” forwarding=enabled


Now lets Create CAS Array

Once we are done with the MS Exchange 2010 CAS setup we need to create CAS Array in order to make it one.

First Step.

Open the Exchange Management Shell for creating cas array

Run below Cmdlet

New-ClientAccessArray -Name CASArray -FQDN “outlook.myexchangeserver.com” -Site “Default-First-Site-Name”

Name Parameter Specify the Client access Array name

Site Parameter Specify the active directory site which belongs to Client access server

Note  : After the Client Access array has been created, you’ll also need to create the address in DNS and associate it with the virtual IP address used for the Client Access array.

Once we are done we need to associate RPCClientAccessServer with Mailbox database on which clients will connect

Using CmdLets

Adding Mailbox Databases to Client Access Server Array

Set-MailboxDatabase MDB03 -RpcClientAccessServer “outlook.myexchangeserver.com”

Verifying the Mailbox Database RPC Settings using Get-MailboxDatabase

Now our outlook clients will connect to NLB Cluster name

We can verify the Server connection from Outlook by using Press Ctrl + Right Click Outlook icon in system tray and check the

Connection status.

Hope this article helps you thanks for viewing.

Update Rollup 6 for Exchange Server 2010 Service Pack 1

Exchange 2010 Rollupdate was released in Nov

Following issues resolved after apply this update.

  • 2431609  An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
  • 2449266  EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
  • 2480474  A Users do not receive quota warning messages after applying SP1 for Exchange 2010
  • 2514820  An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
  • 2521927  Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
  • 2528854  The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
  • 2535289  The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
  • 2536313  Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
  • 2544246  You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
  • 2548246  The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
  • 2549183  “There are no objects to select” message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment
  • 2549289  A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
  • 2555851  A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
  • 2559814  A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
  • 2561514  Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
  • 2563860  You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
  • 2567409  Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
  • 2571791  Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
  • 2572052  Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
  • 2575005  You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
  • 2578631  Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
  • 2579671  No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
  • 2582095  The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
  • 2600835  The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
  • 2601701  The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
  • 2616127  “0x80041606” error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment
  • 2617126  The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment
  • 2627769  Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment

Configuring Exchange Settings on IPhone

Configuring Your IPhone to us MS Exchange Mailbox

New Concept of using Email from Smart Phones for Business users,

The Apple iPhone offers Exchange ActiveSync functionality were users can Exchange Mailbox account and Sync Emails,Contacts,Calenders .When a user uses the Apple iPhone to synchronize e-mail messages, all e-mail messages in their inbox are synchronized to the iPhone. Users can’t limit the synchronization to only 3 days of e-mail messages as they can with other phones.

Let’s Begin

On the iPhone, go to Settings, then Mail, Contacts, Calendars and create a new Microsoft Exchange account.


Add Account

Select Microsoft Exchange


Enter Full Email address, Domain Name, User account and password Details,


Once clicking Next, You will be asked to enter the server name, So Enter the Server name

And Use SSL One

Now we need to set the Mail , Calender, Contact settings

Here if you can See we can Sync our emails with no limit

Now you can Send and receive Emails from our IPhone Enjoy it…..

Hello Everyone

Here is my First blog about Exchange 2010 Unattended Installation Mode.

Let’s discuss about the deployment Scenario for Exchange 2010 in Unattended Mode,

Types of Setup

We have Following Types of Setup which we can perform for Exchange server

1) Exchange Setup GUI:  We can run the Exchange 2010 Setup wizard GUI Mode

2) Exchange Unattended Setup: Setup.com is an unattended which we need to perform using Command prompt or through a script

Before we start our setup we need to install the prerequisites


  • We need to make sure that our Forest Functional Level is windows 2003 Active Directory
  • Minimum OS should be Windows Server 2008 with SP2 64bit or Windows Server 2008 R2 must be installed for Exchange 2010 server
  • Configure Raid as per your requirement.
  • Make Sure to  install Windows Updates
  • Permissions for deploying Exchange 2010
    • Schema Admins
    • Domain Admins
    • Enterprise Admins
    • Local administration rights on the server
  • Imp Note: If we you are planning for DAG (Database Availability Group) We Must install Windows Enterprise 2008 Sp2 or R2 because The Standard Edition doesn’t support the features needed for DAG.
  • Make Sure the IP Settings are proper
  • Microsoft Office Filter Packs http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17062
  • Adding  Import-Module ServerManager from Power Shell
  • Add-WindowsFeature cmdlet to install the component

We are deploying the following roles in Exchange 2010 

Client Access, Hub Transport, and Mailbox server for this we need the following features: 

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy –Restart


After the restart launch another elevated Windows PowerShell console and run the following command

Set-Service NetTcpPortSharing -StartupType Automatic


Just a quick Note:

Before Exchange 2010 SP1 released we need to install this components manually

Now Exchange SP1 has new deployment Functionality were it will install all the components automatically


More information


We can now select the /InstallWindowsComponents parameter during an unattended install of Exchange 2010 SP1

Also we need to install some of the Hotfixes if we are deploying

Exchange 2010 SP1 and SP2 Hotfixes for Windows Server 2008 R2

List of Hotfixes





For more information you can use this link


Before we install Exchange Server in our Organization we need to prepare schema and AD

Setup.com /Prepareschema or Setup.com /PS

To run this command you should have schema admin rights and Enterprise Admin.

Setup /PrepareAD /OrganizationName:organization name

Once we are done with Prepare schema same as we need to run prepare AD.

Lets begin the Setup

setup.com /mode:install /role:CA,MB,HT,MT /organizationName:MyExchangeserver

This command we need to run to install the following roles Client Access Server,Mailbox & Hub-Transport

Now we need to restart the server

Verifying Our Exchange server setup.

Here is very important thing which we need to check to verify our setup.

Microsoft Recommends to verify the setup by using Get-ExchangeServer Cmdlet or by reviewing the Setup logs file.

We can use this CMD to check Full information about our Exchange Server

Get-ExchangeServer |FL


You can find the setup log at <system drive>\ExchangeSetupLogs\ExchangeSetup.log. The <system drive> variable represents the root directory of the drive where the operating system is installed.

For more info you can refer


Thanks for Viewing.

Exchange 2010 Setup in Unattended Mode