Microsoft Windows Small Business Server 2003

Release Notes

Microsoft Corporation

Published: May 2005

Version: 3

Download the most recent Release Notes

To download the most recent version of these notes, visit the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=41392).

Create a backup of all Windows SBS 2003 Group Policy objects (GPOs) on your server before you upgrade to Windows SBS 2003 with SP1

Before you upgrade to Windows SBS 2003 with SP1, you should create a backup of all your Windows SBS 2003 GPOs on your server. Therefore, if an administrator modified the settings of these GPOs, you can restore them to get back the customized GPO settings.

To create a backup of all Windows SBS 2003 Group Policy objects

  1. Click Start, and then click Server Management.

  2. In the console tree, click Advanced Management, double-click Group Policy Management, double-click Forest: <domainname>, double-click domainname, right-click Group Policy Objects, and then click Back Up All.

  3. In the Back Up Group Policy Object dialog box:

    1. Under Location, enter the name of the folder in which you want to store the backup of the GPOs.

    2. Under Description, enter a description (for example, SBS GPOs) to easily identify the file that contains the backup.

    3. Click Backup.
To restore a Windows SBS 2003 Group Policy object

  1. Click Start, and then click Server Management.

  2. In the console tree, click Advanced Management, double-click Group Policy Management, double-click Forest: <domainname>, double-click domainname, double-click Group Policy Objects, right-click the GPO that you want to restore from a backup, and then click Restore From Backup.

  3. In the Restore Group Policy Object Wizard:

    1. On the Backup location page, enter the name of the folder that contains the backup, and then click Next.

    2. On the Source Group Policy Object page, under Backed Up Group Policy Objects, select the backup from which you want to restore the GPO settings, and then click Next.

    3. Click Finish.

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.

SP1 for Windows SBS might reset some customized values to the original default settings

Windows SBS includes default values that are designed to meet the needs of small businesses. When you update to Windows SBS 2003 with SP1, some of these values are reset to the defaults. If you customized any of these values, you should customize them again after you install SP1 for Windows SBS.

The following table contains a list of values that are reset to the defaults.

Title Description Options

User quota settings for Windows SBS 2003 User Templates are reset when you upgrade to Windows SBS 2003 with SP1

When you upgrade to Windows SBS 2003 with SP1, the user quota settings for Small Business Server user templates (User, Administrator, Power User, and Mobile User) are reset. Therefore, if you customized the quota settings of these user templates, you should customize them again after you upgrade to Windows SBS 2003 with SP1.

Note   Upgrading to Windows SBS 2003 with SP1 does not reset user quota settings for existing users. Only new user accounts are affected by this issue.

After you upgrade to SBS 2003 with SP1, verify the user quota settings and ensure that they are set to the values you expect. If any of them are set to different values, customize the user quota for that user again by using the procedure "To modify individual user quota settings," which follows this table in the section, "User quota settings for Windows SBS 2003 User Templates are reset when you upgrade to Windows SBS 2003 with SP1."

Some customized settings for Windows SBS Web sites are overwritten when you upgrade to Windows SBS 2003 with SP1.

When you upgrade to Windows SBS 2003 with SP1, some of the files necessary to create the default Windows SBS Web sites, such as Remote Web Workplace, are updated and replaced. As a result, customizations that you have made to these files are lost. Customizations to your internal Web site (http://companyweb) or Business Card Web site (http://servername) are preserved.

If you have customized any of the default Windows SBS Web sites, you should make a backup of your customizations before you upgrade to Windows SBS 2003 with SP1, and then re-implement the customizations after you complete the upgrade. It should not be necessary to restore changes to your internal Web site (http://companyweb) or Business Card Web site (http://servername).

User quota settings for Windows SBS 2003 User Templates are reset when you upgrade to Windows SBS 2003 with SP1

Note   To complete this procedure, you must be logged on as a member of the Domain Admins security group.

To modify user disk space limits and warning levels for an individual user

  1. Click Start, and then click My Computer.

  2. Right-click the volume for which you want to modify quota values, and then click Properties.

  3. In the Properties dialog box, click the Quota tab.

  4. On the Quota page, click Quota Entries.

  5. In the Quota Entries window, click the entries for the users whose options you want to modify, and on the Quota menu, click Properties.

  6. In the Quota Settings dialog box, modify any of the following options you want to change, and then click OK:

    Do not limit disk usage. Tracks disk-space usage without limiting disk space.

    Limit disk space to. Activates fields for limiting disk space and for setting warning levels. Type a numeric value in the text field, and then select a disk-space limit unit from the drop-down list. You can use decimal values (for example, 20.5 MB).

    Note   If the volume is not formatted with the NTFS file system, or if you are not a member of the Administrators group, the Quota tab is not displayed in the Properties dialog box for that volume.

If you have moved the Exchange Public Folders database from a previous Windows SBS 2003 installation to a new Windows SBS 2003 installation, you might receive an error when you run Windows SBS 2003 SP1 Setup on the new installation

Windows SBS 2003 SP1 Setup might display an error message that refers to the Setup Error Log (setup.log). If it does, it then appears to finish successfully, but in fact there are two problems: The Exchange Public Folders might refer to objects that no longer exist in the directory, and Microsoft SQL Server Service Pack 4 is not applied to any MSDE instances on the server.

Note   A new installation occurs in either of the following scenarios:

  • You install a new copy of Windows SBS 2003 on the same computer as a previous installation of Windows SBS 2003.

  • You install a new copy of Windows SBS 2003 on a different computer.

Note   If you have moved your Exchange Public Folders database using only the instructions in the Windows SBS 2003 migration documents, you will not encounter this problem. The migration documents are available at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=48139).

To resolve this problem, regenerate the Public Folder Active Directory objects, and then run Windows SBS SP1 Setup again.

To regenerate Public Folder Active Directory objects

  1. On the computer running Windows SBS 2003, click Start, point to All Programs, point to Microsoft Exchange, and then click System manager.

  2. Expand Folders.

  3. Expand Public Folders.

  4. Right-click the first Public Folder, and then click All Tasks.

  5. Click Mail Enable if it is available. If Mail Enable is not available, right-click the next Public Folder.

  6. Repeat for all Public Folders.

  7. Run Windows SBS SP1 Setup again.

Outlook profile is not automatically created for new users on a computer running Windows Server 2003 or Windows 2000 Server in Terminal Server application-sharing mode

When you apply SP1 for Windows SBS 2003, additional servers running either the Windows Server 2003 or Windows 2000 Server operating system in Terminal Server application sharing mode do not automatically create an Outlook profile for new users. This is because SP1 for Windows SBS 2003 changes the profile-configuration tool to work with Outlook 2003 with Service Pack 1.

To resolve this problem, use an account with Local Administrator privileges to log on to the server running in Terminal Server application sharing mode. Install SP1 for Outlook from \\ServerName\ClientApps\Outlook2003\setup.exe, where ServerName is the name of the computer running Windows SBS 2003 with SP1.

Notes

  • If the computer running Windows Server in Terminal Services application-sharing mode has Office 2003 installed on it, do not use the method above to resolve this issue. Instead, apply SP1 for Office 2003 from the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=24134.

  • This issue does not affect additional computers running Windows Server in Terminal Services application sharing mode if you add those computers to your Windows SBS 2003 network after you apply SP1 for Windows SBS 2003.

  • This issue does not affect Outlook profiles for existing users on computers running Windows Server in Terminal Services application-sharing mode.

The titles of the performance and usage reports include the server name rather than the organization name

After you install SP1 for Windows SBS, the organization name is replaced with the server name in the title of the performance report and the usage report.

If you prefer to see the organization name in these reports, you can change the RegisteredOrganization entry in the registry.

Caution:
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 RegisteredOrganization registry entry

  1. Click Start, click Run, type regedit in the Open box, and then click OK. Registry Editor opens.

  2. Navigate to and click the following registry subkey:HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer

  3. In the details pane, double-click RegisteredOrganization.

  4. Enter your organization name in the Value data field, and then click OK.

  5. Click File, and then click Exit to close Registry Editor.

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).

Note   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.

"Windows Small Business Server has encountered an error" appears when you install Windows SBS 2003 SP1

If you have not installed the Microsoft Office Outlook 2003 component for Client Deployment on your server running Windows SBS 2003, you might receive the error message “Windows Small Business Server has encountered an error” when you install Windows SBS 2003 SP1.

This error is benign, and you can safely ignore it.

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.