I recently built a test machine with Windows Server 2008 R2 and Microsoft Office SharePoint Server (MOSS) 2007. Before you get started with the MOSS installation, you need to add the .Net Framework 3.5.1 feature to your server and the Web Server (IIS) role. If you do not add the Web Server role manually, the MOSS installation will add it for you, but you’ll run into difficulties later. I’ve previously installed MOSS 2007 and WSS 3.0 on Windows Server 2008 (non-R2) and never ran into any issues.
The first issue I ran into was that MOSS 2007 with SP2 is required to install on Windows Server 2008 R2. A non-SP version or a SP1 version will not install on Windows Server 2008 R2. You can slipstream SP2 into an ISO if you do not have access to media that already has SP2 integrated into it. If you attempt to install a non-SP2 version of MOSS 2007 on Windows Server 2008 R2, you’ll receive the following message:
I chose a basic installation since I wanted to quickly setup a test machine. I received several of these “Program Compatibility Assistant” messages since the basic installation installs SQL 2005. The warming states that you need to install SP3 for SQL 2005.
Watch for what I call pop-unders. This message pops up underneath the installallation screen. The installation will wait forever or until you find the pop-under and click “Run program”.
Here is where you start to see the issues of not manually adding the Web Server role to the server before installing MOSS. Running the configuration wizard at the end of the installation fails with the following:
The referenced error log doesn’t help much. Re-running the configuration wizard without creating a default site will complete successfully. Ignore the name of my server, it’s a virtual machine I previously tested MySQL on.
At this point, a Team Site can be created without issue, but attempting to create a Collaboration or Publishing Portal will fail. You receive the Error “The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated.”:
Checking the Web Application Features shows that this feature is already Active (It is also active at the Farm level):
I found references of this issue in a forum on the TechNet website. The only solution I have found is to reinstall MOSS, although there may be other solutions, you can save yourself a lot of trouble by adding the Web Server role to you server before attempting to install MOSS on Windows Server 2008 R2.