Release Notes for Windows SBS 2003 Service Pack 1, Premium Edition
Download the most recent Release Notes
These release notes document the Windows® Small Business Server 2003 server software with Service Pack 1.
To install ISA Server 2004, you must use the Windows Small Business Server 2003 Premium Technologies CD
If you installed Microsoft Internet Security and Acceleration (ISA) Server 2004 from a source other than a Premium Technologies CD for the Microsoft® Windows® Small Business Server 2003 (Windows SBS) server software, you must first uninstall ISA Server 2004, then install Service Pack 1 for Windows SBS, and then reinstall ISA Server 2004 using a Premium Technologies CD. You can use the Premium Technologies CD either for Service Pack 1 alone or for the full Windows SBS with Service Pack 1.
Before you uninstall ISA Server 2004, you should export your ISA Server 2004 settings so you can use them after you reinstall. For information about how to export and import your ISA Server 2004 settings, see "Export, Import, and Backup Functionality in ISA Server 2004" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=41516).
Windows Server 2003 with SP1 or later cannot connect to a computer running Windows SBS and ISA Server 2000
If you have a second server running Windows Server 2003 Service Pack 1 (SP1) or later, it may not be able to connect to your Windows SBS computer running Microsoft Security and Acceleration (ISA) Server 2000. Changes in RPC client and server behavior in Windows Server 2003 SP1 cause the ISA Server 2000 RPC filter to deny RPC access to the Windows SBS computer.
To resolve this issue, it is recommended that you upgrade your ISA 2000 installation to ISA 2004 with Service Pack 1 (SP1).
Alternatively, if you are required to continue running ISA 2000, you can install the ISA Server 2000 RPC Filter Update for Windows Server 2003 SP1, available at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=46556).
You may receive an error message indicating that a service or driver failed to start
After you install Windows Server 2003 Service Pack 1 (SP1) or later on your computer that is running Windows Small Business Server and Microsoft Security and Acceleration (ISA) Server 2000, and then restart your computer, you may see the following error message:
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
When you examine the event log, you may see Event ID 14192 in the Application Event log indicating that the Microsoft ISA Server Control service failed to start. You may also see related events in the System Event log indicating that services that depend on the Microsoft ISA Server Control service (such as Microsoft Firewall service and Microsoft Web Proxy service) also could not start.
This behavior may occur if the Routing and Remote Access service starts before the ISA Server Control service.
To fix this problem, you can change the DependOnService entry for the Remote Access service in the registry.
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To change the Remote Access service dependency
Click Start, point to All Programs, point to Administrative Tools, and then click Services.
Right-click Routing and Remote Access, and then click Stop.
Right-click Microsoft ISA Server Control, and then click Start.
Click Start, click Run, type regedt32 in the Open box, and then click OK.
Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess
Double-click the DependOnService entry.
In the Data box, position the pointer below any existing values.
Type isactrl, and then click OK.
Quit Registry Editor.
In the Services snap-in, right-click Routing and Remote Access, and then click Start.
Quit the Services snap-in.
Client computers running Microsoft Outlook and Windows Server 2003 with SP1 or later cannot connect to a computer running Windows SBS 2003 and ISA Server 2004
If you have an additional server on your network that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or later, client computers running Microsoft Outlook on that server cannot connect to a server that is running Windows SBS 2003 and Internet Security and Acceleration (ISA) Server 2004. This scenario is most common when you are using an additional server to provide Terminal Services in application-sharing mode to support client computers on your Windows SBS network.
After you have installed Windows SBS SP1 and you try to reinstall a Windows SBS component, you receive the message, "The drive contains a disc for Windows Small Business Server 2003 with no service packs…"
When you try to reinstall a component of Windows SBS after you install Service Pack 1 for Windows SBS, you might receive this message. This is because Service Pack 1 has not installed correctly.
To fix this problem, run Setup for Service Pack 1 again, and then reinstall the Windows SBS component. When you reinstall the component, you will be prompted to insert your original media for Windows Small Business Server 2003.
After you have installed Windows SBS SP1 and you try to install ISA Server 2004, you receive the error message, “The wizard cannot install ISA Server 2004 because the server is not running the correct operating system. To correct this problem, install Windows Small Business Server 2003 with Service Pack 1, and then restart this wizard.”
This error message occurs if SP1 for Windows SBS 2003 has not been installed on the server. ISA Server 2004 must be installed on a server that is running Windows SBS 2003 with SP1.
If you receive the error message after you install SP1 for Windows SBS 2003, the service pack may not be installed correctly.
To resolve this issue, install the service pack again, and then run ISA Server 2004 Setup again.
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 example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and 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.
© 2005 Microsoft Corporation. All rights reserved.
Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.