Export (0) Print
Expand All

Release Notes for Windows Small Business Server 2003 with Service Pack 1

Version: 6

Published: September 2005

Contents

How to Use These Notes

Welcome to the release notes for the Microsoft® Windows® Small Business Server 2003 (Windows SBS) server software with Service Pack 1 (SP1).

These release notes contain information that will help ensure proper installation and use of the product.

To link to the Web sites referenced in this document, you must be connected to the Internet.

Before You Install Windows Small Business Server 2003 with Service Pack 1

Download the latest release notes

To download an updated version of these release notes, visit the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=41392). The update may contain additional critical information that was not available when Windows Small Business Server 2003 with Service Pack 1 was released.

Review the Windows Server 2003 release notes

Windows Small Business Server 2003 runs on a foundation of the Microsoft Windows Server™ 2003 operating system. Before installing Windows Small Business Server 2003, review your operating system release notes. To do so, open Relnotes.htm, located in the \Docs folder on Windows Small Business Server 2003 Disc 1.

Unplug UPS devices

Setup causes some uninterruptible power supply (UPS) devices to switch to battery mode during hardware detection. If a UPS device switches to battery mode during hardware detection, Setup may fail.

Updated Release Notes

SP1 for Windows SBS 2003 cannot be applied to evaluation versions of Windows SBS 2003

SP1 for Windows SBS 2003 cannot be applied to evaluation versions of Windows SBS 2003. Before you apply SP1, you must upgrade your installation from the evaluation version to the full retail version of Windows SBS 2003.

Do not run the Windows Server 2003 Security Configuration Wizard on Windows Small Business Server 2003

The Security Configuration Wizard, which is included with Service Pack 1 for Windows Server 2003, is not designed to work with Windows SBS. Running this wizard can create conflicts with settings that are configured by Windows SBS Setup.

To help secure a computer running Windows SBS, it is recommended that you accept the default settings during Setup and then run the Configure E-mail and Internet Configuration Wizard.

If you run the Security Configuration Wizard on Windows Small Business Server 2003 and experience problems, use the rollback feature in the Security Configuration Wizard to undo the changes.

It is not necessary to install Windows Server Update KB891016 to ensure successful recovery of Exchange data

The CD version of these release notes states that you should install Windows Server Update KB891016. This is no longer necessary because the update is now installed automatically. The update has been removed from the CD and is no longer available on the Microsoft Web site.

E-mail to external recipients with the same e-mail domain name might generate NDR messages when using the POP3 Connector

Windows SBS Service Pack 1 automatically configures Exchange Server to reject e-mail messages that are sent to accounts that do not exist in Active Directory. If you use the Microsoft Connector for POP3 Mailboxes and you have configured Exchange to use the same e-mail domain name as the one being used by your external POP3 mail server, users might receive errors when they try to send mail to external recipients that use the same e-mail domain name.

This issue affects only servers where the SMTP virtual server in Exchange is configured to send mail with unresolved recipients to an Internet service provider's (ISP's) mail server.

To resolve this issue, configure the Default Policy in the Exchange recipient policy to use the local e-mail domain as the primary address, and then add an additional recipient policy to apply the POP3 e-mail domain to the local user accounts. This way, the e-mail domain for the local users matches the e-mail domain that the POP3 mail server is hosting, but the conflict between Exchange and the POP3 mail server is resolved.

The user accounts must be configured so that they are updated by recipient policies. This option is available under the properties for each user on the E-mail Addresses tab.

For more information about how to configure the recipient policies in Exchange, see article 300681, "E-mail to external recipients with the same e-mail domain causes NDR messages when using the POP3 Connector" in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=41371).

noteNote
Every time you run the Internet Connection Wizard or the Configure E-mail and Internet Connection Wizard and set it to modify the Exchange settings, the wizard uses the e-mail domain address that you enter to set the primary address on each recipient policy. After the wizard is finished, you must repeat the steps in this Release Note to modify the recipient policy.

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 and later may 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) 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.

CautionCaution
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
  1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.

  2. Right-click Routing and Remote Access, and then click Stop.

  3. Right-click Microsoft ISA Server Control, and then click Start.

  4. Click Start, click Run, type regedt32 in the Open box, and then click OK.

  5. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess

  6. Double-click the DependOnService entry.

  7. In the Data box, position the pointer below any existing values.

  8. Type isactrl, and then click OK.

  9. Quit Registry Editor.

  10. In the Services snap-in, right-click Routing and Remote Access, and then click Start.

  11. Quit the Services snap-in.

noteNote
You can find more information about this problem at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=46567).

Setup

DHCP is not disabled on a Microsoft Broadband Networking device during Setup

This occurs when you are running the DHCP service on a Microsoft Broadband Networking device that is not running firmware version 1.09 or later. If you request that the DHCP service be disabled on this device automatically when the device is detected during Setup, Setup does not disable the DHCP service on the device. This results in network problems because the DHCP service will be running on both the computer running Windows Small Business Server and the Microsoft Broadband Networking device.

To resolve this issue, stop the DHCP service manually on the Microsoft Broadband Networking device after running Setup.

Upgrade: Remnants of Windows 2000 Administration Tools may block upgrade to Windows Small Business Server 2003

When you are upgrading from Windows 2000 Server or Small Business Server 2000 with Service Pack 1, Setup may become blocked because of some entries left in the registry from a previous Windows 2000 Administration Tools installation. This can occur even if the Windows 2000 Administration Tools were uninstalled prior to upgrade.

To unblock Setup
  1. Open the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B7298620-EAC6-11D1-8F87-0060082EA63E}

    noteNote
    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.
  2. Ensure that there is not a value displayed for Display Name. If there is, it means that the Windows 2000 Administration Tools were not successfully uninstalled and that you need to use Add or Remove Programs to uninstall the tools again.

  3. When the Display Name value no longer exists, delete the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B7298620-EAC6-11D1-8F87-0060082EA63E}

Do not use the .local domain name during Setup if you have client computers running Macintosh OS X version 10.2 or later

If you have Macintosh client computers that are running the Macintosh OS X version 10.2 operating system or later, and you are using the .local label for the full DNS name of your internal domain, then those client computers cannot discover other computers that are members of the network and that use the .local label. Macintosh OS X version 10.2 uses the .local label for its Rendezvous service. To work around this, it is recommended that you do not use the .local label for the full DNS name of your internal domain.

If you have Macintosh client computers that are running the Macintosh OS X version 10.3 operating system or later, and you are using the .local label for the full DNS name of your internal domain, then those client computers cannot discover other computers that are members of the network and that use the .local label. Macintosh OS X version 10.3 uses the .local label for its Rendezvous service. To work around this, it is recommended that you do not use the .local label for the full DNS name of your internal domain. If you must use the .local label, then you must also configure settings on the Macintosh computers so they can discover other computers on the network. For more information about how to configure client computers running Macintosh OS X version 10.3 or later, see “Connecting Macintosh Computers to a Windows Small Business Server 2003 Network” on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=39689).

Upgrade: Setting mailbox quotas for Exchange Server 2003 may prevent users from sending or receiving e-mail

Windows Small Business Server 2003 Setup sets the following quotas for Exchange mailboxes:

Issue Warning at (KB): 175000

Prohibit Send and Receive at (KB): 200000

Users with mailboxes that exceed the quota set during Setup may be prevented from sending or receiving e-mail after an upgrade.

To resolve this issue, perform one of the following actions:

  • Reduce the size of the mailboxes affected by deleting old or unnecessary e-mail to match the new quotas. A good place to start would be the Deleted Items and Sent Items folders.
  • Change the size of the mailbox quota.
To change the size of the mailbox quota
  1. On the computer running Windows Small Business Server 2003, click Start, and then click Server Management. In the console tree, double-click Advanced Management, double-click Exchange, double-click Servers, and then click the name of your server.

  2. In the details pane, double-click First Storage Group, right-click Mailbox Store, and then click Properties.

  3. On the Limits tab, change the quotas described at the beginning of this note.

    noteNote
    The maximum size for the Exchange mailbox store is 16 gigabytes.

Setup initialization error: Source \SQL2000_SP4\x86\Setup\Sqlspre.ini

You may receive this error when you try to install SQL Server 2000 Service Pack 4. It occurs when the Service Pack 4 Setup program tries to copy Setupsql.ini to the %Temp% folder, but cannot overwrite a pre-existing version of the file that is marked as read-only.

If you receive this error, browse to the %Temp% folder on your system drive, and either delete the pre-existing version of setupsql.ini or remove the read-only attribute. Then run SQL Server 2000 Service Pack 4 Setup again.

Setup Requirements Messages

The DNS domain name cannot contain DBCS (Double-Byte Character Set) or extended characters

Windows Small Business Server 2003 Setup cannot install Exchange or Windows SharePoint® Services during the upgrade because the DNS name for the internal domain contains nonstandard characters.

For more information about completing a new installation, see Chapter 3A, "New Installation," of Getting Started.

noteNote
The DNS domain name can only contain standard characters: A-Z, 0-9, and the hyphen (-).

The Microsoft Connector for POP3 Mailboxes no longer supports Authenticated POP or CRAM-MD5 encryption

This message appears on the Setup Requirements page of Setup if the Microsoft Connector for POP3 Mailboxes is installed, and you upgrade from Small Business Server 2000 to Windows Small Business Server 2003.

The message indicates that the authentication type for one or more mailboxes defined in the Microsoft Connector for POP3 Mailboxes was changed to basic authentication. The connector no longer supports Authenticated POP or CRAM-MD5 encryption. However, the connector does support Secure Password Authentication (SPA).

Client Computers

Microsoft Office Outlook® 2003 only supports client computers running Windows 2000 or Windows XP

To use Outlook 2003, you must upgrade client computers running earlier versions of Windows.

Installing Outlook 2003 on a computer running Microsoft Office XP or earlier results in the following issues

You will no longer be able to use Microsoft Word as an e-mail editor.

You will no longer be able to use the File, Send To menu command from Office applications.

To avoid these issues, either upgrade your earlier version of Microsoft Office to Microsoft Office 2003 or later, or do not upgrade to Outlook 2003.

To prevent client computers from upgrading to Outlook 2003, clear the Outlook 2003 check box when you run Assign Applications to Client Computers from Server Management, or run Upgrade Client Computers from the To Do List.

Logon may be slow or redirection might fail after enabling My Documents folder redirection

This is expected behavior the first time a user logs on to the server after My Documents redirection because it takes time to copy files and folders from the user's local My Documents folder to the redirected shared folder on the server. However, if this happens repeatedly, check the event log on the client computer for "Folder Redirection" errors. Such errors commonly occur when users exceed their assigned quota of disk space. If the size of a users My Documents folder exceeds the assigned quota size, folder redirection will fail.

To correct this issue, either reduce the size of the user's My Documents folder or increase the size of the user's disk quota on the server.

To increase the size of the user's disk quota on the server
  1. Click Start, and then click My Computer.

  2. Right-click the volume on which you want to change a user's disk quota, and then click Properties.

  3. On the Quota tab, click Quota Entries.

  4. Double-click the name of the user, increase the limit, and then click OK.

noteNote
Running the Change Users Permission Wizard resets this value to the default setting.

Unable to run the Windows Small Business Server 2003 Client Network Setup Wizard from the default Web site after upgrading from Small Business Server 2000

If you upgraded to Windows Small Business Server 2003 from a computer running Small Business Server 2000 with the Internet Information Services (IIS) Lockdown Wizard and URLScan security tool installed, executable (.exe) files are prohibited by default from being requested through the default Web site. As a result, if you run the Client Network Setup Wizard from a client computer, you receive the following error:

"Files that are critical to Client Setup cannot be copied to this client computer."

To resolve this problem, either remove the URLScan security tool from the IIS default Web site or modify the configuration of the tool to allow .exe files. An updated version of the URLScan security tool for Windows Small Business Server 2003 will be available on the Windows Small Business Server Web site (http://go.microsoft.com/fwlink/?LinkId=17117).

Beta or prerelease versions of Outlook are not updated to Outlook 2003

If you previously installed a beta or prerelease version of Outlook 2003 or any other Office 2003 application on a client computer, you must uninstall it before installing a newer version.

To determine which version of Outlook is installed on a client computer
  1. On the client computer, open Outlook.

  2. Click the Help menu, and then click About Microsoft Outlook. The version number appears at the top of the box.

To uninstall earlier versions of Outlook 2003 or other Office 2003 applications
  1. On the client computer, click Start, click Control Panel, and then double-click Add or Remove Programs.

  2. Click the program that you want to remove, and then click Change/Remove or Remove.

After uninstalling beta or prerelease versions of Office 2003 applications, you can assign the latest version to be installed on client computers.

To assign the latest version of Outlook 2003 to client computers
  1. On the server, click Start, and then click Server Management.

  2. In the console tree, click Client Computers.

  3. In the details pane, click Assign Applications to Client Computers.

  4. Follow the instructions in the Assign Applications Wizard to assign Outlook 2003 to the client computers.

Do not try to connect to a client computer you are currently using if it appears in the computer list in the Remote Web Workplace

Doing so may cause the client computer to become unstable and require you to restart it. This can occur if the client computer was connected to the computer running Windows Small Business Server 2003 during server Setup, and the name of the client computer is changed after Setup.

To correct this problem, delete the pointer (PTR) record for the original name of the client computer from the Reverse Lookup Zone of the DNS service on the server.

To delete the PTR record for the original client computer from the DNS Reverse Lookup Zone
  1. From the server, click Start, point to Administrative Tools, and then click DNS.

  2. In the console tree, double-click the name of your server, open the Reverse Lookup Zone folder, and then open the folder for the IP address of the subnet that contains the PTR record of the client computer that you want to delete.

  3. Right-click the PTR record of the client computer to be deleted, and then click Delete.

Unable to view some Web sites by using Internet Explorer for Macintosh

Some Web sites running on the server require an https:// connection using Secure Sockets Layer (SSL). Web sites that require SSL include Outlook Web Access and the Remote Web Workplace. If you use the Configure E-mail and Internet Connection Wizard to configure SSL and create a new certificate, you cannot view these Web sites by using the Internet Explorer for Macintosh Web browser.

To view these Web sites, you must either purchase a signed certificate from a trusted certification authority (CA) or use a different Web browser.

How to add a Windows server running in Terminal Server application sharing mode

For information about how to configure and use Terminal Server in a small business environment, see "Deploying Windows Server 2003 Terminal Server to Host User Desktops" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=17050).

Backup and Restore

Restoring your server

For information about how to restore your server following an event you cannot recover from, see Appendix F in Getting Started. This documentation can also be found in Restrdoc.htm in the \Docs folder on Windows Small Business Server 2003 Disc 1.

Remote Access

Unable to download Connection Manager from the Remote Web Workplace after upgrading from Small Business Server 2000

If you upgraded to Windows Small Business Server 2003 from a computer running Small Business Server 2000 with the Internet Information Services (IIS) Lockdown Wizard and URLScan security tool installed, executable (.exe) files are prohibited by default from being requested through the default Web site. As a result, if you try to download Connection Manager from the Remote Web Workplace, you receive a "404 File Not Found" error.

To resolve this problem, either remove the URLScan security tool from the IIS default Web site or modify the configuration of the tool to allow .exe files. An updated version of the URLScan security tool for Windows Small Business Server 2003 will be available on the Windows Small Business Server Web site (http://go.microsoft.com/fwlink/?LinkId=17117).

Additional Resources

To review the most recent hardware and application compatibility information, see the Windows Catalog Web site (http://go.microsoft.com/fwlink/?LinkId=3410).

To search for technical support information and self-help tools for Microsoft products, see the Knowledge Base on the Microsoft Product Support Services Web site (http://go.microsoft.com/fwlink/?LinkId=4441).

To obtain the latest product updates, see the Windows Update Web site (http://go.microsoft.com/fwlink/?LinkId=284).

Copyright Notice

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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft