How To Find Which Exchange 2010 CAS Server a Client Connects To

Written by Dan Erelis, Microsoft Premier Field Engineer. With Exchange 2010 comes the new Client access layer, a true middle tier approach in this version of Exchange. No longer do your clients connect to the backend mailbox server but typically through a VIP (Virtual IP address) of a load balancer with multiple Client Access Servers…


Planning MS Exchange Disaster Recovery using the Microsoft Operations Framework (MOF)

Written by Dan Erelis, Microsoft Premier Field Engineer. As a Premier Field Engineer for Microsoft, I find myself in many different customer environments in just about every major industry sector in Canada. Although every customer is different, the same recurring challenge to implementing Microsoft Exchange disaster recovery exists and that is they don’t know what…


Microsoft Exchange 2010: Tools for Performance and Scalability Evaluation

Written by Dan Erelis, Microsoft Premier Field Engineer based in Canada. The design of a Microsoft Exchange 2010 infrastructure can be a daunting task. Countless hours are spent evaluating current loads, hardware and disk specifications, IOPS requirements and potential client activity/growth. Once you have achieved your goals in the design phase, testing and qualification of…


How Microsoft Exchange 2010 Helps Combat PST Infestation

Written by Dan Erelis, Microsoft Premier Field Engineer  As I discussed in a previous post on combating PST (personal folder files) infestation, one of the fundamental reasons why organizations look to an email archiving solution is to solve the problems associated with PST  storage. There are organizations out there that restrict the use of PSTs,…


MS Exchange PST Infestation: What do you do with all that data?

Written by Dan Erelis, Microsoft Premier Field Engineer, based in Canada. Let me start with the obvious: if you have ever supported Microsoft Exchange or Outlook you already know the fundamental DON’T of PST storage: personal folder files (.pst files) are unsupported over a LAN or WAN link.  Now that we have the technical reasons…