If you are an Exchange server administrator, you more than likely spend a fair amount of time searching the Message Tracking logs. The data provided by these logs can be helpful in finding all messages with a particular subject or sent by a certain user during a specific time frame. Of course, there are two ways to search the Message logs: the Exchange Admin Center (EAC) or Exchange Management Shell. Using the GUI is perfectly fine, if that is your preference. However, if you are having to perform searches on a regular basis, the EMS is the more efficient option.
Do you want to know how to get the mailbox count per database on a particular server? Use the following cmdlet to get that information:
Get-Mailbox -Server servername | Group-Object -Property:database | select Name,Count | FT -AutoSize
Remember to change “servername” to the name of your Primary Mailbox server.
Here’s an example of the command output:
We have very busy work and personal lives, which can easily involve several meetings in the span of one week. Outlook reminders serve an important role in helping to manage scheduled appointments and meetings. Although, it’s not sufficient to have a slot on the calendar for that demo scheduled next week with a software vendor. This is where Reminders come to the rescue of human memory shortcomings. A reminder will popup and say “your demo session with Vendor X starts in 15 minutes”. That’s not what it actually says, but you get the point.
With the expanded role of email in business communication, there is a need for organizations to preserve emails for compliance and security reasons. Email has become the lifeblood of companies, the primary means by which employees communicate with clients, coworkers and vendors. Since electronic messages contain business related data or content, emails often maintain importance that extends months or years into the future. Additionally, many times an Email administrator will be faced with the task of gathering and producing messages for legal cases. For these reasons, message Archiving is a vital process.
Here are some useful cmdlets that I’ve collected over time and keep on hand in my toolbox. I hope they come in handy for you as well:
I had a situation where my test environment DAG was offline and not detected. I’m not sure what caused this issue, however the mailbox databases were dismounted and the Content Indexes were in a failed state. This environment has two sites with a single DAG expanding across the sites. One site is active with a single Mailbox server and one CAS/HUB multi-role server. The passive site has the same configuration.
I recently worked on an issue where a client noticed four Archive mailboxes in Outlook with her name. To provide some understanding about the Exchange environment, the servers were running Exchange 2010 SP3 RU5. Also, the users have Outlook 2010 SP1. Although the mailboxes showed her name in the display, they actually belong to her delegates. This was verified by viewing the Archive mailbox folders and their content.
Microsoft introduced the Personal Archives with Exchange 2010. In earlier releases of the product, messages were archived using 3rd party utilities. In addition to eliminating the need for external archiving solutions, this new feature removed the necessity of PST files. Also, since the Exchange Archive is a mailbox, it’s capable of leveraging built-in replication and high availability features within Exchange.
With the introduction of Exchange 2007 came many new features and improvements that help to improve productivity and management: multiple server roles, a 64 bit architecture, built-in high availabilty features (LCR, CCR, SCR and SCC) and Messaging Records Management just to name a few. Another change you will notice is with Email Address Policies (EAPs) and Address Lists.