Exchange Center

Are you attending TechEd North America in Houston, TX from May 12th – the 15th?  If so then choosing your sessions will be quite the challenge. The conference in its entirety has almost 700 sessions to choose from. If you are an IT professional attending in the “Office Servers and Services” track then your choices are narrowed down to 150 sessions covering Office 365, Office client apps, Microsoft Exchange, Microsoft SharePoint, Microsoft Project, Microsoft Visio, Yammer, and Microsoft Lync. Of those sessions there are 58 to choose from covering Office 365 and Microsoft Exchange and only 4 days of conference to learn it all!

Update 02/13/2014: By popular demand, “Lost modified on:” field has been added which displays the date on which one of the settings on the virtual directory was last modified.

MEC 2014 was an educational event that provided great insights into all aspects of Exchange. If you missed the conference this article will cover learning aspects as they related to deploying Exchange On-Premise. Here are some of my takeaways from the conference on this topic.

Every mailbox object in Exchange has a series of fields called custom attributes.  These can be found by right-clicking on a mailbox in the Exchange Management Console, choosing properties and then clicking on the custom attributes button in the bottom right-hand corner of the window.

As an Exchange administrator you likely work in an environment that has public folders.  Public folders allow users centralized access to tasks, email, calendars, contacts and more.  Over the years Microsoft has worked to move away from this technology, but was not able to due to customer dependence on this functionality.  In Exchange 2013, they have redesigned public folder technology and have introduced Modern public folders.  These are built on traditional mailbox technology which should streamline the backup and recovery process.  Despite this many organizations are still running Exchange 2010, so there is still a need to understand how to recover data from the public folder databases within your organization.

As described in the Office 365 CON 2014 Virtual Conference sessions, “Stairway to heaven – Best practices for Hybrid Deployments”, it is very important that you validate your on-premises environment before getting started with the hybrid bits.

The reason why this is so important has to do with the many interactions between Office 365 [the cloud] and your on-premises environment. Let’s take a look at what components are at stake here.

Previously, we discussed keeping three things in mind when you're trying to find the most cost-effective option for deploying on-premises Exchange: using just a bunch of disks (JBOD) for your deployment, letting Exchange handle its own availability, and automating as much as you can. We went into detail about JBOD deployments, default configurations and approaches to consider for your deployment.

Exchange 2010 Public Folders allow your administrators the ability to grant specific users the ability to send mail on behalf of a mail-enabled public folder.

Before we look at the Manage Send As issue, let’s take a look at how an Exchange or Security administrator would adjust the mail-enabled Public Folder Send As Permissions.

Understanding the details of user mailbox access is very important to knowing what is going on within an Exchange environment. Being able to proactively audit mailbox access has become critical to the technology world we live in today due to the constant threat of security vulnerabilities. Environmental threats can come from inside or outside of our organizations.

So, what kind of information can you obtain if you are auditing user mailboxes?

Have you ever needed to change your Default Role Assignment Policy in Exchange 2010 through Exchange Management Shell? An example of when you might want to do this is to prevent users from creating organizationally visible distribution lists through Outlook Web App. Recently I realized that there may be a problem with the Set-RoleAssignmentPolicy command that can be used to set your users default role assignment policy. Here is what was experienced.