Release Notes for Windows Small Business Server 2003 R2

Applies To: Windows SBS 2003

Welcome to the Release Notes for the Windows® Small Business Server 2003 R2 (Windows SBS) server software. These Release Notes contain information that help you properly install and use the product.

To link to any of the Web sites that this document refers to, your computer must be connected to the Internet.

Note

Windows SBS 2003 R2 is an incremental software update to Windows SBS 2003 with Service Pack 1 (SP1). In order to successfully prepare to install Windows SBS 2003 R2, you should also review the Release Notes for Windows Small Business Server 2003 with Service Pack 1 (SP1) at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=41392).

Upgrades

You cannot start the Firewall service after upgrading from the evaluation version of Windows Small Business Server to the fully licensed version of Windows Small Business Server Premium Edition.

The Firewall service may not start after you upgrade from the evaluation version of Windows SBS, with Internet Security and Acceleration Server (ISA Server) 2004 installed, to the fully licensed version of Windows SBS Premium Edition.

To resolve this issue, after Setup is finished, run ISA Server Setup in Repair mode.

You might receive a message advising you to reinstall your existing service packs.

When you upgrade in any of the following ways:

  • From Windows SBS to the Windows Server® 2003 Standard Edition operating system, by using the Windows SBS Transition Pack

  • From the evaluation version of Windows SBS to the fully licensed version

  • From Windows Server 2003 to Windows SBS

You see one of the following messages during Setup:

  • On the Setup Requirements page, the list in Requirements includes the warning "The computer is running a Windows Service Pack."

  • A dialog box appears advising you to reinstall your service packs after finishing Setup.

It is possible that the most recent service packs are already included in the version of Windows SBS or Windows Server that you purchased. If so, you may not need to reapply any service packs.

To determine if you need to reapply any service packs after Setup, do one of the following:

R2 Technologies Setup

Documentation for Windows Small Business Server 2003 R2 Setup is now available on the Web.

For step-by-step instructions to install or upgrade to Windows SBS 2003 R2, see the following documents:

You receive an error when you attempt to install the Windows Small Business Server 2003 R2 Technologies, and the R2_Setup.log file contains the error message, "RunMSP System.Exception: 'Unable to Open Product.'"

In order to successfully install the Windows SBS 2003 R2 Technologies, you must be logged on to the server with the local Administrator account.

To resolve this issue, log off the computer, log back on with the local Administrator account, and then rerun Setup.

If you uninstall and then reinstall the Intranet component in the Windows Small Business Server 2003 Server Tools and you have installed Service Pack 2 for Windows SharePoint Services 2.0, you must reinstall the service pack.

The https://companyweb intranet site no longer functions if you do all of the following:

  • Upgrade the Windows SharePoint Services SQL Server 2000 Desktop Engine (Windows) (WMSDE) instance to SQL Server 2000 Standard Edition or SQL Server 2005 Workgroup Edition.

  • Install Service Pack 2 (SP2) for Windows SharePoint® Services 2.0.

  • Uninstall the Windows SBS Intranet component, and then reinstall it.

To resolve this issue, reinstall SP2 for Windows SharePoint Services 2.0.

Note

You can download SP2 for Windows SharePoint Services 2.0 from the Microsoft Update Web site (https://go.microsoft.com/fwlink/?LinkId=19325).

You cannot install Windows SBS 2003 R2 Update Services on a computer that is running Windows Server Update Services (WSUS) 2.0 if you have installed Service Pack 4 for SQL Server 2000 on the WSUS 2.0 WMSDE instance.

If you attempt to install Windows SBS 2003 R2 Update Services on a computer that is running Windows Server Update Services (WSUS) 2.0 and Service Pack 4 for SQL Server 2000, Setup does not complete properly. This is because this is not a supported installation scenario.

To resolve this issue, uninstall WSUS 2.0, selecting the option to remove the existing WSUS database, and then install Windows SBS 2003 R2 Update Services.

You might receive an error if you delay entering the product key during Setup and then run the Add License Wizard.

If you delay entering the product key during initial Setup, and then later you enter the product key and immediately run the Add License Wizard, you might receive the following error message:

"Your client access licenses (CALs) are not valid and cannot be restored from automatic backup. To restore your CALs, click Yes to cancel the wizard, and then in the Licensing snap-in, click Restore Licenses."

You can safely ignore this error message under these circumstances. Click No to continue with the wizard. After your CALs are activated, you will not see this error message again.

Note

This error is also logged once, with an Event Type of Information, an Event Source of SBCore, and an Event ID of 1016.

Update Services

If your network contains computers that are running operating systems with differing languages, the list of languages to update is automatically updated when machines with new languages register with Update Services.

The default language for updates is determined by the language setting of the server that is running Windows SBS 2003 R2. For example, if the language setting of your server is German, updates downloaded for the network are in German by default.

Additionally, if Update Services detects a computer on the network that has a different operating-system language setting, updates downloaded for the network are in that language as well. For example, if the language setting of the server is English, but the language setting of a client computer is German, updates that are downloaded for the server are in English, and updates that are downloaded for the client computer are in German. In other words, Update Services downloads updates in every operating-system language of computers that are registered with Update Services.

Important

Update Services cannot detect the language of individual applications that are installed on a computer. For example, if you have the French version of Microsoft® Office 2003 installed on a computer that is running the English version of Windows XP, Update Services does not detect the language of Microsoft Office 2003.
In these instances, you must do one of two things. You can use the administrator's console for WSUS to select the additional language to download. Or you can browse to the Microsoft Update Web site and manually install the update on the computer that has the application that is in a different language than the operation system.

Important

You cannot change the language setting for updates by using the Update Services snap-in in the Server Management console. To change the language setting for updates, you must use the WSUS administrator's console.
To do so, click Start, and then point to Administrative tools. Click Windows Server Update Services. When the WSUS home page appears, click Options. On the Options page, click Synchronization Options. When the Synchronization Options page appears, click Advanced in Update Files and Languages.

The status on the Update Services home page indicates "up-to-date," even if you exclude all of the computers from Update Services management.

If you exclude all of your computers, including the server, from the list of computers that Update Services manages, the Update Services home page still displays the green check, which indicates that the network is up-to-date.

You may receive a message that says, "Error 0x80072EE2," "Error 0x80072EE7," Error 0x80072EFD," "Error 0x80072F76," or "Error 0x80072F78" on your server when it attempts to synchronize with the Microsoft Update servers.

When Update Services attempts to synchronize with the Microsoft Update servers, one of these error codes may appear in the System log. These errors indicate that Update Services did not receive a response from the Microsoft Update servers. This may be caused by programs that are running on the client computer or by general network-related failures.

For information about how to resolve this issue, see Article 836941, "You may receive an 'Error 0x80072EE2,' 'Error 0x80072EE7,' 'Error 0x80072EFD,' 'Error 0x80072F76,' or 'Error 0x80072F78' error message when you try to use the Windows Update Web site or the Microsoft Update Web site," at the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=69425).

You receive a message that indicates that Update Services has been automatically turned off.

If you install a pre-release version of Windows SBS 2003 R2, then uninstall it, and then install the released version, you may receive a message that says, "Windows Small Business Server (Windows SBS) Update Services is not running because it automatically turns off if you customize Windows Server Update Services (WSUS). For a list of specific settings that cause Windows SBS Update Services to turn off, see the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=65708). Even if WSUS is managing updates for your network, the accuracy of the status in the Windows SBS monitoring report or on the Update Services home page cannot be guaranteed. To use Windows SBS Update Services, reverse the changes that you have made to WSUS or reinstall Windows SBS 2003 R2."

For more information about how to resolve this issue, see Article 921910, "Software updates are not managed by Microsoft Windows Small Business Server 2003 software update services," at the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=69426).

Update Services does not automatically detect new Update Classification types.

During the first 48 hours after the first synchronization starts, Windows SBS 2003 R2 Update Services detects only Critical updates, Security updates and Service Packs. After the first 48 hours, Update Services detects all classification types that were available at the time that Windows SBS 2003 R2 was released. When Microsoft Update releases new update classification types, Update Services does not automatically include the new classification types for detection by network computers. To determine if there are new update classification types, and to enable them for detection by network computers, you must manually add new update classification types.

To do so, click Start, point to Administrative Tools, and then click Microsoft Windows Server Update Services. On the WSUS home page, click Options, click Synchronization options, and then click Change under Update Classification. Review the list of update classification types to see if there are unselected classification types. You can add additional update classification types by selecting the appropriate check boxes. Update Services now includes these update classification types for detection by network computers.

Premium Technologies

You cannot install Internet Security and Acceleration Server 2006 on Windows Small Business Server 2003 R2.

The network configuration tools that are included with Windows SBS 2003 R2 do not support the new functionality that is included with ISA Server 2006. For this reason, do not install ISA Server 2006 on your server that is running Windows SBS 2003 R2. ISA Server 2006 is not supported on Windows SBS 2003 R2.

For more information about Windows SBS 2003 R2, see the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=20996).

When you open the ISA Server 2004 with Service Pack 1 (SP1) Microsoft Management Console (MMC) snap-in, you receive a message that indicates that MMC has detected an error in the snap-in and must close.

If you install ISA Server 2004 with SP1, and you install the Windows SBS 2003 R2 Technologies, you receive the error message described in this heading if you attempt to open the ISA Server 2004 MMC snap-in. This is because of a compatibility issue between MMC 3.0, which is included in the R2 Technologies, and the ISA Server 2004 with SP1 MMC snap-in.

To resolve this issue, you must install Service Pack 2 (SP2) for ISA Server 2004. SP2 for ISA Server 2004 resolves the compatibility issue between MMC 3.0 and the ISA Server 2004 snap-in. To obtain SP2 for ISA Server 2004, see the Downloads page for ISA Server 2004 at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkID=22657).

Note

After you install SP2 for ISA Server 2004, you also need to install an update that resolves known HTTP issues in SP2. To obtain the update, see Article 916106 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=67767).

You must install Service Pack 3 for Internet Security and Acceleration Server 2004 on a server running Windows Small Business Server 2003 R2 that has more than two processors.

If you install ISA Server 2004, and you install the Windows SBS 2003 R2 technologies on a server that has multiprocessors, the ISACTRL and WSPSRV services do not start. This happens because the ISA Server incorrectly determines the number of processors that are installed on a server that has more than two processors.

To resolve this issue, you must install Service Pack 3 (SP3) for ISA Server 2004. For more information about this issue see, the Knowledge Base article “The ISACTRL and WSPSRV services do not start when you install ISA Server 2004 on a multiprocessor computer” at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkID=124843). To obtain SP3 for ISA Server 2004, see the ISA Server 2004 Service Packs page at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkID=124842).

Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results from the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, SharePoint, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.