Articles (76)

By now we are familiar with the concept of DAG. Database availability group is nothing but a set of up to 16 Exchange Server 2016 mailbox servers that provide high availability or automatic database recovery database-level recovery from a database level. It is an improved clustering operation from Exchange Server 2010 onwards. I recommend you to read more about DAG if you are not familiar with, as this article gives only an insight to DAG creation and database copy configuration. Create Database Availability Group 1. Open Exchange admin center (EAC), and navigate to Servers 2. Click on Database Availability Group on the right pane of the console 3. Click on + sign to add DAG 4. Enter the required information such as DAG Name, Witness Server, Witness directory IP address etc. and click on Save button Note: If you plan to use a domain controller as witness server, please add…
We all know that the OWA page (ECP in purticular) has the option to update the user contact information. However, at time you might in need for a script to enable the similar feature, such as when the OWA feature is not available to all user. I had similar situation in my company, where the OWA feature is not enabled for ALL users, and forced to develop a small PS script which enables the users to update their on contact information self. Download the Script Here Following script gives you a sample, and can extend the fields according to your requirement. Below shows the interface that each user gets, and the username field is choosen authomatically from the user's login page. That makes it clear that the script can only run by the users who directly logged into domain joined computers with their network credentials.   Download the Script Here…
In the past we all had nightmares about the recovery of a failed or crashed exchange server. But from the version 2010 (even in 2007) the recovery process became really painless and easy. The following steps will help you to recover a completely failed/crashed server from scratch. Though all of us know, I would like to emphasize the fact that most of the exchange configuration information are stored in the AD database and we only need to recover the application by using the AD information and then complete the Database recovery and other customized exchange settings. Note – This document is reference only for Exchange server which are not part of Database Availability Group. If you wish to get more details about DAG member recovery, please follow  Recovery Installation of a DAG Member with Multi Roles – Exchange Server 2010. Before we proceed, please ensure that a proper account with…
This video will help you to deal with applying the service pack on Exchange Server 2010 DAG Cluster. Microsoft has made the upgrade process fairly simple by the introduction couple of scripts. I will exhibit the behavior of these scripts and its usage in the Cluster infrastructure during the installation of Service Pack 3 on Exchange DAG Cluster with 3 nodes.  Hope this will give an overall idea and a proper approach in your upgrade plans. -Praveen  
This documents describes how the exchange environment for is installed. This includes the steps by step process of installing exchange in a new environment. Exchange and AD Environment Pre-requirement  Ensure that the Active Directory® directory service is in 2003 Native mode. If Active Directory is not in native mode, we will not be able to install Exchange 14.
Let us now discuss about interesting and useful feature of Exchange 2010, MailTips! Mail tips are messages, rather informative messages displayed to the user(who composes the email) while they composing it.  In some situation we think to send out emails for auto response to know whether the user(recipient) is on leave or out of office etc, am I right? Mail tips gives you a way around for this. This small article will give you a little lights on the same.
Microsoft Exchange Server 2010 uses client throttling policies to manage the performance of the Exchange org. In other words, the throttling concept of Exchange 2010 allows an administrator to control how much activity a user is able to perform against an Exchange 2010 client access server.
Microsoft has released the beta version of Exchange 2010 SP1. Click here to download. The beta version has number of features including the personal archive on different mailbox store, few OWA improvements as discussed in my previous article.
Now most of us are aware some new very interesting features of Exchange 2010 including the DAG, Mail Tips, and Transport shadow server etc.  Here I have tried to explain how client access server works in exchange 2010 as middle tier. In Exchange 2007 the CAS server provides a connection end point for all the client requests except for MAPI (outlook) and Entourage. This helped in improving the processing handled by the back end mailbox servers in turn improving the performance. In Exchange 2010 CAS design Microsoft has introduced a new service called RPC client access service. This intern moves all the RPC and directory (AD query) client access connection to middle tier CAS. So, now onwards MAPI clients no longer connects a mailbox server to open the mailbox and will use the RPC client access service in CAS server to connect to AD and Exchange mailbox server. For directory…
Role Based Access Control(RBAC) is the new permission control feature introduced by Microsoft in Microsoft Exchange 2010. By using the RBAC, we can define/control what resources or actions or controls a user or an administrator can access. RBAC in Exchange Server 2010 allows you manage your exchange server permissions effectively. Using a combination of management role groups, management role assignment policies, and management scopes etc, you can grant permissions to administrators and end users. RBAC allows the permission control in broad and granular levels, what an administrator or an end user can do.
Page 1 of 6
theme by reviewshub