A little bit of Exchange history

While reading An Overview of Microsoft Exchange Server 2007 White Paper, I noticed this cool Exchange timeline, with all the dates of the major Exchange releases:

Exchange is getting older (and better!), it has celebrated its 11th anniversary recently.

Although I had some experience with MS Mail 3.1, I was introduced to Exchange by version 5.0. It was love at first sight [;)].

And since we’re talking history here, do you know all the code names Exchange had during all this time? Here they are:


Microsoft Exchange Server 5.5

Version 5.5


Microsoft Exchange 2000 Server

Version 6.0


Microsoft Exchange 6.1

Version 6.1 (cancelled)


Microsoft Exchange 2003 Server

Version 6.5


Microsoft Exchange 2006 Server

(Exchange Edge Services)

Version 7.0 (cancelled)


Embedded Exchange


Exchange “12”

Microsoft Exchange Server 2007

Version 8.0

And what about the future? Well, the next version of Exchange, code name Exchange 14 (can you imagine why they skipped 13?) will probably be released in 2010, but who knows what will happen during this time. Untill there, just sit back, relax and enjoy all the exciting new features of Exchange Server 2007.

While doing some research for this post, I was surely intrigued by Magma. David Lemson from Microsoft was kind enough to enlight my knowledge about that.
Magma was the code-name for the portion of Exchange (the store, mostly) that shipped as part of SharePoint Portal Server 1.0.  That product, now MOSS, switched to SQL as their store in the next release.  Magma was only built with Exchange 2000 internally, since there is no remaining consumer, it is no longer being built.  Magma wasn’t really a product, first because it never shipped except to SPS, and second because it was really just a portion of the store, it didn’t have its own code.
The name Magma was inspired by the Austin Powers movie.

Microsoft Exchange Server 2007 Shell Help

Microsoft released an update for the Microsoft Exchange Server 2007 Shell Help. The download contains an XML file that should be placed in the Exchange installation folder.

Brief Description
This download contains an update to the Exchange Management Shell Help

The Microsoft Exchange Server 2007 Exchange Management Shell Help file helps you use cmdlets in the Exchange Management Shell to perform day-to-day administration of Exchange 2007. You can view help in the Exchange Management Shell by using the Get-Help cmdlet.


  1. Close the Exchange Management Shell

  2. Click Download on this page to start the download, or choose a different language from the drop-down list and click Go.

  3. Do one of the following:
    – To start the installation immediately, click Open or Run this program from its current location.
    – To copy the download to your computer for installation at a later time, click Save or Save this program to disk.

  4. Install the Exchange Management Shell Help file, Microsoft.Exchange.Management-Help.xml, to the correct folder that represents your locale. The default installation location is C:\Program Files\Microsoft\Exchange Server\bin\en. “en” is the English language locale code. If you downloaded another language version of the Exchange Management Shell Help file, change the locale code “en” to the locale code for your language, and then install the file. For more information about locale codes, see CultureInfo Class.

  5. Open the Exchange Management Shell after you have completed installation.

TechNet Magazine – June 2007

The June 2007 edition of the TechNet Magazine is now available online.

This time the main subject is security, so expect some good articles, signed by some of the most renowned authors, such as Steve Riley or Mark Russinovich. So far I haven’t discovered an article covering Exchange or messaging besides Windows PowerShell, which is somehow related with Exchange Server 2007 management.

The magazine is also available to download as a standalone HTML Help file (.chm).

ESEUTIL to copy files?

Every Exchange Administrator knows what ESEUTIL does. It can be used to defragment the Exchange databases and recover free space or to repair them (knock on wood).

What probably you didn’t know (I know I didn’t) is that, according to the Microsoft Performance Team, ESEUTIL is the best utility to copy large files over the network. The syntax for ESEUTIL is very simple: eseutil /y <srcfile> /d <destfile>.

Read the full post Slow Large File Copy Issues.

(Source: Flaphead’s blog)

Powershell technical documentation

While reading Anderson Patricio’s blog, I found out about this cool (and free) Powershell book. So I think it’s time for a small compilation of some of the best resources about Powershell available freely on the Internet:

  • Windows PowerShell course book – This “Windows PowerShell” book will give you an introduction to Windows PowerShell as well as practical examples, in order to give you a quick introduction to this subject even if you have no significant previous scripting experience. The book is explicitly not aimed at professional scripters; the extensive Windows PowerShell help and the many Internet forums and additional literature are designed to give experts everything they need.

  • Windows PowerShell Help – chm file – A compilation of tips for Powershel by Paul Flaherty.

  • Windows PowerShell 1.0 Documentation Pack – Documentation of Windows PowerShell 1.0, which includes the Windows PowerShell Getting Started Guide, the Windows PowerShell Primer, the Windows PowerShell Language Quick Reference, and Windows PowerShell V1.0 Release Notes.

  • Introduction to the Exchange Management Shell: Microsoft® Exchange Server 2007 introduces a new management platform called the Exchange Management Shell, based on Microsoft Windows® PowerShell, formerly codenamed “Monad”. This document outlines the key benefits that the Exchange Management Shell provides to Exchange administrators and developers, and explains how cmdlets are structured, and how data is managed.
  • Quick Reference for Exchange Management Shell: Microsoft® Exchange Server 2007 introduces a new management platform called the Exchange Management Shell, based on Microsoft Windows® PowerShell, formerly codenamed “Monad”. This topic provides a list of many frequently used cmdlets, important conventions, and useful tips. The information is presented by feature area, such as recipient, transport, and database administration.

Using Exchange 2007 for Unified Messaging and Fax

Using Exchange Server 2007 for Unified Messaging and Fax is a new podcast (mp3 or wma format) available for download at the Microsoft site.

How can you best implement the Unified Messaging (UM) features of Exchange Server 2007? Microsoft IT uses the UM features of Exchange Server 2007 to integrate voice messaging with the internal e-mail messaging environment. This content will detail the technical implementation and deployment strategy for deploying Exchange 2007 Unified Messaging features in the Microsoft enterprise messaging environment as well as answer the following questions: What is Unified Messaging and why is it a compelling service offering for Microsoft employees? What are the typical features and functions that have been deployed? What design issues do my IT specialists need to be aware of when planning to integrate Exchange Server 2007 with an existing PBX infrastructure?

Exchange Best Practices Analyzer Update Pack

Microsoft released an update for its popular tool Exchange Best Practices Analyzer (ExBPA).

Microsoft Exchange Best Practices Analyzer Web Update Pack contains configuration, rule, and help updates for the ExBPA v2.7.

This download contains the latest XML and ExBPA.chm files. Use this package to update your existing installation of the Exchange Best Practices Analyzer. NOTE: If Internet connectivity is available, the Exchange Best Practices Analyzer will attempt to automatically update itself from the Internet. Where updates are being applied automatically, there is no need to download the Web Update Pack.To find out which version of ExBPA.Config.xml is installed on your computer, click the ‘About Exchange Best Practices Analyzer’ link within the tool. The upper version number refers to the core application (e.g. 2.7.7830.0), the lower version is for the configuration XML file.

Workflow for Exchange

One of the many feeds I keep track is Microsoft Download Center, which allows me to be informed about the latest items available for download. Recently, 2 items triggered my curiosity:

But my enthusiasm quickly faded away, after all these products were meant for Exchange Server 2000 and are discontinued? So, what’s the current and supported away for implementing workflow for Exchange? Windows Workflow Foundation!

Microsoft recommends that you migrate applications that use Exchange Workflow and the Collaborative Data Object for Exchange Workflow (CDOWF) to use the Windows Workflow Foundation. Windows Workflow Foundation supplies the programming model, engine, and tools required to quickly build workflow-enabled applications on Microsoft Windows. It consists of a namespace, an in-process workflow engine, and designers for Microsoft Visual Studio 2005. Applications that use Windows Workflow Foundation can be developed and run on Microsoft Windows Vista, Microsoft Windows XP, and the Microsoft Windows Server 2003 family. Windows Workflow Foundation includes support for both system workflow and human workflow across a variety of scenarios, including workflow within line-of-business applications, user interface page flow, document-centric workflow, human workflow, composite workflow for service-oriented applications, business rule–driven workflow, and workflow for systems management.If you have developed applications that are based on the Exchange SDK Workflow Application Template and you require a copy of the installation package for archival purposes, please contact Microsoft Customer Support Services.The Exchange SDK Workflow Application Templates will be supported while Microsoft Exchange Server 2003 support is available.

Update Rollup 2 for Exchange Server 2007 (KB935490)

Update Rollup 2 for Exchange Server 2007 resolves issues that were found in Exchange Server 2007 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 customers.

If you already downloaded the patch that corrects the Exchange 2007 vulnerability mentioned on the previous post, you noticed that it corresponds to a new Update Rollup.

No, Microsoft will not release a new rollup every 3 weeks, they only did it this time because of the security issue. For a list of the included fixes, please read the Knowledge Base article Description of Update Rollup 2 for Exchange 2007.