After Exchange 2010 SP1 became publicly available I wrote, apart from the SP1 changes, also on the prerequisites differences, comparing Windows Server 2008 with Windows Server 2008 R2. Note that these prerequisites are additional to the server roles and features required to install Exchange 2010 server roles.
With the recent release of Windows Server 2008 R2 Service Pack 1 a new operating system level was introduced to the spectrum. It would be interesting to see what impact R2 SP1 has on these prerequisites. When we put that Exchange 2010 SP1 prerequisites in a table, comparing them to Windows Server 2008 R2 prerequisites, we get the following:
Component | Windows Server 2008 R2 |
Windows Server 2008 R2 SP1 |
AD RMS | KB979099 | |
.NET Framework 2.0 | KB979744
KB977020 (CAS) |
|
.NET Framework 3.5 | KB982867 | |
ASP.NET 2.0 | KB983440 | |
UCMA (UM) | UCMA Runtime 2.0 | UCMA Runtime 2.0 |
Content Filtering
(Hub, Mbx) |
Office 2010 Filter Pack | Office 2010 Filter Pack |
That’s excellent, no hotfixes to install upfront and the required reboot that goes with it. For the suspicious, here’s a what Setup reported missing on a freshly installed Windows Server 2008 R2 SP1 server:
So, we can conclude going straight to Windows Server 2008 R2 SP1 with Exchange 2010 SP1 should make the job of deploying Exchange 2010 SP1 easier and save you some time.
Pingback: Tweets that mention Exchange 2010 SP1 Prerequisites on 2008 R2 SP1 « EighTwOne (821) -- Topsy.com
Just a foot note on the 2010 Filter pack. If you install the filter pack before installing Exchange, the install will register them for you. If you install the filter pack after Exchange has been installed you will need to manually register them with Exchange. Without the filter pack installed and/or registered, Exchange cannot index contents on Office docs.
LikeLike
Jesus. This article saved me a ton of time :). Total duh moment about SP1
LikeLike
Some systems will also require the microsoft server speech platform runtime.
LikeLike