Small Business Server 2000

Release Notes

December 2000

This document contains important, late-breaking information about Microsoft Small Business® Server 2000. Before installing Small Business Server, please read this entire document. It contains critical information that will help you ensure proper installation and use of the product.

These materials are provided “as-is,” for informational purposes only.

Neither Microsoft nor its suppliers makes any warranty, express or implied, with respect to the content of these materials or the accuracy of any information contained herein, including, without limitation, the implied warranties of merchantability or fitness for a particular purpose. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation may not apply to you.

Neither Microsoft nor its suppliers shall have any liability for any damages whatsoever including consequential incidental, direct, indirect, special, and loss profits. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation may not apply to you. In any event, Microsoft's and its suppliers' entire liability in any manner arising out of these materials, whether by tort, contract, or otherwise shall not exceed the suggested retail price of these materials.

CONTENTS

Before Installing Small Business / Small Business Server 2000...

Suite Requirements.

Server Upgrades.......

Installing Small Business/Small Business Server 2000..............

Connectivity....

Management Consoles........

Server Health and Monitoring

Shared Fax Service..........

Shared Modem Service..........

SQL Server 2000..............

Exchange 2000 Server............

Microsoft Connector for POP3 Mailboxes.......

Internet Security and Acceleration Server 2000...

Client Notes....

Uninstalling Applications....

Before Installing Small Business Server 2000

Download Updated Release Notes from the Web

It is recommended that you go to http://www.microsoft.com/sbserver/relnotes.htm and download an updated version of these Release Notes. The update may contain additional information critical to your installation that was not available when Small Business Server 2000 was released to manufacturing.

Before Running Setup, Fill Out the ‘Before You Begin’ Card

Before running Small Business Server 2000 Setup, fill out the Before You Begin card. Small Business Server Setup will ask you for information about your network, and the Before You Begin card ensures that you have all the necessary setup information on hand. If the Before You Begin card is not available, you can also fill out the worksheets in Appendix C of the Small Business Server 2000 Planning and Installation guide.

Latest Windows 2000 Service Packs and Updated Security Fixes

Small Business Server 2000 includes Windows 2000 Service Pack 1. Later versions of Windows 2000 Service Packs as well as security updates can be obtained from the Microsoft Web site at:
http://www.microsoft.com/windows2000/downloads/default.asp

Connect or Disable Network Adapters Before Running Setup or the Internet Connection Wizard

Windows 2000 automatically detects network adapters on a domain controller that is not connected to an active network, and assigns them a fixed IP address of 169.254.x.x. If either Small Business Server Setup or the Small Business Server Internet Connection Wizard is run while any network adapters have this IP address, some network services, such as DNS or WINS, will not be configured correctly. If this happens, you may incur networking errors.

To avoid this issue, ensure that all network adapters are either disabled or are connected to an active network segment, such as a hub or router, before running Small Business Server Setup or the Small Business Server Internet Connection Wizard.

Unplug UPS During Windows 2000 Portion of Setup

Windows 2000 hardware detection can cause some Uninterruptible Power Supplies (UPS) to switch to battery mode. This may cause setup to fail. Unplug any UPS devices during installation of Windows 2000, and then install the UPS after completing Windows 2000 Setup.

Bootable Startup Disks for DVD are Not Interchangeable with Startup Disks for CD-ROM

Both the CD-ROM version of Small Business Server and the DVD version contain a BOOTDISK directory providing users with utilities to create bootable startup floppy disks. Startup disks created for the CD-ROM version of Small Business Server, however, will not permit you to install the DVD-ROM version, or vice versa. You must create bootable startup disks from the same medium that you use for your installation.

Internet Explorer 5.0 or Later Required to View Small Business Server Tours and Online Help Topics in Windows NT 4.0

Small Business Server 2000 tours and Online Help require that Internet Explorer 5.0 or later be installed on the computer. If you attempt to open any Small Business Server 2000 tour or Online Help on a computer running Windows NT 4.0 or earlier, the following error message appears:

“Error: automation server cannot create objects.”

Download the latest version of Internet Explorer from: http://www.microsoft.com/windows/ie/

Small Business Server Setup Will Not Run on Windows 95 Without Internet Explorer 3.02 or Higher Installed To install Small Business Server 2000 on a computer running Windows 95, you must have Microsoft Internet Explorer 3.02 or higher installed.

Suite Requirements

‘Apply Windows 2000 Service Pack 1 to Windows 2000 Server Before Upgrading to Small Business Server 2000’

If you have installed an evaluation edition of Windows 2000 Server and want to upgrade to Small Business Server 2000, you must install Windows 2000 Service Pack 1 first.

To install Windows 2000 Service Pack 1, run the Sp1i386full.exe file located in the \Win2K_SP1\i386 folder of Small Business Server 2000 Disc 1.

Exchange Internet Mail Connector Installed

When upgrading from Exchange Server 5.5 to Exchange 2000 Server, you must remove the Internet Mail Connector (IMC). You should record any custom IMC configuration properties before deleting it.

To record the IMC information

1. Open Microsoft Exchange Administrator.

2. Expand Servername, expand Configuration, and then click Connections.

3. Double-click Internet Mail Service, and record the following settings:

· On the Connections tab, note whether message delivery is using DNS or if it is configured to forward all messages to host; if the latter, note the host name.

Note if the dial using checkbox is selected. If it is, note which connection is being used.

Under Specify by E-Mail domain, click E-Mail Domain. Note the domains listed.

· On the Dial-Up Connections tab (for dial-up connections only) note the dial-up schedule, and the information displayed under Mail Retrieval and Logon Information.

· On the Routing tab, note the domains listed under routing. This is typically your external domain name.

· On the Address space tab, note the entry listed under ‘Address'. This is typically listed as *.

4. After recording all this information, delete the connection named Internet Mail Service.

‘This Computer is Running an Evaluation Version of Windows 2000 Server’

If you receive this message on the Suite Requirements page of Small Business Server Setup, you have the Not for Resale version of Windows 2000 Server installed. Small Business Server cannot be installed on this version of Windows. Before you can install Small Business Server, first install a new version of Windows 2000 Server from Small Business Server Disc 1.

‘Network Properties Page is Open’

Small Business Server 2000 Setup cannot install or configure networking components if the Network Properties page is open. Close the page and restart setup.

Small Business Server Upgrade Language Mismatch

If you are running Small Business Server 4.5 in one language, you cannot upgrade to Small Business Server 2000 in a different language. For example, English Small Business Server 4.5 cannot be upgraded to German Small Business Server 2000.

Windows 2000 Server Evaluation Copy in One Language Cannot Be Upgraded to Small Business Server 2000 in a Different Language

If you are running an evaluation copy of Windows 2000 Server in one language, you cannot upgrade it to Small Business Server 2000 in a different language. For example, German Small Business Server 2000 cannot upgrade an evaluation copy of English Windows 2000.

After Upgrading to Windows 2000 Server, Session Must Be Set to ‘Install’ Mode

For you to install Small Business Server on a Windows 2000 Server running Terminal Services in Application Server mode, Windows 2000 Server must be running in ‘install’ mode to install applications on the computer. After the upgrade to Windows 2000 Server, you will receive a message stating that you need to launch setup from the Add/Remove Programs in Control Panel. To continue with setup, do one of the following:

1. Re-launch setup from Add/Remove Programs in Control Panel.

2. Change the mode of the server from 'execute' to 'install' by running change user /install from a command prompt.

Note: If setup reboots again you will receive a message that you must launch setup from Add/Remove Programs in Control Panel. In this case, perform option 2 from above and then run Small Business Server Setup using the temporary shortcut created in <Systemdrive>\Documents and Settings\All Users\Start Menu\Programs\Startup. This will re-launch setup from the place it was interrupted.

Server Upgrades

Windows 2000 Components

Configure DHCP Scope Options After Upgrading from Small Business Server 4.5 to Small Business Server 2000

DHCP scope options are not set when upgrading from Small Business Server 4.5 to Small Business Server 2000. After completing the upgrade, configure these options manually from the DHCP snap-in.

To configure DHCP Scope Options

1. Open the DHCP management console. (Click Start, point to Programs, point to Administrative Tools, and then click DHCP.)

2. In the Console Tree, expand the node that represents your DHCP server, and then expand Scope.

3. Right-click Scope Options, and then click Configure Options.

4. Under Available Options, select and configure the following options:

003 Router - For IP address, specify the IP address of your Small Business Server computer.

006 DNS - For IP address, specify the IP address of your Small Business Server computer.

044 WINS/NBNS Servers - For IP address, specify the IP address of your Small Business Server computer.

046 WINS/NBD Node Type - For Byte, specify 0x1 (type B).

5. After configuring scope options, click OK to save the changes.

DHCP Server Unreachable if IP Address is Changed During Upgrade from Windows 2000

When upgrading to Small Business Server 2000, if you change the IP address of a Windows 2000 Server computer running DHCP, you will receive an error stating that the DHCP server is unreachable when you attempt to access the DHCP snap-in.

To work around this problem

1. In the Console Tree, right-click DHCP, and then click Manage authorized servers.

2. Select your server computer in the list, and then click OK.

The new DHCP server will be added to the Console Tree. The old IP address will be shown with an error icon.

Note: Even though the old IP address still appears as a node in the Console Tree, DHCP clients are being assigned IP addresses correctly according to the scope defined for the new DHCP server.

You Must Reapply Windows 2000 Server Service Pack 2 After Setup is Complete

You currently have a Service Pack later than Service Pack 1 installed on your evaluation copy of Windows 2000 Server. Upgrading to Small Business Server will upgrade the evaluation copy of Windows 2000 Server to the full version of Windows 2000 Server with Service Pack 1. You will need to reapply your current Service Pack when Small Business Server installation is complete.

Small Business Server Unable to Resolve DNS Names

If you are installing Small Business Server 2000 on a computer running Windows 2000 Server, and that computer is configured as the root of the active directory forest but is using DNS services on a different computer, Internet Protocol (TCP/IP) Properties will be configured to point the Local Area Network (LAN) back to itself for DNS services. To correct this problem, you must manually change the IP Address for the DNS server to point to the computer that is providing DNS services.

To change the IP addresses for DNS servers

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click the icon for your Local Area Network, and then click Properties.

3. In the list of components, select Internet Protocol (TCP/IP), and then click Properties.

4. For Preferred DNS server, specify the IP address for the computer that is providing DNS services.

5. Click OK to save your changes.

6. Close the Local Area Connection Properties page.

Error Message: ‘DNS cannot be configured for Domain <YourDomain>, but DNS Service Has Been Successfully Installed. Error: DNS Zone Already Exists’

This error appears if you have already configured DNS on Small Business Server 4.5 and have specified the same domain name during Small Business Server 2000 Setup. It is expected behavior. If you see this message, click OK to continue with setup. DNS will function properly.

WINS Behavior on Small Business Server 2000 with DHCP Installed

If you upgrade a Windows 2000 computer that is running DHCP Server without Windows Internet Naming Service (WINS) to Small Business Server 2000, setup will not install WINS. Rather, it will configure the Internet Protocol (TCP/IP) properties to point to the computer's internal static IP address. In this scenario, you can either clear the WINS IP address in the network settings, or install WINS.

To clear the WINS IP address

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click your internal connection, and then click Properties.

3. Select Internet Protocol (TCP/IP), click Properties, and then click Advanced.

4. Click the WINS tab, select the IP address listed, and then click Remove.

5. Click OK in each open dialog box.

To install a WINS server

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.

3. Under Components, click Networking Services.

4. Click Details.

5. Under Subcomponents of Networking Services, click Windows Internet Name Service (WINS), and then click OK.

If you install Small Business Server 2000 on a network that already has a computer running DHCP, WINS will be installed on the Small Business Server computer. Since DHCP is running on another computer, the WINS entry is not added to network settings.

To add the WINS IP address to network settings

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click your internal connection, and then click Properties.

3. Select Internet Protocol (TCP/IP), click Properties, and then click Advanced.

4. Click the WINS tab, and then click Add.

5. Type the IP address for the WINS server, and then click Add.

6. Click OK in each open dialog box.

Small Business Server Setup

Small Business Server Administration Sub-Component Fails to Install if There is no Web Site 1 in the Metabase

If you do not have a Web site in your metabase when you run Small Business Server Setup, the administration sub-component will fail to install. To address this issue, complete setup and then create a new Web site with the Internet Information Services snap-in in the Small Business Server Administrator Console. When this Web site is created, restart Small Business Server setup in Maintenance mode, and select to re-install the administration sub-component.

Note: The administration component is a sub-component of the Small Business Server component.

To create a new Web site

1. In the Small Business Server Administrator Console, expand the Internet Information Services snap- in.

2. Right-click Your Computer, point to New, and then click Web Site.

3. Follow the on-screen instructions to complete the Web Site Creation Wizard.

Small Business Server Upgrade Language Mismatch

Error When Using Setup to Change the Install Action for a Component

When attempting to change the install action for a component, if you encounter a problem on the Component Selection page of setup, perform one of the following workarounds:

· If you have made changes for other components, complete setup so that you do not lose the changes, then correct the problem, and then re-run setup to complete the action for the component that created the install problem.

· If you have not made changes to other components, cancel setup, correct the problem, and then re-run setup to perform the action for the component that created the install problem.

SQL Server 2000

SQL Server 7.0 OLAP with Service Pack 2 Cannot be Upgraded to Analysis Services via BackOffice Server Setup

If you are running SQL Server 7.0 OLAP with Service Pack 2, you cannot upgrade to Analysis Services using BackOffice Server setup. To upgrade to Analysis Services, you must run native SQL Server setup from BackOffice Server Setup Disc 2 and install Analysis Services manually.

SQL Server 2000 and English Query Install in Default Directories Even If Installation Path is Changed

When upgrading to BackOffice Server 2000, SQL Server 2000 and English Query will be installed to their default directories even if you change the installation path. This does not affect the functionality of SQL Server or English Query.

MSSQLSERVER Service Must Be Running Before Upgrading to Small Business Server 2000

If SQL Server 2000 is already installed on a computer that will be upgraded to Small Business Server 2000, start the MSSQLSERVER service before running Small Business Server 2000 Setup. Otherwise, setup may fail.

Restart After Applying Service Packs for SQL 7.0 or English Query

If you are installing Service Packs on SQL Server 7.0 or English Query, before upgrading to SQL Server 2000, you should restart the computer upon conclusion. This ensures that all Service Pack updates and file changes have occurred before running BackOffice Server 2000 setup.

Upgrading SQL Server 2000 Evaluation Version to SQL Server 2000 Standard Version

When upgrading from the evaluation (time-bombed) version of Small Business Server 2000 to the standard (full) version of the product, set the install action for SQL Server 2000 to “Upgrade.” Otherwise, the SQL Server 2000 time bomb will not be removed.

Critical Error Message: ‘Could Not Open File SQLCTR60.DLL’

When installing the SQL Server 6.5 Service Pack 5 component during setup, the following critical error message may appear:

“A critical error has occurred.

Could not open the file named:

‘<drive>:\MSSQL\BINN\SQLCTR60.DLL’ ”

If you encounter this error, click Retry. The file will be added the next time the computer is restarted.

Innocuous Event Viewer Errors Occur When Not Upgrading to SQL Server 2000

Not upgrading to SQL Server 2000 from a Small Business Server 4.5 computer running SQL Server 7.0 will cause application event errors that will not affect the SQL Server application. Some of these errors occur when Performance Monitor counters are not properly implemented by the open applications that are running.

The following event viewer errors are innocuous

Source Event ID Description

SQLCTR70 1001 SQL Performance DLL Open function.

SQLCTR70 1001 Shared Memory Segment

Perflib 1008 Open Procedure for service MSSQLServer

To resolve this issue, you can either install Service Pack 2 for SQL Server 7.0, or upgrade to SQL Server 2000.

World Wide Web Publishing Service May Not Restart After ISA Server Installation

The World Wide Web Publishing Service (W3SVC) may not restart after Internet Security and Acceleration (ISA) Server is installed. Before starting this service, ensure that you have not configured the Web publishing service to use port 8080, because ISA Server uses this port.

Autodial Settings Are Not Migrated When Upgrading Proxy Server 2.0 to ISA Server

Autodial and Dial-on-Demand settings are not migrated when upgrading from Proxy Server 2.0 to ISA Server 2000. After completing the upgrade, you can reconfigure this functionality by running the Small Business Server Internet Connection Wizard.

After Upgrading to Small Business Server 2000, Microsoft Search Service May Not Start Automatically

After upgrading from Small Business Server 4.5 to Small Business Server 2000, the Microsoft Search Service may need to be manually started and then set to start automatically.

To start the Microsoft Search Service and set it to start automatically

1. Click Start, point to Programs, point to Administrative Tools, and then click Services.

2. Right-click Microsoft Search, and then click Properties.

3. From the Start type list, select Automatic, and then click Start.

4. When the service has started, click OK.

Microsoft Exchange Server

Do Not Overwrite Dll Files When Upgrading from Exchange 5.5 with Service Pack 4 to Exchange 2000 Server

During Small Business Server 2000 Setup, when upgrading Exchange 5.5 with Service Pack 4 to Exchange 2000 Server, you may be asked to overwrite existing Exchange .dll files. To prevent the .dll files from being overwritten, click No or Do not overwrite all. Overwriting the .dll files causes setup to fail.

If Exchange 5.5 Upgrade Fails You Must Run Disaster Recovery to Re-run Setup

If the upgrade from Exchange Server 5.5 to Exchange 2000 Server fails, to run Exchange 2000 Setup again, you must run Exchange 5.5 disaster recovery.

Only Previously Installed Exchange Server Components Can be Upgraded

When upgrading Small Business Server 4.5 to Small Business Server 2000, you will only be able to upgrade Exchange Server components previously installed on the server computer. If you want to install new Exchange Server 2000 components, complete the upgrade, and then run Small Business Server 2000 Setup in Maintenance mode to install the new components.

Message: ‘A Valid Ordering Could Not Be Found’

When upgrading to Small Business Server 2000, if the following conditions are true, a message appears stating “A Valid Ordering Could Not Be Found”:

· Exchange Server 5.5 is installed on the server computer.

· Small Business Server 2000 is installed without SMTP service or Exchange 2000 Server.

· You are re-running Small Business Server Setup in maintenance mode to upgrade to Exchange 2000 Server.

To address this message, on the Component Selection page of Small Business Server Setup, set the action to Install for the Internet Information Services (IIS), SMTP Services component.

Numerous Event Viewer Errors Following Upgrade to Exchange 2000 Server

After you upgrade Exchange Server 5.5 to Exchange 2000 Server, you may receive numerous Event Viewer errors because old performance counters from Exchange 5.5 are attempting to load. To correct this problem, manually install the counters associated with the Exchange Database Engine.

To manually install Exchange Database Engine counters

· At the command prompt, change to the Exchsrvr\Bin folder, type lodctr eseperf.ini, and then press Enter.

For more information about this issue, refer to Knowledge Base article Q273177 at:
http://support.microsoft.com/support/kb/articles/Q273/1/77.ASP

Exchange LDAP Event Log Error 10048

After upgrading to Exchange 2000 Server, the following error may appear in the Application event log:

“Source MSExchangeDS

Category: LDAP Interface

Description: Register LDAP Port Failed with error 10048. The LDAP SSL Server is not available. Make sure port number 636 is not in use by another application”

This was an issue when running Exchange 5.5 on a Windows 2000 Server domain controller. If you have upgraded to Exchange 2000 Server, you may safely disregard this error.

SBSETRN.exe Mail Connections are Not Compatible with Small Business Server 2000

Small Business Server 4.5 mail connections using Sbsetrn.exe to download mail from an ISP are no longer supported in Small Business Server 2000. Before upgrading to Small Business Server 2000, contact your ISP to determine what other mail download options are available to you.

Small Business Server

Re-distributable Components May Require Windows 2000 Service Pack 1

Some of the re-distributable components included with Small Business Server 2000 require Windows 2000 Service Pack 1, which is automatically installed by Small Business Server Setup. If you plan to install any of these components on a Windows 2000 Server or Windows 2000 Professional computer outside of Small Business Server Setup, before doing so, make sure that Windows Service Pack 1 is installed on the computer.

Installing Small Business Server 2000

Windows 2000 Components

Manual Logon Required After Computer Restarts Following Configuration of Domain Controller

After the domain controller configuration phase of Small Business Server Setup, the computer will restart, and you will be required to manually log on to the computer. This is true even if you selected Automatically log on during setup. Additionally, if you cancel setup, you may be required to log on to the computer manually even though you selected automatic log on.

Note: Password information is not stored on the computer when automatic log on fails.

Setup Blocked by Duplicate IP Addresses in Multiple Network Adapter Configuration

If you are installing Small Business Server 2000 on a computer with two network adapter cards, you may receive a blocking message from Small Business Server Setup indicating that the static IP address you have chosen for your internal network adapter is already in use. This can result when a computer on the external network (the network that your external adapter in on, such as your ISP) has the same IP address that you have chosen for your internal network adapter. Disable the external network adapter card and you will be able to continue with setup.

Event Messages During Setup: ‘DNS Bad Key Error’

After restarting Small Business Server during setup, there may be multiple event log error messages from the net logon service referring to “DNS bad key error.” This message can safely be ignored at this time. For more information about these events, refer to Knowledge Base article Q259277 at:
http://support.microsoft.com/support/kb/articles/Q259/2/77.ASP

Event ID 1002 ‘The DHCP Service Failed to Initialize its Global Parameters. The Following Error Occurred: %%0’

After completing setup, this event can appear in an event log when the DHCP Server service attempts to impersonate an account to prevent domain hijacking by way of a Dynamic Domain Name Services (DDNS) update. You can safely ignore this message because DDNS updates are disabled during installation of Small Business Server 2000.

For additional information about this and related event messages, or if you plan to enable DDNS updates, refer to the Microsoft Knowledge Base (KB) article Q255134 located at:
http://support.microsoft.com/support/kb/articles/Q255/1/34.ASP

Windows 2000 Service Pack 1 May Disable BlackICE And ZoneAlarm Firewall Software

Installation of Windows 2000 Service Pack 1 may disable the firewall programs BlackICE from Network ICE, and ZoneAlarm from Zone Labs. Updates that correct this problem are available from the manufacturer’s Web sites.

Small Business Setup

Message Following Installation: ‘Setup is Loading Installation Components’

When your Small Business Server 2000 computer restarts after completing installation, you may see a message stating, “Setup is loading installation components. This may take a minute or two” along with the post-installation To Do List. Setup is not re-running on your system. This message runs in the background and will remain open while you complete the items on the To Do List.

SQL Server 2000

SQL Server Service Account Selection During Setup

If you are installing SQL Server 2000 as part of the Small Business Server 2000 Setup, you will be asked to assign a service account to SQL Server. Unless you have special circumstances, it is recommended that you do not assign this service account. Not assigning a service account enables Server 2000 to run as localsystem account, which is sufficient for most installations.

Accounts you specify should be in the Domain\User format.

Warning: Specifying a non-existent account will cause SQL Server Setup to fail because Small Business Server Setup will not validate the account.

Microsoft Exchange Server

Message: ‘Microsoft Exchange Messaging and Collaboration Services Depends on Microsoft Exchange Domain Preparation, Which Has an Install Problem’

Before installation of Exchange 2000 Server, setup attempts to update the Active Directory schema. The Exchange 2000 Server DomainPrep utility is run once per domain to identify the address list server and set permissions within the domain. To successfully update the Active Directory schema, you must be logged on with an account that has Schema Administrator privileges. If you are not logged on with an account that has these privileges, the following message appears:

"Microsoft Exchange Messaging and Collaboration Services depends on Microsoft Exchange Domain Preparation, which has an install problem.”

Work around the problem by running Small Business Server 2000 Setup while logged on as a user with Schema Administrator privileges.

Alternatively, you can run the Microsoft Exchange Domain Preparation utility manually by following the steps below [BOS Only]. You can run DomainPrep on any computer running Windows 2000 Server in the domain.

To run the Exchange 2000 Server DomainPrep utility manually

1. Insert Small Business Server 2000 Server Disc 3 into your disc drive.

2. From a command prompt, type <drive>:\EXCHSRVR60\setup\i386\setup /DomainPrep, where <drive> is your disc drive.

3. On the Welcome page, click Next.

4. On the End User License Agreement (EULA) page, read the EULA. If you agree to the terms, click I agree, and then click Next.

5. On the Recipient Update Server page, type the name of the computer that will be your Exchange Recipient Update server for this domain. This computer must not be installed yet, but a computer account must exist in the Active Directory Users and Computers snap-in. When you install the first instance of Exchange in this domain, it must use the computer account that you enter in this step. Click Next.

6. On the Completion page, click Finish.

Installation of Microsoft Exchange System Management Tools Fails if CD Not in Disc Drive

If you are running Small Business Server Setup to install only the Microsoft Exchange System Management Tools component of Exchange 2000 Server, be sure that Disc 3 is seated in the disc drive before clicking Next on the Installation Summary page of setup. If the disc is not already in the disc drive, installation of the tools will fail.

Exchange System Management Tools Fail to Install

If Small Business Server Setup is unable to stop the IIS Admin Service, the Exchange System Management Tools will fail to install. To correct this problem, rerun Small Business Server Setup, and select to install the Exchange System Management Tools component again.

Service Packs

Cannot Install Service Pack if High Encryption Pack is Installed on Windows NT Server 4.0

If you encounter an error during Service Pack installation on Windows NT Server 4.0 that Internet Explorer High Encryption Pack or Internet Explorer 5.01 or later is already installed, perform one of the following:

Internet Explorer 5.01 or earlier

1. At the command prompt, type RunDll32 advpack.dll,LaunchINFSectionC:\WINNT\INF \ie5dom.inf,Uninstall,5, where C:\WINNT represents the system root.

2. In the \WINNT\SYSTEM32\ folder, rename the Schannel.dll file to Schannel.old.

3. Copy the Schannel.dll file from the Service Pack disc to the \WINNT\SYSTEM32 folder.

4. Restart Windows NT Server 4.0.

5. Delete the Schannel.old file in the \WINNT\SYSTEM32\ folder.

6. Install the applicable Service Pack, and then restart the computer.

7. Re-install High Encryption Pack.

Internet Explorer Service Pack 1 or later

1. Uninstall Internet Explorer.

2. In the \WINNT\SYSTEM32\ folder, rename the Schannel.dll file to Schannel.old.

3. Copy the Schannel.dll file from the Service Pack disc to the \WINNT\SYSTEM32 folder.

4. Restart Windows NT Server 4.0.

5. Delete the Schannel.old file in the \WINNT\SYSTEM32\ folder.

6. Install the applicable Service Pack, and then restart the computer.

7. Re-install Internet Explorer.

For more information, refer to Knowledge Base article Q250867

Connectivity

Unable to Join Domain on Windows NT 4.0 and Windows 2000 Client Computers

Client computers running Windows NT 4.0 Workstation or Windows 2000 Professional may be unable to join the Small Business Server domain under these scenarios:

· When running client setup after being a member of another domain.

· After rebuilding the Small Business Server computer.

· After migrating Small Business Server from one computer to another.

To work around this issue, remove the Windows NT 4.0 or Windows 2000 client computers from domain membership.

To remove Windows NT 4.0 client computers from domain membership

1. On the desktop, right-click Network Neighborhood, and then click Properties.

2. Click the Identification tab, and then click Change.

3. In the Identification Changes dialog box, under Member of, select Workgroup, and then specify a temporary name for the workgroup.

4. Click OK to save your changes.

To remove Windows 2000 client computers from domain membership

1. On the desktop, right-click My Computer, and then click Properties.

2. Click the Network Identification tab, and then click Properties.

3. On the Identification Changes dialog box, under Member of, select Workgroup, specify a temporary name for the workgroup, and then click More.

4. On the DNS Suffix and NetBIOS Computer Name dialog box, clear the entry for the primary DNS name of the computer, and then click OK.

5. On the Identification Changes and System Properties dialog box, click OK.

After removing computers from domain membership

1. On the client computers, release the IP address, and then flush the DNS cache by doing the following:

At the command prompt, type ipconfig /release, and then press Enter. This will release the IP address of the client computer.

At the command prompt, type ipconfig /flushdns.

2. Run client setup.

DNS Server Required for Networking Services

For Small Business Server networking services to function correctly, the DNS Server Service must be running on the Small Business Server computer. If you disable the DNS Server Service, you will experience problems with your network.

Small Business Server Internet Connection Wizard Default Recipient Policy May Override Custom Mail Policies

If you have customized the Reply address in Exchange 2000 Server for a user's SMTP e-mail account and then run the BackOffice Server Internet Connection Wizard, the customized setting may be overridden. For example, if you have set a user's reply address to user@microsoft.com and then run the BackOffice Server Internet Connection Wizard and configure the Internet mail domain as domainname.com, the user's reply to address will be changed to user@domainname.com. This scenario is likely to occur if you are using the Microsoft Connector for POP3 Mailboxes, and have added custom e-mail addresses to your POP3 users.

To correct this issue

1. Open the Small Business Server Administrator Console (click Start, and then click Small Business Server Administrator Console).

2. Expand the Active Directory Users and Computers node, expand the node for your domain, and then click Users.

3. In the list of users, right-click the affected user, and then click Properties.

4. Click the E-mail Addresses tab, select the SMTP address with the custom setting, and then click Set As Primary.

5. Click OK to save your changes.

DC Locator Records Sent to Internet Service Provider

In Windows 2000, the DNS server computer will attempt to send DC Locator records out through the external network connection to your ISP on a regular basis. This will result in added network traffic to your ISP, and could pose a security risk if the information is misused. This is a known issue with Windows 2000 that will be fixed in Service Pack 2.

A supported patch that corrects this problem is now available from Microsoft, but it has not yet been fully tested and should be applied only to computers that are experiencing this specific problem. If you are not affected by this specific problem, it is recommended that you wait for Windows 2000 Service Pack 2.

For more information, refer to Knowledge Base article Q265395 at:
http://support.microsoft.com/support/kb/articles/q265/3/95.ASP

Small Business Server Internet Connection Wizard Does Not Configure Content or Protocol Filtering

The Small Business Server Internet Connection Wizard configures Internet Security and Acceleration (ISA) Server 2000 to provide IP packet filtering. The wizard does not configure content or protocol filtering on ISA Server. For information on configuring those security settings, refer to ISA Server documentation.

Internet Explorer Unable to Find a Connection

After you run the Small Business Server Internet Connection Wizard, an error stating that ’Internet Explorer was unable to find a connection’ may appear if you run Internet Explorer from the Small Business Server computer using a dial-up connection. To resolve this problem, click Try Again.

Restart Services if Changes are Made to Dial-up Connection Properties

If you have configured ISA Server 2000 to use a dial-up connection to connect to your ISP, and you then make changes to the properties of that dial-up connection, you will need to restart the Microsoft Web Proxy Service and Microsoft Firewall Service.

Management Consoles

Migrate User Wizard Cannot Create Mailboxes When Logon Name Contains Only DBCS Characters

If you run the Migrate User Wizard attempting to migrate user accounts that use strictly DBCS characters, Exchange mailboxes may not be created for those users. You can, however, manually create mailboxes using the Active Directory Users and Computers snap-in, located in the Small Business Server Administrator Console.

To manually create an Exchange mailbox

1. Click Start, and then click Small Business Server Administrator Console.

2. In the Console Tree, expand Active Directory Users and Computers, expand your domain, and then click Users.

3. Right-click a user account in the Details Pane, and then click Exchange Tasks.

4. If this is the first time you have run the Exchange Task Wizard, select Do not show this Welcome Page again if desired, and then click Next.

5. Select Create Mailbox, and then click Next.

6. Fill in the required information, and follow the on-screen instructions to complete the wizard.

Note: Perform these steps for each mailbox you need to create.

Server Health and Monitoring

Configure SMTP Service to Relay E-Mail Alerts from Health Monitor 2.1

For Health Monitor to send e-mail alerts, SMTP service needs to be properly configured to relay e-mail from Health Monitor.

To configure e-mail relay in Exchange Server, do one of the following:

· Run the Small Business Server Internet Connection Wizard.

-Or-

· Perform the following steps:

1. Open the Small Business Server Administrator Console.

2. In the Console Tree, expand the Server (Exchange) node, expand Servers, expand Servername, expand Protocols, and then expand SMTP.

3. Right-click Default SMTP Virtual Server, and then click Properties.

4. Click the Access tab, and then click Relay.

5. Click Add, type the IP address of the computer where Health Monitor is installed, and then click OK.

Note: It is recommended that you add the IP address for each network adapter.

6. Click OK to close all open dialog boxes.

Close and then Re-open Server Status View to Reconnect Interfaces lingansStopping and starting Windows Management Instrumentation (WMI) may disconnect some interfaces to the Server Status View. To re-establish these interfaces, close and then re-open the Server Status View.

Update Health Monitor Thresholds to Reflect Your Network Monitoring Needs

The default counter thresholds provided with Health Monitor 2.1 are sample counters. You should establish a baseline for your network configuration and update the threshold values accordingly. In particular, the default values for Page faults/sec and Processor queue length need to be addressed.

Shared Fax Service

All Users Have Access to Fax Printer After Upgrade

After an upgrade, all members of the Domain Users security group have permission to fax documents regardless of what fax permissions they had prior to the upgrade. For information about assigning permissions to security groups, refer to the topic “Using Security Groups to Control Access to Resources” in Small Business Server 2000 Online Help.

Not All Modems Support Adaptive Answering

Adaptive answering enables a fax device to identify whether incoming calls are fax or data calls. Using the Shared Fax Service Manager console, you can choose to enable this functionality on the Properties page of each fax device. It should be noted that although you can enable this option for all devices, adaptive answering would only be enabled for modems that support this feature.

Windows 2000 Personal Fax Can Receive Inbound Fax Transmissions

Windows 2000 Personal Fax can be configured with a higher transmission priority than the Shared Fax Service application included with Small Business Server. To avoid confusion, you should either disable Windows 2000 Personal Fax or the Receive setting.

Asian Characters Not Displayed for Shared Fax Services Cover Page

When you send a fax with a cover page and use Asian characters from an English-only version of Shared Fax Service, the Asian characters are not correctly displayed.

To change the fax cover page to display an Asian language

1. Open the BackOffice Server Management Console.

2. Expand the Microsoft Shared Fax snap-in, and then click Cover Pages.

3. In the Details Pane, right-click the cover page you want to modify and then click Edit.

4. Click OK for the Cover Page Editor Tips.

5. To modify the default font for the cover page, click Select All from the Edit menu, click Font from the Format menu, and then select the appropriate language font. Click OK.

6. To save the modified cover page, select Save As from the File menu, name the file, and save the template in the default folder \\ Documents and Settings\All Users\Documents\Microsoft\Shared Fax\Common Cover Pages.

7. Quit the Fax Cover Page Editor.

Note: The computer must be configured to read and write documents in multiple languages. To install additional languages, open Regional Options in Control Panel.

Upgrading the Shared Modem Client

Upgrading the Shared Modem Client removes all existing modem sharing ports on the computer. To reestablish the modem sharing ports, refer to the Microsoft Shared Modem Service Client Help in <system drive>\Program Files\Microsoft Shared Modem\Clients\Platform.

Reinstall Shared Fax Service if the Fax Printer is Deleted

When Shared Fax Service is installed on a server computer, a fax printer is created. If this fax printer is deleted for any reason, you must reinstall Shared Fax Service to create a new fax printer.

Shared Fax Service Unable to Detect Some ISDN Modems

Microsoft Shared Fax Service cannot detect or use ISDN modems that do not emulate analog modems. To enable Shared Fax Service to work with ISDN modems of this type, Fax Service Provider software must be installed on the computer. If your ISDN modem does not work with the Shared Fax Service, check with your ISDN modem supplier for the availability of Fax Service Provider software that works with Microsoft Shared Fax Service.

Windows 95 Client Computers May Need to Install a .tif Viewer to View Faxes

To view sent and received faxes on a Windows 95 computer, you must have an application installed that can open files with a .tif file extension. For example, both Kodak Imager and Adobe Acrobat can view .tif files.

Selecting ‘Store in a Folder’ as an Incoming Method

When selecting Store in a folder as the incoming method for a specific device, or as the global method for incoming routing, the computer account must have access rights to the folder specified. It is not sufficient for the local user to have access rights to the folder.

Support in Send Fax Wizard for Languages Other Than the Default System Locale Language

When sending a fax using the Send Fax Wizard on a Windows 2000 client computer, if you enter an address from the Windows Address Book with characters in a language other than that of the default system locale, the characters will appear as question marks ("?") in the To field. This occurs because Shared Fax Service does not support Unicode for this entry. For recipient names to appear correctly in the To field, you must change the system locale to one that represents the language of the recipient, before you select a recipient from the address book. For example, if the system locale is English (United States) and you want to include the name of a recipient that appears in Japanese, you must change the system locale to Japan.

To change the system locale

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Regional Options.

3. Click Set Default, and then select the appropriate system locale.

4. To close the Select System Locale dialog box and Regional Options properties page, click OK.

Sending a Fax from Outlook, Using Both E-mail Addresses and Fax Numbers

When you use Shared Fax Service to send a fax from Outlook, if the fax has both an e-mail address and a fax number, you will receive a message stating that the e-mail cannot be sent because the e-mail address is incorrect. However, the fax was submitted and sent successfully. This issue will be resolved in a future Exchange 2000 Service Pack..

Do Not Select a Separator Page for the Shared Fax Printer

A separator page must not be selected for the Shared Fax printer, even though this option is available. If you elect to use a separator page, Shared Fax Service will not be able to send faxes until the option is turned off.

Non-Textual Content Cannot Be Copied and Pasted into Microsoft Outlook Fax Documents

You cannot use Shared Fax Service to send a fax from Outlook that includes non-textual content, such as graphics and tables that have been copied and pasted into the fax document. Rather, save the non-textual content to a file and attach it to the Outlook document.

Microsoft Outlook Should Be Configured as the Default Mail Client

If Outlook is not installed as the default mail client, the address book displayed by the Send Fax Wizard will be the Windows Address Book. Outlook is not configured as the default mail client unless the user specifies that option when Outlook is opened for the first time on the client computer.

To configure Microsoft Outlook as your default mail client

1. Start Microsoft Internet Explorer.

2. Open the Internet Options properties page, as follows:

· In Microsoft Internet Explorer versions 3.x, or 4.x, on the View menu, click Internet Options.

· In Microsoft Internet Explorer 5.0 or later, on the Tools menu, click Internet Options.

3. Click the Programs tab, select Microsoft Outlook in the Mail or E-Mail list, and then click OK.

‘Print Directly to Option’ Not Supported by Shared Fax Printer

A Shared Fax printer does not support the Print directly to printer option in printer properties. You must set printer properties to the Spool print documents so program finishes printing faster option.

To change the printer properties

1. Click Start, point to Settings, and then click Printers.

2. Right-click the Shared Fax printer icon, and then click Properties.

3. Click the Advanced tab, select Spool print documents so program finishes printing faster, and then select one of the sub-options.

4. Click OK.

Printing a Document to the Shared Fax Printer as it is Displayed in Microsoft Word 2000

When sending a fax (printing) to the Shared Fax Printer, the resulting fax document layout is displayed differently than the Word 2000 document. You can change a setting in Word to print a document as it is displayed.

To print a Word 2000 document as it is displayed

1. In Word, on the Tools menu, click Options.

2. Click the Compatibility tab, and then select Use printer metrics to lay out document from the Options list.

3. Click OK.

Can't Use 'Mail To' Feature if Outlook is Not Configured

From the Small Business Server computer, you will be unable to send a received fax as e-mail unless you have configured Outlook on the Small Business Server computer. To send a received fax as e-mail, right-click a received fax and then click Mail to.

Shared Fax Service Modem Unavailable

If you are unable to send or receive faxes with a modem in use by the Microsoft Shared Fax Service, one of the following may resolve the issue:

· Turn the modem off and then on, without stopping Shared Fax Service.

-or-

· Stop Shared Fax Service, turn the modem off and then back on, and then restart Shared Fax Service.

Shared Modem Service

Install Service Pack 2 to Replace Modem.sys

To use a Windows 2000 Professional Modem Sharing Service client with tone dialing, you must first download and install Windows 2000 Service Pack 2. For more information, refer to Knowledge Base article Q263643 at
http://support.microsoft.com/support/kb/articles/Q263/6/43.asp

After Upgrade, Modem Sharing Client Does not Automatically Detect the Shared Modem

After upgrading to Small Business Server 2000, some clients may not be able to detect the shared modem on the Small Business Server computer. To address the issue, perform the following steps.

On the server

1. From the Services snap-in, stop the Shared Modem Service.

2. Update the modem driver to a Windows 2000 Server-compatible driver.

3. From the Shared Modem Service applet in Control Panel, add a modem to the desired modem pool.

4. From the Services snap-in, start the Shared Modem Service.

On the client

1. Open Control Panel, double-click the Modems applet, and then remove the Small Business Server 4.5 shared modem.

2. Install Modem Sharing Client on the Small Business Server client computer.

3. Configure the client to use the modem pool on the server:

· For Windows 9x clients, go to MS Shared Modem Service Client in Add/Remove Programs and then select "Add a Shared Modem Service Port."

· For Windows NT Workstation 4.0 and Windows 2000 Professional clients, run "netmodem use * \\servername\poolname"

4. Open Control Panel, and then double-click the Modems applet.

5. Add a modem, and try to detect it automatically.

Virtual Port Does Not Appear in List of Available Ports in Install New Modem Wizard

If a virtual port mapped to a modem pool is busy, the virtual port will not appear in the list of available ports in the Install New Modem Wizard. A pool is considered busy when all of the ports in it are in use. This issue only applies to the Windows 2000 Modem Sharing client.

To avoid this issue, do not attempt to install a modem on a virtual port for a Windows 2000 Modem Sharing client if it is mapped to a modem pool that is busy.

Removing the Shared Modem Service may not removed Shared Modem Service Icon from Control Panel

Removing the Shared Modem Service Server may remove the Shared Modem Service applet from Control Panel.

The applet can be manually removed by deleting the file modemshr.cpl from the winnt\system32 directory. If the file cannot be deleted because it is being used by another process (for example, explorer.exe), restart your computer and try to remove the file again.

Do Not Install Microsoft Shared Modem Service and Modem Sharing Client on the Same Computer

A Modem Sharing Client must not be installed on a computer that is running Microsoft Shared Modem Service. Installing both components together results in unstable components.

Exchange 2000 Server

Exchange 2000 Server Release Notes

For further information about Exchange 2000 Server, refer to the Exchange 2000 Server Release Notes located in the \EXCHSRVR60 directory on Small Business Server 2000 Setup Disc 3.

The 'Synchronize Mail' Task Will Run on the Next Piece of Outgoing Mail

On the Small Business Server Administrator Console, when you select the Servername (Exchange) snap-in, and on the Small Business Server Personal Console when you select E-mail, there is a taskpad task called Synchronize Mail. Clicking this task triggers Exchange 2000 Server to send any mail that is waiting in the Outside Delivery queue. If there is no mail in the queue, the trigger will be set to send mail the next time e-mail arrives in the queue for outside delivery.

Additionally, if you have configured your SMTP connector to use a scheduled ETRN or TURN signal to retrieve mail from your ISP, that ETRN or TURN signal will be sent at the same time the outbound mail is being sent, regardless of the delivery schedule that has been defined.

Configure the Postmaster Address to Receive Non-Delivery Reports and Undeliverable E-mail

If your Internet domain name is not identical to your Active Directory domain name, you must configure the postmaster address. The postmaster address allows users who receive non-delivery reports to reply to a designated postmaster to report delivery failure or seek assistance. You will need to configure the postmaster address in both a clean installation and an upgrade.

Note: Exchange Server automatically configures a postmaster address for the Administrator account during setup. If you want the administrator to receive postmaster mail, you must modify this account. If the Administrator account is not the designated recipient for postmaster mail, delete the postmaster address entry.

To configure the postmaster address

1. From the Small Business Server Administrator Console, expand the Active Directory Users and Computers snap-in, expand the node that represents your server computer, and then click Users.

2. Right-click the user account you want to receive postmaster mail, and then click Properties.

3. Click the E-Mail Addresses tab, and then click New.

4. Under E-mail address type, select SMTP Address, and then click OK.

5. Type the e-mail address for the postmaster. For example, postmaster@<domain> where <domain> is the domain name for your organization.

6. Click OK, and then close the Administrator Properties dialog box.

Unable to Resolve Exchange Server Alias When Client Language Differs from Server Language

You are unable to resolve an Exchange 2000 Server e-mail alias when the client language differs from the server language. To resolve the problem:

1. On the server computer, open Control Panel, and then double-click Regional Options.

2. In the list of language settings for the system, select all applicable languages.

3. Click Apply, and then close the Regional Options dialog box.

Power Users May Not Be Able to Create Mailboxes if Exchange Server is Installed in Maintenance Mode

If you install Small Business Server 2000 without Exchange 2000 Server, and then install Exchange Server later using Small Business Server Setup in maintenance mode, power users will not be able to create Exchange mailboxes for users. To provide this capability, refer to the topic “Enable Small Business Template Power Users to Create Exchange Mailboxes for New Users” in Small Business Server Online Help.

Microsoft Connector for POP3 Mailboxes

Unable to Download POP3 Mail After Configuring Router Trigger

If you configure Microsoft Connector for POP3 Mailboxes to use a router trigger when it attempts to download mail, the mail will not be downloaded from your Internet service provider (ISP) until the router trigger has finished executing. If the program defined in the router trigger fails or hangs, the POP3 Connector will be unable to download POP3 mail. Since the router trigger is still attempting to execute, clicking Retrieve Now will have no effect. This functionality occurs by design.

If you suspect this problem, use Task Manager to end the task defined as the router trigger. Once the task is ended, the POP3 Connector should be able to finish downloading mail from your ISP.

Define a Global Mailbox to Receive Mail Downloaded from an External Mailing List

Before you can configure the Microsoft Connector for POP3 Mailboxes to retrieve mail from an external mailing list, you must first define a global mailbox in the POP3 Connector to download POP3 mail from your ISP. Once this has been done, you can define an external mailing list to route POP3 mail to Exchange users.

Internet Security and Acceleration (ISA) Server 2000

ISA Services Will Not Start if Network Address Translation (NAT) is Enabled

If ISA Server is installed on a computer that has the Network Address Translation (NAT) routing protocol enabled through Routing and Remote Access Service (RRAS), ISA services will not start. This occurs because the NAT configuration in RRAS conflicts with the NAT service provided by ISA Server. To correct this issue, disable the NAT configuration in RRAS.

To disable NAT in RRAS

1. Click Start, point to Programs, point to Administrative Tools, and then click Routing and Remote Access.

2. Expand the node that represents your server computer, and then click IP Routing.

3. In the Details Pane, right-click Network Address Translation (NAT), and then click Delete.

4. Click Yes to verify removal of the NAT from the computer.

Use Only the Dial-up Connection Specified in ISA Server to Connect to the Internet

If your Small Business Server computer is connected to the Internet by way of a dial-up connection other than the one that is defined in your ISA Server settings, ISA Server will not properly monitor network traffic over the connection, which may pose a security risk to your network. As a best practice, use only the dial-up connection defined in ISA Server. Use the Small Business Server Internet Connection Wizard to easily select the dial-up connection you want to use to connect to the Internet.

Using ISA Server With a Dial-up Connection May Cause Unexpected Dialing When ‘Active Caching’ is Enabled

By default, ISA Server enables active caching, which causes ISA Server to dial at intervals to retrieve Web content. If ISA Server is configured to connect to the ISP using a dial-up connection, the modem dials at intervals, even if no user is requesting Web content. To correct this problem, run the Small Business Server Internet Connection Wizard, which will disable active caching. As an alternative, perform the steps in the following procedure.

To disable active caching

1. Click Start, point to Programs, point to Microsoft ISA Server, and then click ISA Management.

2. In the Console Tree, expand the Servers and Arrays node, and then expand your server node.

3. Right-click Cache configuration, and then click Properties.

4. Click the Active Caching tab, and then clear the Enable active caching check box.

5. Click OK to save your changes.

Client Notes

Error When Upgrading Fax Client Software: ’Fax network client setup failed. Please contact your system administrator.’

This may occur after upgrading a client computer's operating system to Windows 2000 Professional. If you see this error, you must add the fax printer manually through the Windows 2000 Add Printer Wizard. In the wizard, enter the name of the printer as \\SBSservername\SharedFax.

Before Upgrading Client OS to Windows 2000 Professional, Uninstall Fax Sharing Client 4.5 and Modem Sharing Client 4.5

Before upgrading a client computer's operating system to Windows 2000 Professional, you need to uninstall both Fax Sharing Client 4.5 and Modem Sharing Client 4.5. Once these have been removed, upgrade the operating system to Windows 2000 Professional. When the operating system is upgraded, install the fax and modem sharing client software for Small Business Server 2000.

Error When Running Client Setup: ‘Conflicting Credentials’

This message appears if you attempt to run Client Setup without first logging on as a user with local administrator privileges. To avoid this problem, log on to the client computer as a local administrator.

Auto Logon Information Error: ‘Your Auto Logon Password is Incorrect. Re-enter Your Password’ When Password is Entered Correctly

This error message appears if you select the Automatically logon option in setup on a Windows 2000 Server computer where the Client for Microsoft Networks networking component has been disabled or removed. Additionally, the following error will appear in your System event log:

Event ID 12291, SAM failed to start the TCP/IP or SPX/IPX listening thread

To correct this problem, install the Client for Microsoft Networks networking component on the Windows 2000 Server computer before attempting to install Small Business Server 2000.

To add the Client for Microsoft Networks networking component

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click your network connection, and then click Properties

3. In the list of components, select Client for Microsoft Networks, and then click Install.

4. When asked, restart the computer.

Interactive Logon is Disabled on a Windows 2000 Server Computer Running Terminal Services

If you install an additional Windows 2000 Server computer on your network running Terminal Services, you may receive the message “interactive logon has been disabled” when attempting to log on over the network or locally.

To resolve this, you must manually restart the Windows 2000 computer running Terminal Services, logon using an account in the computer's local Administrator group and install Service Pack 1 for Windows 2000. After installing Service Pack 1 for Windows 2000, you need to grant permissions for users to logon to the computer.

To allow users to logon to a computer running Terminal Services

1. Click Start, and then click Small Business Server Administrator Console.

2. In the Small Business Server (BackOffice Manager) snap-in, click Users.

3. Right-click a user account, and then click Properties.

4. Click the Terminal Services Profile tab, select Allow logon to terminal server, and then click OK.

5. Repeat this procedure for each user that will access Terminal Services.

Note: Service Pack 1 for Windows 2000 is located in the W2K_SP1 directory on Small Business Server Setup Disc 1.

Tip: If you want all new users to have this access, perform this procedure on the Small Business User template user account.

Error When Creating Networking Setup Disk: ’Insufficient Space’

If you run the Add User Wizard or Set Up Computer Wizard and receive an “Insufficient space” error when writing to the networking setup disk, you may have a system language issue. Check to ensure that your Small Business Server 2000 computer is using the same locale as the client computers on the network.

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Regional Options.

3. Under Your locale (location), ensure that the proper locale is listed, or set the proper locale to match that of your client computers.

4. Under Language settings for the system, ensure that all applicable client computer languages are selected.

5. After verifying and/or configuring locale and language settings, re-run the Add User Wizard or Set Up Computer Wizard.

Uninstalling Applications

Stop MSSQLSERVER Service Before Uninstalling SQL Server 2000

When using Small Business Server Setup to uninstall SQL Server 2000, you must first stop the MSSQLSERVER service. Otherwise, SQL Server 2000 will not be uninstalled.

To stop the MSSQLSERVER service

1. Open the Services administrative tool (click Start, point to Programs, point to Administrative Tools, and then click Services).

2. In the list of services, right-click MSSQLSERVER, and then click Stop. Do Not Restart Computer

When Uninstalling English Query 2000

When using Small Business Server Setup to uninstall English Query 2000, a dialog box appears asking you to restart the computer. Do not restart the computer at this time, otherwise setup will not complete the uninstall process. Rather, click Exit Setup. Another dialog box appears informing you that you must restart the computer to complete the installation of the software. Click OK in this dialog box; a message appears stating that “Microsoft English Query 2000 Setup was not completed successfully.” This is expected behavior and there is no cause for alarm. Click OK and complete setup. After setup is complete, restart the computer.

Before Uninstalling Exchange 2000 Server on Small Business Server 2000

If you are running Small Business Server 2000 and need to remove Exchange 2000 Server, you will need to stop the Exchange IFS service and remove the drive mapping to the Exchange Web Store.

To stop the Exchange IFS service, open a command prompt and type net stop exifs. With the command prompt still open, type subst m: /d, which will remove the drive mapping to the Exchange Web Store.

Exchange 2000 Server Requires IIS

If you attempt to uninstall Internet Information Services (IIS) when Exchange 2000 Server is installed, a message appears informing you that Exchange Messaging and Collaboration Services will also be removed. This is due to a dependency that Exchange 2000 Server has on IIS. If there are any existing user mailboxes, IIS will be removed, but Exchange Messaging and Collaboration Services will not. Because Exchange 2000 Server depends upon IIS, removal of IIS will cause Exchange Server to stop functioning.