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.

Read More →

Thursday, April 30, 2009 2:56 PM by Eric Norberg

 I have recently received a number of questions surrounding the generation of e-mail addresses in Exchange 2007. Particularly, whether or not custom email addresses can be generated via “legacy” replacement strings to meet specific organizational naming conventions.
This post will present a brief overview of the process as well as offer numerous examples which should assist you when tasked with creating your own custom proxy address templates in Exchange 2007.

Read More →

Recently, I’ve gone through an exercise to rebuild the Exchange 2007 environment at my new company. The original Exchange 2007 design was not what I would call optimal, so we decided to just rebuild instead of fix all of the problems. Luckily, most of the users were still on Exchange 2003, so this made the rebuild fairly simple. We did however run into a couple of issues during the uninstall process which resulted in orphaned Exchange servers in the environment. The servers showed up in Exchange 2003 System Manager and Exchange 2007 Management Console, but the server no longer existed. You might run into the same issue if a server was improperly uninstalled or a server was prematurely reimaged, etc.

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.

Read More →

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.

Read More →

These are some notes I took at TechEd a couple of years ago.

7 Steps to Secure Environment:

  • Establish a Security Team
  • Security Assessment – What impacts our bottom line? What is normal?
  • Risk Analysis – For the Assets
  • Write a Security Policy. Enforce it.
  • Design Operations Plans and Security Standards
  • Implement Training and Awareness Measures
  • Perform Ongoing Security Management

10 Immutable Laws of Security Patch Management

  • 1: Security patches are a fact of life
  • 2: It does no good to patch a system that was never secure to begin with
  • 3: There is no patch for bad judgment
  • 4: You cannot patch what you do not know you have
  • 5: The most effective patch is the one you do not have to apply
  • 6: A service pack covers a multitude of patches
  • 7: All patches are not created equal
  • 8: Never base your patching decision on whether you have seen an exploit code … Unless you have seen an exploit code
  • 9: Everyone has a patch management strategy, whether they know it or not
  • 10: Patch management is really Risk Management