http://markswinkels.nl/2009/05/19/exchange-2010-delete-the-first-mailbox-database/
This past Monday Ross Smith from Microsoft Exchange Team, posted the Exchange 2010 Mailbox Server Role Requirements Calculator during one of his sessions at the Exchange Connections conference in Las Vegas. This tool is the equivalent of the Exchange 2007 Storage Calculator. It’s actually a giant Excel spreadsheet. It’s a useful tool to assist in sizing your Exchange servers and storage. There are many assumptions made when using this calculator, so you always want to test, pilot, and deploy in phases to production. I’ll be posting some of my Best Practices in another blog soon.
When managing Exchange 2007, the recipient scope for Exchange Management Shell (EMS) and Exchange Management Console (EMC) defaults to the domain where the Exchange servers are located. Recipient scope refers to the specified portion of the Active Directory directory service hierarchy that the Exchange Management Console and the Exchange Management Shell uses for recipient management. When you set the recipient scope to a specific location within Active Directory, you can view and manage all recipients stored in that location and all of the containers under it. If your environment has multiple domains, then you may need to change the scope of recipients to find specific accounts. Read More →
While running some reports on Exchange backup success I could not figure out why when I ran get-mailboxdatabase | fl Name,LastFullBackup it would return a blank LastFull Backup. In Exchange Management console I could look at the properties of the database and see the Last full backup and the Last incrementation backup times.
After some search, Martin’s Wonderful World of Exchange had an answer for me. You need to add -status to your command or the backup properties where blank.
Read More →
There are so many articles that I need to write for myself, but with my workload it becomes difficult. I’ve resigned myself to posting links to other people articles. Maybe some day I’ll get back to these.
This article discusses Mailbox cache limits in Exchange. If you ever find yourself in a situation where someone like an executive hits their mailbox storage limit and you need to change their limit very fast you might find that it is not an instantaneous change.
Sending email through telnet can be a useful tool when testing mail functionality, testing for open relays, or sending mail from admin scripts. This is something I don’t use often enough, so I’ve created this blog as a reminder.
Read More →
There are a number of advantages to spreading your users’ mailboxes across your databases in Exchange 2007 versus putting department or groups in to a single database together. One of the biggest advantages is risk mitigation of a single database outage putting an entire group out of commission. Managing database sizes is also important in your environment to meet backup and restore Service Level Agreements (SLAs) in your organization.
In any email environment where quotas are enforced, requests to increase quotas are a regular occurrence. The fact of the matter is storage costs money and therefore must be managed in a meaningful way. There has to be some kind of process or mechanism to determine if a quota increase is justified. Typically quota increases are a result of poor mailbox management. One way to help users is to analyze their mailbox for or with them.