Windows Small Business Server 2003
Release Candidate Release Notes

July 2003

Web statistics are not appearing in the server usage report

This can occur if the Web Usage Logging service stopped running. This may happen after running the Configure Internet and E-mail Connection Wizard or the Routing and Remote Access Configuration Wizard.

To correct this issue, restart the Routing and Remote Access and Web Usage Logging services if they are not running.

To restart the Routing and Remote Access and Web Usage Logging services

1. In the Monitoring and Reporting snap-in in Server Management, click View Services.
2. In the list of services, ensure that the Routing and Remote Access service is started. If it is not, right-click the service, and then click Restart.
3. Ensure that the Web Usage Logging service is started. If it is not, right-click the service, and then click Restart.

Web sites are not accessible from the Internet when using Internet Security and Acceleration Server 2000 after using the Change IP Address Tool

This occurs because the Change IP Address Tool does not update the DNS Address (A) record for publishing.yourdomain.local (where yourdomain.local represents your local Active Directory domain name).

To update the DNS address for publishing.yourdomain.local

1. Click Start, point to Administrative Tools, and then click DNS.
2. In the console tree, double-click the name of your server, double-click Forward Lookup Zones, and then click the name of your domain.
3. In the details pane, right-click the (A) record for publishing, and then click Properties.
4. On the Host (A) tab of the Server Properties dialog box, change the IP address to that of the new local IP address of the server.

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

When 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}

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

Welcome to the Release Candidate release notes for Windows Small Business Server 2003.

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.

Download the latest release notes

To download an updated version of these release notes, visit the Windows Small Business Server Community Web site. (http://go.microsoft.com/fwlink/?LinkId=16919) The update may contain additional critical information that was not available when Windows Small Business Server 2003 Release Candidate 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 uninterruptable 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.

Upgrading Windows Small Business Server 2003 Beta 1 to Release Candidate is not supported

For information about how to perform a new installation of Windows Small Business Server 2003 Release Candidate, see Chapter 3 in Getting Started.

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

The Macintosh OS 10.2 operating system uses the .local extension for its Rendezvous service. As a result, client computers running OS 10.2 will be unable to discover other computers that are members of a Windows Small Business Server network that uses the .local extension.

If your Windows Small Business Server network contains client computers running Macintosh OS 10.2 or later, change the default domain name during Setup to use a domain extension other than .local. For example, you could use a .lan or .office extension.

For more information, visit the Apple Web site (http://www.apple.com)and search the Knowledge Base for the article "Mac OS X 10.2: About Your Computer's Rendezvous Name."

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.

Monitoring alerts are not being generated after importing a Health Monitor configuration

Typically, this issue occurs because the imported Health Monitor configuration contains actions that point to resources that do not exist on the network. For example, an imported action may point to an e-mail server that is a member of the network from which the configuration was exported.

To work around this issue, review the imported actions and make corrections to the configuration as necessary.

To review and modify imported actions

1. Click Start, point to Administrative Tools, and then click Health Monitor.
2. In the console tree, click Actions.
3. In the details pane, right-click an action, and then click Properties.
4. Review the settings on each tab, and modify them as necessary. For example, you can update the SMTP server to send e-mail, or you can update file paths for scripts.
5. Repeat Steps 3 and 4 for each action.

Server performance and usage reports are not being received after restoring from backup

Windows Small Business Server uses scheduled tasks to automate Backup and Monitoring features. After restoring your server from backup, these scheduled tasks do not run. This occurs because the "Run as" credentials for scheduled tasks are not restored with the backup.

To resolve this issue, open the Scheduled Tasks tool, and specify the "Run as" credentials for each of your scheduled tasks.

To specify "Run as" credentials for the Backup and Monitoring scheduled tasks

1. Click Start, point to Control Panel, right-click Scheduled Tasks, and then click Open.
2. Right-click Back Up Small Business Server, and then click Properties.
3. On the Task tab, for Run as, type System, and then set a blank password.
4. Repeat steps 2 and 3 for each of the following scheduled tasks if they are listed:
   • SBSDataCollector
   • Collect Server Performance Data
   • Collect Usage Data
   • Small Business Server - Server Performance Report
   • Small Business Server - Server Usage Report
   • ShadowCopyVolume

Note

• If you scheduled other tasks, you must specify the "Run as" credentials for those also.

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 Restore.htm located in the \docs folder on Windows Small Business Server 2003 Disc 1.

Windows Small Business Server Backup does not run automatically after restoring from backup

Windows Small Business Server uses scheduled tasks to automate Backup and Monitoring features. After restoring your server from backup, these scheduled tasks do not run. This occurs because the "Run as" credentials for scheduled tasks are not restored with the backup.

To resolve this issue, open the Scheduled Tasks tool, and specify the "Run as" credentials for each of your scheduled tasks.

To specify "Run as" credentials for the Backup and Monitoring scheduled tasks

1. Click Start, point to Control Panel, right-click Scheduled Tasks, and then click Open.
2. Right-click Back Up Small Business Server, and then click Properties.
3. On the Task tab, for Run as, type System, and then set a blank password.
4. Repeat steps 2 and 3 for each of the following scheduled tasks if they are listed:
   • SBSDataCollector
   • Collect Server Performance Data
   • Collect Usage Data
   • Small Business Server - Server Performance Report
   • Small Business Server - Server Usage Report
   • ShadowCopyVolume

Note

• If you scheduled other tasks, you must specify the "Run as" credentials for those also.

Restoring your server on different hardware

When restoring your server, some hardware components must be the same as those of the computer from which the backup was performed. You cannot restore your server to a new or upgraded computer if the computer contains any of the following hardware variances:

• A different SCSI controller (going from SCSI to IDE is acceptable)
• A different type of processor
• A different number of processors
• An insufficient amount of disk space
• A different drive letter specification for the boot partition

Other hardware requirements may exist in this and future releases of Windows Small Business Server. For best results, restore the server to the same brand and model of computer from which it was backed up.

Backing up data to a FAT partition may fail

If you use the Backup Configuration Wizard to back up your server to a FAT partition, backup may fail and you may get the error "End of media encountered."

This commonly occurs because the size of the backup file exceeds the 4-gigabyte file size limitation on FAT partitions.

To resolve this issue, convert the FAT partition to NTFS.

For information about how to convert a FAT partition to NTFS, search for article Q314097 in the Knowledge Base at the Microsoft Product Support Services Web site. (http://go.microsoft.com/fwlink/?LinkId=4441)

Users' My Documents folders do not redirect to the specified location after you run the Client Document Redirection tool

When you use the Client Document Redirection tool to redirect users' My Documents folders to a different network folder, the folder may not be redirected to that location.

This problem typically occurs when adequate permissions are not set on the network folder that My Documents is being redirected to.

To set permissions on the network folder where each user's My Documents folder is redirected

1. Click Start, and then click Windows Explorer.
2. Right-click the folder to which you redirected the user's My Documents folder, and then click Sharing and Security.
3. On the Sharing tab, ensure that Share this folder is selected, and then click Permissions.
4. Add the following users and groups if they are not listed, and then assign them Full Control permissions:
   • Domain Users
   • Domain Admins
   • SBS Folder Operators
5. On the Security tab, add the following users and groups if they are not listed, and then assign them Full Control permissions:
   • Domain Admins
   • SBS Folder Operators
   • System
6. Click Advanced.
7. Clear the check box for Allow inheritable permissions from the parent to propagate to this object and all child objects, and then click Copy.
8. Click Add, add the Domain Users group, and then select Allow for the following permissions:
   • Traverse Folder/Execute File
   • List Folder/Read Data
   • Read Attributes
   • Read Extended Attributes
   • Create Folders/Append Data
   • Read Permissions

Note

• It is recommended that you remove Everyone, Administrators, and Users from the list of group and user names.

Previous versions of Outlook are not updated to Microsoft Office Outlook 2003

If you previously installed a beta or release candidate version of Outlook 2003 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

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 release candidate versions of Outlook 2003, 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.

Outlook 2003 supports only client computers running Windows 2000 or Windows XP

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

Do not try to connect to a client computer running Windows XP Professional if it appears in the computer list in the Remote Web Workplace

When you click Connect to my computer at work or Connect to Client Desktops from the Remote Web Workplace while logged on to a client computer running Windows XP Professional, the name of the client computer you are using to access the Remote Web Workplace may appear in the list of computers that you can connect to. If it does, do not try to connect to it. Doing so may cause the client computer to be unstable and require you to restart it. This can occur if a physical network connection exists during Setup between the client computer running Windows XP Professional and the computer running Windows Small Business Server 2003, 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.

Using Terminal Server in a small business environment

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

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

Some Web sites running on the server require 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 Certificate Authority (CA) or use a different Web browser.

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)

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results of the use of this document remains with the user. 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.

© 2003 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows NT, Windows Server, and Outlook 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.