Office 365: Directory synchronization and object attributes…

For many Office 365 customers directory synchronization is the primary method of populating their Office 365 tenant with users, groups, and contacts.  The directory synchronization process allows for the centralized management of these objects.   In the service customers taking advantage of Exchange Online through Office 365 actually have two directory representations.  Objects managed with…

2

Exchange / Office 365: Have a centralized mailbox for application processing with individual customer SMTP addresses

Customers may implement CRM applications that track customer interactions.  In some instances the CRM applications are configured to archive and record email transactions that are sent to and from customer service representatives.    I recently worked with a customer that has their CRM application configured to monitor a centralized mailbox.  When a new organization was…

2

Exchange 2010 / Exchange 2013: Attempting to mount a new database results invalidOperationException

In Exchange 2010 and Exchange 2013 the process of mounting a database has changed since Exchange 2007.  In versions prior to Exchange 2010 the Information Store process on a server was solely responsible for tracking the creation of mailbox databases and performing mount and dismount operations.   In Exchange 2010 and newer the Active Manager…

7

Office 365: Large item migration limits did not apply…

Administrators of Office 365 may have been pleasantly surprised to hear that the large item migration limit for hybrid mailbox moves has increased.  Administrators may now migrate messages up to 150 meg.  Originally when performing a migration any item that was found in the mailbox over 35 meg was either left behind or it was…

2

Exchange 2013: In place upgrade places components in an offline state.

In Exchange 2013 we introduced the concept of server component states.  This allows administrators a great deal of flexibility to control a server’s ability to service certain requests either partially or fully.  More information on server component states can be found here.   Normally when applying a cumulative update to an Exchange 2013 instance the…

12

Exchange 2010 / 2013 – PAM and the Cluster Core Resources

At any given time, in every database availability group (DAG), there is one member that is responsible for the coordination of database actions across the DAG. This member is known as the Primary Active Manager (PAM). The current PAM can be determined by using Get-DatabaseAvailabilityGroup –Status, as shown below.   [PS] C:\>Get-DatabaseAvailabilityGroup -Status -Identity DAG…

15

Exchange 2013 / Exchange 2010: Database availability groups with shared storage on Windows 2012 and Windows 2012 R2

Although Exchange no longer uses shared storage, it can be deployed in clustered environments where shared storage is used. The storage is not actually shared between nodes as was the case with traditional clustering. Instead, the storage is presented through traditional shared storage controllers including fibre channel and iSCSI.   When creating a cluster with…

2

Exchange and Office 365: Mail Forwarding

Exchange Server and Office 365 offer many different options for forwarding messages to different recipients. Some of these options exist for users and others are for administrators. Administrators can also control how forwarding is handled within the organization.   The forwarding options available to clients and administrators are described below. Each of these methods has…

9

Part 10: Datacenter Activation Coordination – My nodes not invalid!

The Start-DatabaseAvailabilityGroup cmdlet is used to restore failed nodes in a Database Availability Group (DAG) by joining the evicted nodes back to the existing cluster. When a node joins a cluster it is assigned a unique decimal value ID.  For example, the first node is assigned Node ID 1, the second node Node ID 2,…

0