Automating Exchange 2010 Pre-Requisites on Windows Server 20008 R2

Everyone knows its a good idea to automate your installations of Exchange.  It provides a solid, repeatable process by which to deploy your infrastructure – and it takes less time – win/win!.

One area that I have witnessed repeatedly over the last 12 months or so is organisations automating their OS build and Exchange build, but deploying the Exchange pre-requisites manually.  This obviously leads to inconsistencies in the built out environment.

Since Windows Server 2008 we have been able to automate the pre-requisites deployment with “servermanagercmd” and appropriate xml files for each role.  However, in Windows Server 2008 R2 this method is deprecated.

Instead of “servermanagercmd” in Server 2008 R2 and SP2 we use a powershell cmdlet “add-windowsfeature

As a quick example, if you are installing the Client Access, Hub Transport and Mailbox roles onto a single server, the following PowerShell commands will take care of the pre-requisites for you…

Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart

This is discussed in more detail, including the features required for each specific role here :

Posted by Neil Johnson, MCS UK, MCM Exchange 2007

Comments (3)

  1. Anonymous says:

    thank you thank you very much this article. I fixed my problem.

  2. Anonymous says:

    This is really very cool

  3. Ben says:

    The Technet documentation is wrong with R2: it says to install "Web-Server" – This also installs FTP Service and IIS Core mode !

    Replace Web-Server by Web-WebServer to ensure that only *minimum* components are installed.