A Messaging Uplift
November 1, 2007
I'm taking the Microsoft course for upgrading skills from Exchange 2003 to Exchange 2007 this week. It's a three day…
Quick Hit: Installing Pre-Reqs for Exchange 2010
Posted on September 12, 2009
This can be a bit tricky … and you can either get enough exposure by doing it so many times that you just know what needs to be installed before you start, or you can get through a bunch of steps in the setup before it stops to tell you that the right things aren’t installed and can’t continue.
Exchange 2010 requires Windows Server 2008 or Windows Server 2008 R2. You can use Server Manager to install the Web Server (IIS) role, however, there are many, many pieces to IIS that are broken out into individual components in 2008. Which ones are required to get you the prerequisites you need to get through the Exchange 2010 installation?
Instead, consider using ServerManagerCmd.exe, which is built-in in Windows 2008 to automate the role installation for you. This command is very useful in installing new components and making sure that you have the pieces you need. From a command line, run:
ServerManagerCmd -i RSAT-ADDS Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-ISAPI-Ext NET-HTTP-Activation Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy Web-Net-Ext –Restart
This will install the necessary components including ADDS which needs to be installed for remote administration of Active Directory and for the Exchange 2010 schema extensions to be installed. Once the command completes, the server will restart. After that, you’re ready for your Exchange 2010 installation.
You can find more information on ServerManagerCmd.exe on Technet.
FYI, Instead of ServerManagerCmd for W2k8R2 MS is now recomending that users use PS to install the pre-req’s for Exchange. ServerManagerCmd is being depreciated.
Exchange 2010 has a number of prerequisite features that need installing. Unfortunately the documentation gives them using ServerManagerCmd. This will never do. Ok the PowerShell equivalent is:
Add-WindowsFeature -Name RSAT-ADDS-Tools, RPC-over-HTTP-proxy, NET-HTTP-Activation, Web-Dyn-Compression, Web-Windows-Auth, Web-Digest-Auth, Web-Basic-Auth, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-ISAPI-Ext, Web-Server -Concurrent
If required the features can be installed individually. The PowerShell remoting features enable us to perform these actions on remote servers as well as the local server.
Nice tutorial. Now I have a crystal clear view when computer networking is involve and truly appreciates the detailed explanation. But it is much better if we are using proxy servers because it make the connection faster. You can go over the internet for for this proxy info. Most especially if you wish not to reveal your basic information. Or better yet suit yourself for free proxies. As you surf, take into consideration that you are in the safe hand.. I think computer networking can be your easy access to the world as it provides general idea regarding about anything. Cheers!!! proxify servers