If like me, you’re looking forward to getting Server 2008 R2 up and running in the server room, and taking advantage of all those juicy new features like BranchCache and Direct Access, you might be interested in this document.
It outlines what are the supported upgrade paths to Server 2008 R2. It’s quite straightforward and is very similar to the supported upgrade paths to Windows 7. Here’s what’s definitely not supported:
Upgrades to Windows Server 2008 R2 from the following operating systems are not supported:
- Windows® 95, Windows 98, Windows Millennium Edition, Windows XP, Windows Vista®, Windows Vista Starter, or Windows 7
- Windows NT® Server 4.0, Windows 2000 Server, Windows Server 2003 RTM, Windows Server 2003 with SP1, Windows Server 2003 Web, Windows Server 2008 R2 M3, or Windows Server 2008 R2 Beta
- Windows Server 2003 for Itanium-based Systems, Windows Server 2003 x64, Windows Server 2008 for Itanium-based Systems, Windows Server 2008 R2 for Itanium-based Systems
- Cross-architecture in-place upgrades (for example, x86 to x64) are not supported
- Cross-language in-place upgrades (for example, en-us to de-de) are not supported
- Cross-edition upgrades (for example, the Windows Server 2008 Foundation SKU to the Windows Server 2008 Datacenter SKU) are not supported
- Cross-build type in-place upgrades (for example, free to chk) are not supported
That’s all pretty straightforward, and the doco goes into depth about which are the supported upgrade paths, which I won’t repeat here. There’s no information available about whether server running particular roles are suitable for upgrade – for example, are there any gotchas when considering to upgrade a DC running IIS. Hopefully, we’ll get more information on that shortly.