Upgrading from Windows Server 2008 to Windows Server 2008 R2 fails if the server is running Internet Information Services (IIS) 7.0

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Consider the following scenario.� You are running Internet Information Services (IIS) 7.0 on a Windows Server 2008 server, and you have IIS configured in a web farm environment with Shared Configuration enabled.� When you upgrade from Windows Server 2008 to Windows Server 2008 R2, the upgrade fails and the following error is logged to the Windows Compatibility Report.htm file that gets saved to the desktop:



The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.�



Error



Setup has determined that IIS shared configuration is enabled. You must disable shared configuration to upgrade from Windows Server 2008 to Windows Server 2008 R2. For information about how to disable shared configuration, complete the upgrade, and re-enable shared configuration, see article (http://go.microsoft.com/fwlink/?LinkId=130887 ).

During the upgrade of Windows Server 2008 to Windows Server 2008 R2, Internet Information Services is upgraded from version 7.0 to version 7.5.� IIS 7.5 on Windows Server 2008 R2 introduces new schema elements that cannot be used by, and therefore are not recognized by, IIS 7.0.� Because of this, the upgrade fails.

To resolve this problem in a web farm scenario, you must first disable shared configuration, upgrade to Windows 2008 R2, and then re-enable shared configuration as follows:

�

�

For the first server in the farm:

�

1 -�� Turn off shared configuration

���������������������� Click Start, point to Run, Type in Inetmgr and press Enter.

���������������������� In the Connections pane, Select the server name, Select the Shared Configuration in the Home pane, and click Open Feature in the Actions pane.

���������������������� In the shared Configuration pane, uncheck the Enable Shared Configuration radio button and click Apply in the Actions pane.

���������������������� In the Shared Configuration Information window, click yes to import the shared configuration files along with the encryption keys to the local server.� Note: This action will overwrite the local configuration files and encryption keys.�

���������������������� Click OK in the Shared configuration information window.

���������������������� Close and reopen IIS Manager.

���������������������� Note: This steps is required only if Management Service is installed. In IIS manager, go to the Connections pane, Select the server name, Select the Management Service in the Home pane, and click Restart in the Actions pane.

���������������������� Close IIS Manager.

�

�

2 - Stop IIS

���������������������� Click Start, Right-Click Command prompt and Select Run As Administrator.

���������������������� Type in IISReset /stop and press Enter.

�

�

3 - Upgrade to Windows 2008 R2.

�

4 - Start IIS.

���������������������� Click Start, Right-Click Command prompt and Select Run As Administrator.

���������������������� Type in IISReset /start and press Enter.

�

5 - Export configuration files to a new share location in the file server

���������������������� On the file server that will be hosting the shared configuration files, create a new folder�� (i.e.: \\servername\sharedConfig).

���������������������� On the IIS Server, click Start, point to Run, Type in Inetmgr and press Enter.

���������������������� In the Connections pane, Select the server name, Select the Shared Configuration in the Home pane, and click Open Feature in the Actions pane.

���������������������� Click Export Configuration in the Actions pane

���������������������� In the Export Configuration Window, provide the physical path location (i.e.: \\servername\sharedConfig). And If needed provide the Connect As credentials.

���������������������� Type in the Password for the encryption keys and click OK.

�

�����������������������

6 - Turn shared configuration back on (point to the newly share location containing the exported configuration files created in the previous step).

���������������������� Check the checkbox Enable Shared Configuration.

���������������������� Provide the physical path where the configuration files were exported (i.e.: \\servername\sharedConfig).

���������������������� Provide the user name and password to connect to the share if they were supplied while exporting the configuration. Click Apply in the Actions pane.

���������������������� In the Encryption Keys password window message, provide the password that was supplied while exporting the configuration. Click OK.

���������������������� Click OK on the shared configuration window message.

���������������������� Click OK on the second shared configuration window message.

���������������������� Close and reopen IIS Manager.

���������������������� Note: This steps is required only if Management Service is installed. In IIS manager, go to the Connections pane, Select the server name, Select the Management Service in the Home pane, and click Restart in the Actions pane.

���������������������� Close IIS Manager

�

For more information on shared configuration, please visit the following article:

http://learn.iis.net/page.aspx/264/shared-configuration/#01

�

�

�

�For subsequent servers in the farm:

���������� Follow the same steps as above, except for step #5

�

This behavior is by design. Web farms of both Windows 2008 and Windows 2008 R2 cannot use the same shared configuration due to the IIS schema changes made between IIS7.0 and IIS 7.5.

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE �MATERIALS�) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.