Viral Rathod Exchange Server 2016 Blog

Microsoft Exchange Server Blog

  • Click here to Register for Experts-Exchange Account

  • My Experts Exchange Profile

  • Disclaimer

    All information is provided "AS IS" with no warranties, and confer no rights, and as such you perform at your own risk.

    NOTE: You should always make a backup of your server or export the registry before making any changes to it.

  • Advertisements

Archive for the ‘Exchange Server 2010 Posts’ Category

Powershell command to track emails sent to specific user email address

Posted by viralr on December 5, 2016

Suppose you have an end user saying that he is missing a message from an external sender in this case what you will do to track email from exchange server for that user ?

Well you can use following PowerShell command to track emails sent to your end user

Condition 1 – Get all failed/undeliverable emails:

Get-Messagetrackinglog -Recipients: -EventID “FAIL” -Start “5/4/2011 9:00:00 AM” -End “5/10/2011 5:00:00 PM” |ft Timestamp, Source, Sender, Recipients, MessageSubject >>C:output.txt

Condition 2 – Get all success emails

Get-Messagetrackinglog -Recipients: -EventID “RECEIVE” -Start “5/4/2011 9:00:00 AM” -End “5/10/2011 5:00:00 PM” |ft Timestamp, Source, Sender, Recipients, MessageSubject >>C:output.txt

This will give you the output in the form:
Timestamp Source Sender Recipients MessageSubject

Source “SMTP” means it’s an external email and “STOREDRIVER” means processed internally

Hope this help you to track your user email, if any question get back to me and I will be happy to help.


Posted in Exchange Server 2007 Posts, Exchange Server 2010 Posts, Exchange Server 2013 Posts | Leave a Comment »

Email Server SMTP Test for Outgoing E-mails

Posted by viralr on February 24, 2015

Email Server SMTP Test for Outgoing E-mails :-

If you are facing issues where your outgoing Emails are consistently rejected by other servers or land up in Junk Email or SPAM folders of the recipient mail box, this test can help you in identifying the problems.

Testing Process

  1. Send an Email to
  2. That email will bounce with a URL in the bounce messge.
  3. Either click on the URL or Copy/paste the URL in a browser.
  4. You will see report on your Email Server.


Ref :

Posted in Exchange Server 2003 Posts, Exchange Server 2007 Posts, Exchange Server 2010 Posts | Leave a Comment »

Internet Explorer 11 Only Allows “Use the light version of Outlook Web App”

Posted by viralr on February 17, 2014

If you upgraded to Windows 8.1 and tried to access Outlook Web App with the new Internet Explorer 11, you probably noticed that the “Use the light version of Outlook Web App” checkbox is checked and disabled on the login page:


That means that IE11 is willing to render only the basic version of OWA which was originally designed to target legacy browsers. This is quite embarassing, because IE11 is a really modern browser even in the preview! The solution is to force IE to render OWA in compatibility mode. You can add the site to the compatibility list in the Tools –> Compatibility View Settings dialog: Click Add button



IF the above settings didn’t resolve the issue then try to add your OWA URL to the list of sites in the Intranet Zone in the Tools –> Internet Options –> Security –> Local intranet –> Sites –> Advanced dialog.

According to some forum posts, the same issue arises with Office 365 and some popular websites like GitHub as well.

Ref :

Posted in Exchange Server 2010 Posts, Exchange Server 2013 Posts | Leave a Comment »

Exchange 2010 EMC “initialization failed” error execution of scripts is disabled on this system

Posted by viralr on November 15, 2011

Exchange server 2010 and I have just launched the EMC and received the following error.  

Initialization failed

ConsoleInitialize.ps1 cannot be loaded because the execution of scripts is disabled on this system

Cause :-


The reason for this error is the security setting on your pc that does not allow you to execute a script.  This is the so-called Execution Policy. By default, the Execution Policy is set to Restricted. This setting means that you may not run any PS1 script at all.

An overview of the policy levels:

Restricted: Individual cmdlets can run, but not saved Powershell scripts. This is the default setting.
AllSigned: Scripts can run, but must have a digital signature even if written on the local computer. Prompts you before running scripts from trusted publishers.
RemoteSigned: Scripts written on the local computer do not need a digital signature, but any script downloaded from outside (email, IM, Internet) must have a signature to execute. 
Unrestricted: Any script can run, but scripts downloaded from outside will run with a warning.

If you’re working on a desktop and just experimenting with PowerShell, the best is to set the policy-level to Unrestricted. This allows you do everything with annoying security boundaries. Just be careful not to run every script you download from the internet 🙂
If you’re working in a production environment and only want to run self-written scripts, the RemoteSigned level should be loosy enough.

Resolution :-


To change the Execution Policy to Unrestricted, type the following command in Powershell

Set-ExecutionPolicy Unrestricted

To change the Execution Policy to RemoteSigned (to run your own scripts), type the following command in Powershell

Set-ExecutionPolicy RemoteSigned

And that’s it! Your scripts can be run. Have fun !!!!!!!

Posted in Exchange Server 2010 Posts | 3 Comments »

Exchange 2010 Unable to start EdgeSync service on Hub Transport server

Posted by viralr on November 12, 2011

Exchange 2010 HT/CAS/MB on Windows Server 2008 R2 x64

When i try to start edge sync service on HT server, i get an error 

1) Event Id 1070

“EdgeSync has failed. See the EdgeSync Log for more details.” and 

2) Warning Event Id 1045

Initialization failed with exception: Microsoft.Exchange.EdgeSync.Common.EdgeSyncServiceConfigNotFoundException: Couldn’t find EdgeSync service configuration object for the site PDO-GKL. If the configuration object doesn’t exist in the Active Directory location CN=EdgeSyncService,CN=PDO-GKL,CN=Sites,CN=Configuration,DC=pdosolutions,DC=net, create it using the New-EdgeSyncServiceConfig cmdlet. If the object does exist, check its permissions.. If this warning frequently occurs, contact Microsoft Product Support.

Resolution :

1) Open Exchange power shell

2)  Run command “New-EdgeSyncServiceConfig”

3) After that I was able to start the EdgeSync.

Hope this helps.

Posted in Exchange Server 2010 Posts | 5 Comments »

Services for Exchange Server 2007 or Exchange Server 2010 cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server

Posted by viralr on October 31, 2011

When you install Microsoft Exchange Server 2007 or install Microsoft Exchange server 2010 on a global catalog server, Exchange Server services cannot start. However, you can start other services manually. Servers in this configuration may take a long time to shut down. Additionally, the following events are logged:

Event ID : 1005
Source : MSExchangeSA
Category : General
Type : Error
Description : Unexpected error The Local Security Authority cannot be contacted ID no: 80090304 Microsoft Exchange System Attendant occurred.

Event ID: 2601
Source: MSExchange ADAccess
Category: General
Type: Warning
Description: Process MSEXCHANGEADTOPOLOGY (PID=1624). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…> – Error code=80040934. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

Event ID: 1121
Source: MSExchangeIS
Category: General
Type: Error
Description: Error 0x96e connecting to the Microsoft Active Directory.

Event ID: 5000
Source: MSExchangeIS
Category: General
Type: Error
Description: Unable to initialize the Microsoft Exchange Information Store service. – Error 0x96e.

Cause :
This problem occurs because the domain controller and other Exchange-Server-dependent services do not start completely when Exchange Server 2007 or Exchange Server 2010 try to start.

Solution :
–The solution which was worked for me was :

Set all the Exchange failing services to “Automatic (Delayed Start)” and reboot the server .

Make sure after setting the services to “Automatic (Delayed Start)” the services are not starting automatically after reboot.

Automatic (Delayed Start) delays the startup of a service approximately 2 min. after the system has completed starting the operating system.

More about “Automatic (delayed start)”:

Posted in Exchange Server 2010 Posts | Leave a Comment »

Outlook 2010 Sync Issues and Conflicts when Blackberry server available

Posted by viralr on October 20, 2011

–While troubleshooting this issue i observed some e-mails in conflicts folder under outlook 2010

Cause :
–The issue happens because the user opens the message in Outlook before BES delivers it to their Blackberry.  Then the message gets delivered to their mobile and thus the properties of the message on the server are changed before the user changes them with Outlook.

–Research the web and found following Blackberry forum

–As per this blackberry forums ,This is by design of Cached Exchange Mode in Microsoft Outlook. When a new email message arrives at the mailbox, Microsoft Outlook is notified before the BlackBerry Enterprise Server. When the BlackBerry Enterprise Server accesses the email message, it modifies properties such as injecting a RefID.

–A possible workaround is to enable the ProcessMailDelay registry key to cause the BlackBerry Enterprise Server to wait for a period of time before picking up the email message.

Resolution :
–To fix the sync issues, We have two options,

1) Disabled Cached Exchange Mode on user machine and see if that helps.


2) On the Blackberry server follow the above blackberry forum and enable the “ProcessMailDelay” registry key to cause the BlackBerry Enterprise Server to wait for a period of time before picking up the email message.(This registry needs to be change from server so get this enable from your end)

Ref Article :

Hope this post helps to resolve Sync Issues and Conflicts.

Posted in Exchange Server 2010 Posts | Leave a Comment »

Exchange 2010 Store.exe using up RAM

Posted by viralr on September 9, 2011

Exchange 2010 Store.exe using up all the available RAM (High Memory Usage ) :

–In Exchange 2010 It is absolutely normal for Store.exe to grab as much RAM on the server as it can possibly get – as long as Store thinks it needs it to optimize performance. Store was written to do so. It does this as it wants to do as much stuff in memory as possible, without having to go to the slow page file.

–This is a feature, not a bug,Exch will use as much memory as it can for store.exe to optimize performance,another service runs and need some of the RAM itself then exchange will release some

–We can limit the amount of memory that Exchange uses by following the below steps to limit the store.exe process

1.      Start ADSIEDIT.msc

2.      Navigate to Configuration > Services > Microsoft Exchange > <“Organization Name”>  Administrative Groups > <“Administrative Group”>, > Servers > <“Server Name”> > InformationStore

3.      Right-click InformationStore, and edit msExchESEParamCacheSizeMax. Set it it to the number of pages to maximize the Database Cache to. Note that Exchange 2007 works with 8 KB pages and Exchange 2010 with 32 KB pages!

4.    Restart the Microsoft Exchange Information Store service for the change to become effective.

So, for instance, if you want to limit the Database Cache to 4 GB of an Exchange 2010 server, set msExchESEparamCacheSizeMax to 131072 (4 GB = 4.194.304 KB / 32 KB). If you want to limit the Database Cache to 2 GB of an Exchange 2007 server, set msExchESEparamCacheSizeMax to 262144 (2 GB = 2.097.152 KB / 8 KB).

Note that lowering these values may degrade performance, in terms of server performance as well as in terms of end-user experience. However, smaller organizations with a limited number of mailbox users may benefit because they don’t let Exchange claim significant amounts of memory which it will never use.

 You can get more information from the following documents

Why is Exchange Store.exe so RAM hungry?

Note :-It is not recommended to set the “msExchESEParamCacheSizeMax” key to limit the memory usage ,but if you still want to limit the store.exe memory utilization then follow the above ADSIEDIT steps.

Posted in Exchange Server 2010 Posts | 5 Comments »

Exchange 2010 Management Console Initialization Failed

Posted by viralr on August 31, 2011

  • Exchange 2010 Management Console Initialization Failed :

After installing Exchange 2010 successfully and opening up the Exchange Management Console.

The online premises fails with the following error:

[<server_name>] Processing data from remote server failed with the following error message. The user domainAdministrator isn’t assigned to any management roles.,This occurs if the Administrator account is not apart of the Organization Management group. See steps below.

Solution wich worked for me was:

1. Make sure the logon user  is added to “”Organization Management”,”Administrator” ,”Enterprise Admin”  group

  • Open up Active Directory Users and Computers
  • Locate the Administror account being used and go to the properties
  • Locate the Member Of tab and click on Add
  • Add the Organization Management group
  • Click on Apply and Ok
  • Relaunch EMC and this time the console should launch successfully .

If the above steps does not resolved the issue then Try this all………….

— Make Sure Exchange Directories has been excluded from AVG OR any other antivirus software and reboot the server and check the issue.

(Found AVG antivirus was installed on the server and Exchange directories is not excluded from AVG antivirus which was causig the WINRM issue)

Two things were wrong:
Remove any port 80 site bindings that point to a hostname. (IIS Manager, Default Site)
Rename any WEB.CONFIG file in the WWWROOT folder (C:Inetpubwwwroot)
Reboot the Server.

If the above steps does not resolved the issue then simply reboot the server and check ths issue.

Hope this helps.

Posted in Exchange Server 2010 Posts | Leave a Comment »

What’s New in Exchange 2010

Posted by viralr on August 29, 2011

 What’s New in Exchange 2010


Microsoft Exchange Server 2010 brings a new and rich set of technologies, features, and services to the Exchange Server product line. New features and functionality in Exchange 2010 support several key concepts:

  • Flexible and reliable
  • Anywhere access
  • Protection and compliance

The following sections provide you with an overview of some of the important new features and functionality, which you can use when you’re planning, deploying, and administering your Exchange 2010 organization.

(For information about features that have been discontinued or de-emphasized from Microsoft Exchange Server 2003 or Exchange Server 2007 to Exchange 2010, see Discontinued Features.)

For information about the features and changes that have been added in Exchange 2010 SP1, see What’s New in Exchange 2010 SP1.

 Flexible and Reliable

The pressure to optimize your IT infrastructure to respond to changing business conditions demands agility and that means investing in solutions that provide you and your organization choice. Exchange 2010 gives you the flexibility to tailor your deployment based on your organization’s unique needs and a simplified way to help keep e-mail continuously available for your users.

 High Availability Functionality

Exchange 2010 integrates high availability into the core architecture of Exchange to enable customers of all sizes and in all segments to economically deploy a messaging continuity service in their organization.

Exchange 2010 includes many changes to its core architecture. In Exchange 2010, new features such as incremental deployment, mailbox database copies, and database availability groups work with other features such as shadow redundancy and transport dumpster to provide a new, unified platform for high availability and site resilience.

For more information about high availability features, see New High Availability and Site Resilience Functionality.

 Exchange Store and Mailbox Database Functionality

The following is a list of core store functionality that’s included or has been changed in Exchange 2010:

  • Deprecated storage groups
  • Mailbox databases no longer connected to the server object
  • Improvements in Extensible Storage Engine (ESE) for high availability, performance, and database mobility
  • Flattened Outlook store schema
  • Enhanced reporting with public folders

For more information about Exchange store and mailbox database features, see New Exchange Core Store Functionality.

 Permissions Functionality

In Exchange 2010, Role Based Access Control (RBAC) replaces the permissions model used in Exchange 2007. Using RBAC, you can define extremely broad or extremely precise permissions models based on the roles of your administrators and users.

For administrators and specialist users, management role groups define what these users can manage in the organization. Role groups associate role group members to a set of management roles that define what the members can do. By adding or removing users as members of role groups, and adding or removing role assignments to or from a role group, you can control what aspects of the organization the members can manage.

For end users, management role assignment policies define what users can configure on their own mailbox. Assignment policies are applied to every mailbox either by default or manually, and enable you to control whether users can change their personal information, contact information, distribution group membership, and so on.

Both role groups and role assignment policies are assigned management roles. Management roles control access to the cmdlets and parameters required to perform a task. For example, if a cmdlet exists on a management role, and that role is assigned to a role group, the members of that role group can then use that cmdlet.

For more information about RBAC features, see Understanding Permissions.

 Transport and Routing Functionality

The following is a list of new transport and routing functionality included in Exchange 2010:

  • Shadow redundancy
  • MailTips
  • Moderated transport
  • Federated delivery
  • Latency service level agreement (SLA) management
  • End-to-end message tracking
  • Incremental EdgeSync
  • Transport rules integration with AD RMS
  • Transport dumpster improvements
  • Transport database improvements

For more information about transport features, see New Transport Functionality.

 Exchange Server 2010 Deployment Assistant

Exchange Server 2010 introduces the Exchange Server Deployment Assistant, or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment.

For more information, see Exchange Server Deployment Assistant.

 Administration Functionality in the Exchange Management Console

The following is a list of the new core Exchange Management Console (EMC) features included in Exchange 2010. The core EMC refers to new functionality that affects how you use the EMC, and not how you use specific features:

  • Ability to add Exchange forests to the console tree
  • Customer Feedback start tab
  • Community and Resources
  • EMC command logging
  • Property dialog box command exposure
  • RBAC permissions aware for the EMC
  • Online Exchange Help

For more information about EMC features, see New Administrative Functionality in the Exchange Management Console.

 Administration Functionality in the Exchange Management Shell

The following is a list of features available in the new Exchange Management Shell:

  • Remote administration   With the new Shell, you can connect to remote servers running Exchange 2010 across the network with only Windows Management Framework installed, which includes Windows PowerShell. For more information, see Overview of Exchange Management Shell.
  • RBAC integration   The Shell works with RBAC to give you and your users access only to the cmdlets and parameters you and they are allowed to use. If your permissions don’t allow you to configure a certain feature, you aren’t given access to the cmdlets, parameters, or both, that manage that feature. For more information, see Understanding Role Based Access Control.
  • Administrator audit logging   Actions that result in the modification of Exchange organization configuration and other object properties in the EMC, the Web management interface, and the Shell can now be logged for later review. For more information, see Overview of Administrator Audit Logging.
  • Improved multiple-valued property syntax   Instead of running multiple commands to add and remove values from a single property, you can now add and remove values with a single command. For more information, see Modifying Multivalued Properties.

 Exchange Control Panel

Administrators can use the Exchange Control Panel for Outlook Web App to manage some on-premises tasks. The following is a list of the administrative features available:

  • Text messaging integration
  • Voice messaging integration
  • Multiple mailbox search
  • Additional proxy addresses for mailboxes
  • Moderation and approval for distribution list submission

In addition, users have self-service capabilities in that they can perform administrative tasks via the Exchange Control Panel. The ECP enables users to perform common tasks without having to call the help desk. This allows your users to be more productive and allows IT staff to deliver more, while reducing support costs.

For more information, see Configure ECP Virtual Directory Properties.

 Mailbox and Recipient Functionality

The following is a list of the new mailbox and recipient functionality that’s included or has been changed in Exchange 2010:

  • Ability for users to share information, such as calendar free/busy information and contacts with users who reside in a different organization
  • Improved scheduling and configuring for resource mailbox calendar processing
  • Ability to move a mailbox while the end user is still accessing it
  • Additional parameters added to distribution group cmdlets to allow users to create and manage their own distribution groups in Outlook Web App and Exchange 2010
  • Ability to appoint a moderator to regulate the flow of messages sent to a distribution group
  • Ability to manage folder-level permissions for all folders within a user’s mailbox
  • Expanded bulk recipient management to allow you to bulk manage recipient properties
  • Ability to send mail to recipients from the EMC

For more information about mailbox and recipient features, see New Mailbox and Recipient Functionality.

 Exchange Web Services Managed API 1.0

The Microsoft Exchange Web Services (EWS) Managed API 1.0 provides a managed interface for developing client applications that use Exchange Web Services. Beginning with Exchange 2007 Service Pack 1 (SP1), the EWS Managed API simplifies the implementation of applications that communicate with Exchange. Built on the Exchange Web Services SOAP protocol and Autodiscover, the EWS Managed API provides a .NET interface to Exchange Web Services that’s designed to be easy to learn, use, and maintain.

For more information, see Introducing the Exchange Web Services Managed API 1.0 and Microsoft Exchange Web Services Managed API 1.0.

 Client Throttling Functionality to Manage System Performance

Exchange 2010 uses client throttling policies to manage the performance of your Exchange organization. To do this, Exchange tracks the resources that each user consumes and enforces connection bandwidth limits as necessary.

Some of the benefits of client throttling include making sure that:

  • Users aren’t intentionally or unintentionally taxing the system.
  • Users of various connectivity methods are proportionally sharing resources.

You manage client throttling policies with Shell cmdlets. For more information about client throttling policies, see Understanding Client Throttling Policies.

 Anywhere Access

Enhancements in Exchange 2010 helps users get more done by helping them to access all of their communications—e-mail, voice mail, instant messaging—from virtually any platform, Web-browser, or device through industry standard protocols. Managing the flow of information into and out of an individual’s inbox daily can create overload and affect productivity and profitability. In response to this challenge, Exchange 2010 adds new productivity features that can help users more easily organize and effectively prioritize their communications.

 Unified Messaging Features

The following is a list of new Unified Messaging features included in Exchange 2010:

  • Call answering rules
  • Additional language support included in Outlook Voice Access
  • Enhancements to name lookup from caller ID
  • Voice Mail Preview
  • Message Waiting Indicator
  • Missed call and voice mail notifications using text messaging
  • Protected Voice Mail
  • Incoming fax support
  • Addressing to groups (personal distribution lists) support
  • Built-in Unified Messaging administrative roles

For more information about Unified Messaging and voice mail features, see New Unified Messaging Functionality and Voice Mail Features.

 Outlook Web App Features

The following is a list of new features in Outlook Web App included in Exchange 2010:

  • Favorites in the navigation pane
  • Search folders
  • Message filtering
  • Ability to set categories in the message list
  • Options in the Web management interface for Outlook Web App
  • Side-by-side view for calendars
  • Multiple client language support
  • Ability to attach messages to messages
  • Expanded right-click capabilities
  • Integration with Office Communicator, including presence, chat, and a contact list
  • Conversation view
  • Ability to send and receive text messages from Outlook Web App
  • Outlook Web App mailbox policies

For more information about Outlook Web App features, see Understanding Outlook Web App.

 Exchange ActiveSync Features

The following is a list of new Exchange ActiveSync features included in Exchange 2010:

  • Conversation grouping of e-mail messages
  • Ability to synchronize or not synchronize an entire conversation
  • Synchronization of SMS messages with a user’s Exchange mailbox
  • Support for viewing of message reply status
  • Support for availability information for contacts

 Text Messaging Features

The following is a list of new text messaging features included in Exchange 2010:

  • Missed call and voice mail notifications
  • Calendar and agenda updates
  • Text messages sent and received through Outlook Web App and Outlook 2010
  • Text message synchronization with a mobile phone

 POP3 and IMAP4 Cross-Site Connectivity Support

Cross-site POP3 and IMAP4 client connectivity is supported by default in Exchange 2010. For more information about POP3 and IMAP4 client connectivity features, see Understanding POP3 and IMAP4.

 Protection and Compliance

Exchange 2010 delivers new, integrated e-mail archiving and retention functionality, including granular multi-mailbox search and immediate legal hold. Exchange 2010 also helps you to better protect your company’s communications and e-mail through centrally managed information control capabilities. This includes the ability to more effectively intercept, moderate, encrypt, and block e-mail messages. Together, this functionality provides you with a flexible range of protection and control options, whether you want to automatically enforce controls or empower users to implement their own data protection.

 Messaging Policy and Compliance Features

Exchange 2010 compliance features make retention independent of users’ mailbox management and filing habits, and ensure retention policies are applied continuously. The following is a list of new messaging and compliance features included in Exchange 2010:

  • Additional messaging records management (MRM) functionality to apply message retention policies
  • Personal Archive feature to provide users with online archive mailboxes and help eliminate .pst files
  • Mailbox search features for cross-mailbox search with Advanced Query Syntax (AQS) support
  • Additional transport rules predicates and actions

For more information about messaging policy and compliance features, see New Messaging Policy and Compliance Functionality.

 IRM-Protected E-Mail Functionality with Active Directory Rights Management Services

The following is a list of new Information Rights Management (IRM)-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) included in Exchange 2010:

  • Microsoft Outlook protection rules, to apply IRM-protection to messages in Outlook 2010
  • Transport protection rules, to apply IRM protection to messages based on rule conditions
  • Persistent protection of attachments in IRM-protected messages
  • Support for AD RMS templates
  • Support for IRM in Microsoft Office Outlook Web App
  • Transport decryption, to decrypt IRM-protected messages to apply messaging policies
  • Journal report decryption, to attach a decrypted copy of IRM-protected messages to journal reports
  • AD RMS protection for Unified Messaging voice mail messages

For more information about IRM features, see Information Rights Management.

Ref :


Posted in Exchange Server 2010 Posts | Leave a Comment »