Exchange Center

For as long as Microsoft Exchange has existed, Outlook meeting corruption has been a consideration for those who rely on calendaring. Meeting corruption can appear in many forms. However, meeting corruption typically occurs when meetings disappear, when duplicate meetings appear or through other unusual anomalies that users may experience with an appointment.

Eventually all good things come to an end and that’s no exception to our 3rd party certificates that allow access to Outlook Web App and other web-based Exchange workloads such as Active Sync or Outlook. This article provides a step by step process on how to update your Exchange 2010 certificates from start to finish. This article also assumes we are using a DigiCert wildcard certificate. Most of this work can be pre-staged before the actual implementation and is highlighted below. With that, let’s begin!

If you have ever been in a situation where you have lost a physical Exchange 2010 server from your DAG then this document is critical to your ability to recover this server.  Examples of how this could occur are through OS corruption, accidental overwrite or a true datacenter disaster.  Even if you haven’t been in this situation this article will provide the insight to what it takes to recover an Exchange server that had once been a beloved member of your Exchange 2010 DAG.

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!

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.

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.