Microsoft Small Business Server 2000 Resource Kit by Microsoft Corporation, Microsoft

From the Publisher

Enhance the way your organization communicates and collaborates with comprehensive information, tools, and insights from the Small Business Server 2000 product team!

Roll out, support, and optimize Microsoft’s server-based platform for small businesses with the expertise of those who know the technology best—the Microsoft® Small Business Server 2000 team. This official RESOURCE KIT includes hundreds of pages of authoritative technical information plus essential tools on CD-ROM—all designed to help you maximize the productivity of your server system while minimizing overhead and support costs. It’s full of information and tools that can help any small business turn information into action.

Find vital details about these topics:

• PRODUCT OVERVIEW: Learn about the Microsoft Small Business Server 2000 design philosophy and features and read introductory information specifically for the technology consultant.
• PLANNING: Discover how to plan for a Small Business Server 2000 network and applications, an Internet presence, connectivity for remote access users, and capacity increases.
• DEPLOYMENT: Find out how to deploy Small Business Server 2000 both on new machines and in existing environments, learn about setup and client issues, understand ISP and remote connectivity issues, and familiarize yourself with Windows 2000 configuration issues.
• ADMINISTRATION: Understand Small Business Server Wizard processes, Terminal Services, and other administrative tools; and find out how to monitor, optimize, and administer Small Business Server components.
• INTEGRATION AND SECURITY: Learn about e-mail andInternet connectivity alternatives; cross-platform issues; and security and Web caching with Microsoft Proxy Server 2000, Microsoft Windows® 2000 Server, and Internet Information Services 5.0.
• UPGRADES, MIGRATION, AND TROUBLESHOOTING: Find out about Small Business Server 2000 licensing and upgrades, data migration, disaster recovery, and troubleshooting.
• OTHER RESOURCES: Get complete appendixes full of information about networking basics, migrating from Netware, customization and extensibility options, deployment with Microsoft Office 2000, Telephony Applications Programming Interface (TAPI) solutions, and more.

Included On CD-Rom:

• An electronic copy of the book
• Tools and accompanying help files for computer and network management, deployment, diagnostics and troubleshooting, security, scripting, and use with Microsoft Internet Information Server (IIS) and Microsoft Internet Explorer.

Booknews

Provides instructions for installing and maintaining Microsoft's server-based platform for small businesses with under 50 employees. The guide addresses issues that arise when planning the server network, outlines factors and conditions that should be considered when customizing the deployment of the server, and describes administration of server tools, applications, and components. The closing chapters cover integration and interaction, security, migration and upgrade, and disaster recovery. The CD-ROM contains tools, utilities, and scripts. Annotation c. Book News, Inc., Portland, OR (booknews.com)

Product Details

• Table of Contents
• Read an Excerpt
• Read a Sample Chapter

Table of Contents

Read an Excerpt

Chapter 11: ISP Connectivity Tasks

• Internet connection basics
• Internet connection issues
• Small Business Server Internet Connection Wizard walk-through

Internet connectivity is a key feature for small- and medium-sized businesses. International Data Corporation (IDC) in Framington, Massachusetts, estimates that Internet access drives computer sales faster than LAN connectivity. One might extrapolate from this research that businesses buy computers to be able to access the Web and that deployment of a LAN is secondary. IDC now estimates that 85 percent of businesses with 100 or fewer employees have computers.

Broadband Internet access is exploding, as are the connectivity services for those broadband connections. "By 2005, more than 35 million small and medium businesses, residential consumers and small office/home office customers will be using some form of broadband access, according to the NxGen Data Research report [by New Paradigm Resources Group]. DSL will represent about 13 million of those lines in service, while cable modems, terrestrial microwave and satellite access methods will claim significant market share, as well." -PRNewswire, July 1999.

Internet Connection Basics

Small Business Server 2000 supports Internet connectivity primarily through the Small Business Server Internet Connection Wizard. The Small Business Server Internet Connection Wizard helps you configure Microsoft Windows® 2000 Server, Microsoft Exchange 2000 Server, and Microsoft Internet Security and Acceleration (ISA) Server 2000 for an Internet connection. The wizard relies on the Windows 2000 Routing and Remote Access Service (RRAS) for network or dial-on-demand modem connectivity. After network connectivity has been established with RRAS, the wizard configures Exchange 2000 Server and ISA Server accordingly.

Internet Connection Topologies

Before starting the Small Business Server Internet Connection Wizard, you might want to review how Small Business Server connects to the Internet. For overall network topology diagrams, including Digital Subscriber Line/Asynchronous Digital Subscriber Line (xDSL), cable modem, Integrated Services Digital Network (ISDN), and dial-up, refer to Chapter 5, "Planning for an Internet Presence."

Internet Connection Types

Small Business Server supports many types of connectivity hardware, which can be grouped into two categories: dial-up and non-dial-up.

• Dial up. Dial-up connection hardware establishes an Internet connection by using the Network and Dial-up Connections feature. The dial-up connection hardware includes analog modems and ISDN terminal adapters. These devices are connected to Small Business Server through a serial port, multiport serial board, or an internal card and can be configured with the Phone and Modem Options utility in Control Panel.

Note Small Business Server 2000 has much stronger modem support than previous versions of Small Business Server. Small Business Server 2000 supports any Windows 2000 Server-compatible modem and automatically detects the modem with Device Manager.

ISDN dial-up connections are beneficial in areas not served by other high-speed Internet connection alternatives. In general, ISDN is more expensive that the non-dial-up Internet connection alternatives discussed later in this section. One benefit of an ISDN connection is that you can dial other ISDN telephone numbers if your primary connection fails. You can also dial other ISDN-based communications servers (for example, a customer site) and use RRAS to transfer files, use a remote network, and so on. More information on ISDN connections is provided later in this section.

• Non-dial up. Non-dial-up Internet connections consist of full-time broadband connections and routers. There are two popular full-time connections that use broadband devices:
• xDSL modems or routers
• Cable modems

xDSL Modems or Routers

Establishing an Internet connection by using an xDSL modem or router requires an internal adapter and a second network adapter. The default gateway is configured on the second network adapter, causing all Internet connections to be filtered by ISA Server. xDSL connections are typically configured to be "always on" from the time the Small Business Server computer starts. A static Internet Protocol (IP) address is recommend for this configuration and is obtained from the ISP, and it should be applied to the device's external network adapter (WAN port). However, you can have either a registered Internet IP address or dynamic IP address assigned to the xDSL by the ISP. An xDSL modem or router solution might accrue additional service charges for the small business if you exceed a certain level of downloads during a billing period.

Note When the hardware device used to connect the Small Business Server network to xDSL service is running in bridging mode (Layer Two of the Open Standards Interconnection model), it is typically referred to as an xDSL modem. When the same device is running in Point-to-Point Protocol (PPP) mode (Layer Three of the Open Standards Interconnection model), the device is known as an xDSL router. ISPs vary on whether you connect in bridging mode or PPP mode, but PPP mode has emerged as the preferred connectivity approach for xDSL.

Cable Modems

With the advent of cable technology that enables information to flow two ways, cable companies started providing Internet connectivity services to homes and businesses. The cable company serves as both the telecommunications company providing communications services and the ISP company providing Internet connectivity.

Cable connections are initiated at the time the Small Business Server computer starts and are maintained while the computer is on. The default gateway is configured on the second network adapter, causing all Internet connections to be filtered by ISA Server. Cable modems typically receive a dynamic IP from the ISP to discourage the user from running an external Web server. Cable companies discourage this practice because the bandwidth for a cable modem is multiplexed for everyone on that cable segment. If one user consumes a large amount of the available bandwidth, all cable modem users on that segment experience decreased performance. However, cable companies do offer business-level Internet connection packages that allow for the acquisition and use of static IP addresses. Cable companies typically charge a flat fee, regardless of download volumes...

Read a Sample Chapter

• Shared Fax Service
• Faxing Model
• Managing Shared Fax Service
• Fax and E-mail Integration
• Faxing Documents from the Small Business Server Network
• Shared Fax Service—Remote Administration
• Shared Modem Service
• Administering the Shared Modem Service
• Viewing and Configuring Modem Pools
• Configuring Clients for Modem Pool Connection
• Status Monitoring
• Exchange 2000 Server
• System Manager Interface
• Mailboxes
• Distribution Groups
• Custom Recipients
• Address Lists
• Public Folders
• Protecting Exchange Data
• Exchange Administration Tips
• Monitoring the Performance of Exchange Server
• Internet Security and Acceleration Server
• User Access Control
• Using FTP
• Configuring System Monitor Alerts for ISA Server
• Firewall Client
• SQL Server 2000
• Migrating Access to SQL Server 2000
• Small Business Database Scenarios
• SQL Server 2000 Administration
• Outlook 2000
• Team Interaction
• Outlook 2000 Team Folders
• Downloading the Outlook 2000 Team Folder Kit
• Installing the Team Folders Wizard
• Building Outlook 2000 Team Folders
• Extending Team Folders
• Summary

This chapter provides concepts and procedures to help you administer the following Microsoft^® Small Business Server 2000 applications and components:

• Shared Fax Service
• Shared Modem Service
• Microsoft Exchange 2000 Server
• Microsoft Internet Security and Acceleration (ISA) Server 2000
• Microsoft SQL Server^™ 2000
• NTFS/FAT volume security
• Microsoft Outlook^® Team Folders

Shared Fax Service

Shared Fax Service provides fax services to client computers on the small business network. After fax client software is installed, users can send and receive faxes with fax devices installed on the server. At least one high-quality Class 1 fax modem must be installed on the Small Business Server computer to use Shared Fax Service.

Faxing Model

The Shared Fax Service uses a fax printer to send and receive faxes. During installation, the Shared Fax Service creates a default shared fax printer. Users then fax documents by printing them to the shared fax printer, just as if they were sending a document to a shared printer. The fax printer instructs the fax device to send the fax.

The three components of Shared Fax Service are:

• Shared Fax Service. The core server component.
• Microsoft Shared Fax (Local). Used to configure, manage, and monitor the Shared Fax Service.
• Microsoft Shared Fax Console. The Microsoft Management Console (MMC) snap-in, used to send and receive faxes, monitor the fax queue, and archive sent and received faxes.

The Shared Fax Service is set up by default when Small Business Server is installed.

Managing Shared Fax Service

You can manage the Shared Fax Service by selecting Microsoft Shared Fax (Local) in the Console Tree of Small Business Server Administrator Console. The Shared Fax Service Manager appears, called Tips—Microsoft Shared Fax, as shown in Figure 18.1. It enables you to:

• Observe and modify the fax properties, including general properties, receipts, event reports, activity logging, outbox, inbox, sent items, and security settings.
• Start the Microsoft Shared Fax Console.
• Manage devices, providers, and incoming and outgoing routing objects.
• Manage cover pages.

Figure 18.1 The Shared Fax Service Manager (right pane) in the Small Business Server Administrator Console allows extensive Shared Fax Service configurations (Image unavailable)

Adding a Fax Modem

When Small Business Server installs Shared Fax Service, it configures any fax modems installed during setup to send faxes. If your fax modem was not automatically installed, make sure your fax modem is a high-quality Class 1 fax modem. Shared Fax Server enables faxing activity automatically for those fax modems installed after setup.

Shared Fax Service can be configured to work with high-quality specialized fax cards. For more information, refer to the Microsoft Small Business Server Web site at: http://www.microsoft.com/ smallbusinessserver/.

If you need to install additional modems after setup, you can do so by using the Add/Remove Hardware program group in Control Panel.

User Access to the Fax Printer

You can control who uses a fax printer in the same way that access to any printer is controlled—by changing the security and sharing settings for the fax printer. To do this, perform the following steps.

To control user access to the fax printer

1. Click Start, click Small Business Administrator Console, and then right-click Microsoft Shared Fax (Local).
2. Click Properties.
3. Click the Security tab (shown in Figure 18.2).
4. Click Add to add users and groups to the Name list.
5. Click Remove to remove users from the Name list.
6. In the Name list, highlight the user or group, and then in the Permissions list, modify the permissions listed as necessary. For example, to grant the Everyone group the permission to manage fax jobs, in the Name list, select Everyone and then in the Permissions list, click Allow for the Manage fax jobs permission.

Figure 18.2 User access to the fax printer is configured on the Security tab (Image unavailable)

Monitoring Fax Activity

Shared Fax Service provides reporting capabilities for outgoing and incoming faxes through the Microsoft Shared Fax Console, shown in Figure 18.3.

Figure 18.3 Microsoft Shared Fax Console (Image unavailable)

Start the Microsoft Shared Fax Console by selecting Manage Fax Jobs on the Tips—Microsoft Shared Fax page (see Figure 18.1).

Monitoring Outgoing Faxes

You can monitor outgoing faxes from the following Shared Fax Console folders:

• Outbox
• Sent Items

Outbox Folder

The Shared Fax Console Outbox folder is the queue for outgoing faxes, displaying information about outgoing faxes in the Status column. Faxes are in one of the following stages when shown in the Outbox folder:

• Pending. The fax is waiting in the outgoing queue for an available transmission group device, according to priorities in the group (in this case, a group of fax devices).
• Sending. Sub-stages in the sending stage include dialing, initializing, or transmitting the fax.
• Paused. The fax is pending because while it was in the queue, it was paused by either a user or the administrator.
• Retrying. Following receipt of a busy signal or of finding no free telephone line, the service redials the recipient fax number to attempt to send a fax to the recipient’s fax device.
• Retries exceeded. The service has attempted to transmit the fax the maximum number of times allowed by the administrator.

Sent Items Folder

After an outgoing fax has been successfully transmitted, it moves to the Sent Items folder in the Shared Fax Console. This folder archives all successfully sent faxes and displays information about them.

Monitoring Incoming Faxes

You can monitor incoming fax queue status from the Inbox folder. The folder displays information about incoming faxes while they are being processed and after they have been processed.

Logging and Events

Shared Fax Service provides a log for all incoming and outgoing faxes. You can configure logging by using the Activity Logging tab in the Microsoft Shared Fax (Local) Properties dialog box. Set the location for the activity logs in the Log database folder location field.

You can also generate fax-related events in the in Event Viewer Activity Log by using the Activity Logging tab in the Microsoft Shared Fax (Local) Properties dialog box.

Shared Fax Service generates the following four types of events:

• General
• Incoming
• Outgoing
• Initialization or shutdown

You can view a description and the properties of generated events in the Event Viewer. View log entries by using the Event Viewer Application log (available from the Start menu, Programs, Administrative Tools, Computer Management snap-in, Event Viewer, Application log).

Fax Queue

The Fax Queue is the printer device used for sending and receiving faxes. You view it from the Printers folders, just like any other printer. Received faxes are placed in the Store Directory, a folder on the Small Business Server computer. Sent faxes are placed in the Archive Directory.

Received Faxes

The Store Directory is a folder entitled Received Faxes located on the Small Business Server computer. The built-in group Everyone has Read and Execute, List Folder Contents, and Read NTFS–based permissions. Received faxes are stored at the following location:

%systemroot%\Documents and Settings\All Users\Application Data\Microsoft\Shared Fax\Inbox

Archive Directory

The Archive Directory is a folder entitled Sent Faxes located on the Small Business Server computer. It can only be enabled on an NTFS file system partition. The built-in group Everyone has Read and Execute, List Folder Contents, and Read NTFS–based permissions. Sent faxes are stored at the following location:

%systemroot%\Documents and Settings\All Users\Application Data\Microsoft\Shared Fax\SentItems

Cover Pages

A cover page is the first page of a faxed document. It provides the recipient and sender with information, such as sender name, company, and fax number. Typically, a cover page is sent as an introduction to an accompanying document, but it can also be sent alone as a note.

The following two cover page template groups are available for fax printers in Small Business Server:

• Global
• Existing (Stored)
• Personal

Global Cover Pages

When Small Business Server installs Shared Fax Service, it sets up a fax printer and assigns four default cover pages—called global cover pages—that users can send with faxes. Shared Fax Service provides global cover page templates for simplicity, speed of use for first-time users, and controlled access to personal cover pages.

There are four global cover page templates:

• Confident
• FYI
• Generic
• Urgent

These templates are stored at the following location:

%systemroot%\Documents and Settings\All Users\Documents\My Faxes\Common Cover Pages\Personal Cover Pages

Users can choose personal cover pages by using the Send Fax Wizard if the administrator has enabled the option for them. Sometimes this option is not enabled. Denial of access to personal cover pages is a Small Business Server feature that the technology consultant can use to prevent employees from using inappropriate fax cover pages on a Small Business Server network. For example, some independent software vendors (ISVs) provide fax cover pages that contain cartoon characters uttering humorous phrases. Many businesses find these covers pages unacceptable and distasteful in a business climate. Access to all personal cover pages, even those created in other fax programs, depends on whether the administrator has enabled the option for each user individually.

Creating Cover Pages

Users can create and modify cover pages and store them on the server or local workstation. They can do this by selecting Edit Fax Cover Page on the Tips—Microsoft Shared Fax page, and then working in the Fax Cover Page Editor.

Receiving and Routing Incoming Faxes

When Small Business Server installs Shared Fax Service, all the fax modems on the computer are enabled to only send faxes. To receive a fax, complete the following steps.

To receive a fax

1. Click Start, point to Small Business Server Administrator Console, and then click Microsoft Shared Fax (Local).
2. Expand the Devices and Providers folder.
3. Expand Devices.
4. Right-click the modem device, and then click Receive.

For each fax modem, you can specify the following routing options for received faxes. The options are accessed by using the Fax Administration Tool, and then clicking Global methods in the Incoming Faxing folder:

• Print. Automatically print faxes as they are received.
• Store in a folder. Save faxes in a shared folder anywhere on the network. You can view these faxes by using a Tagged Image File Format (TIFF) viewer. In a typical installation, all client computers have access to the share. To select the folder that will store the faxes, in the Microsoft Shared Fax (Local) Properties dialog box, on the Inbox tab, complete the Archive folder field. The box can be accessed from the Small Business Administrator Console by right-clicking on Microsoft Shared Fax (Local), and then selecting Properties.

---

NOTE:
If you archive sent and received faxes, delete them periodically from the saved location to conserve disk space.

---

• Routing through e-mail. You can send faxes to a Simple Mail Transfer Protocol (SMTP) e-mail address if Exchange Server is installed. Faxes are saved as an attachment to the e-mail message by using the TIFF file format. After received, you can view the fax with a TIFF viewer. You can configure fax routing in the Microsoft Shared Fax (Local) Properties box, on the Receipts tab. Select the Use this configuration for the Microsoft Route through e-mail incoming routing method check box and complete the From e-mail address and Server address fields.

After installation, fax modems can be disabled or enabled to receive faxes, and the routing of faxes can be changed. For example, all received faxes could be sent to an office manager’s mailbox. The office manager could then open the faxes in the fax viewer and use the Send command to forward each fax to the addressee on the cover page.

Figure 18.4 illustrates the various ways a fax can be received and routed.

Figure 18.4 Receiving a fax with Small Business Server (Image unavailable)

Fax and E-mail Integration

Small Business Server 2000 integrates fax and e-mail services by routing messages between the Shared Fax Service and Exchange Server. With Small Business Server 2000, you can:

• Receive and view incoming fax messages in your Outlook 2000 Inbox.
• Send fax messages to a contact from Outlook 2000.
• Create distribution lists that contain both e-mail addresses and fax numbers.
• Send faxes to contacts by using the Microsoft Windows^® Send To command.

Faxing Documents from the Small Business Server Network

On the Small Business Server 2000 network, there are several ways to fax documents, as described in the sections that follow. The discussion begins with creating a fax address in Exchange 2000 Server.

Creating a Fax Address

A fax address is required when faxing documents and messages by using Outlook 2000. Outlook 2000 automatically creates a fax address for each contact’s fax number entered in the Outlook 2000 Contacts folder. To fax by using Outlook 2000, however, you must first create a fax recipient contact record in Exchange 2000 Server.

Use the following procedure to create a fax address record in Exchange 2000 Server.

To create a fax address in Exchange 2000 Server

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Small Business Server Administrator Console.
2. In the Console Tree, select Active Directory Users and Computers.
3. Right-click the folder (for example, Users) or organizational unit (for example, MyBusiness) in which you want to create a fax address, click New, and then click Contact to start the New Object – Contact Wizard.
4. In the First Name and Last Name fields, type the fax recipient’s first and last name. The Full Name field will automatically appear with the contents of the First Name and Last Name fields. Completing the Initials field is optional because not all fax recipients have a middle name. Click Next.
5. On the untitled page that appears, you can create an Exchange e-mail address for this fax recipient. To do so, click Create an Exchange e-mail address, and then click Next.
6. On the next untitled page that appears, click Finish to close the New Object – Contact Wizard.
7. In the Details Pane, right-click the contact you just created, and then click Properties.
8. The contact’s property sheet appears. Click the Telephones tab.
9. In the Fax field, type the fax telephone number, and then click OK.

---

NOTE:
Outlook 2000 supports dial-as-entered faxing capabilities. This allows you to enter a fax telephone number directly in the To field of an Outlook 2000 message. In the To field, type [fax: xxxxxxx] where xxxxxxx is the fax telephone number.

---

Faxing a Document with the Print Command

By using an application’s Print command, you can fax any document by using the Send Fax Wizard (as described in the following procedure). You can also fax a document by choosing a fax address from the Outlook 2000 Address Book if an e-mail client is installed.

To send a fax by using the Print command, perform the following steps.

To fax a document by using the Print command

1. Open the document you want to fax.

---

NOTE:
You can also right-click the document, and then click Print.

---

2. On the File menu, click Print (or follow the procedure for printing documents in your application).
3. Select a fax printer, and then in the Print dialog box, click OK. The Send Fax Wizard appears.
4. On the Welcome page, click Next.
5. On the Recipient Information page, click Address Book (if an e-mail client is installed) or type a name in the To field and a fax number in the Fax number field. If you are sending a fax to another country, in the Location list, select a country dialing code (for example, 011).
6. Click Next.
7. To send a fax to more than one recipient, click Add, and then repeat Steps 5 and 6.
8. Click Next, and then follow the on-screen instructions to add a cover page and send the fax.

---

NOTE:
Do not use the Fax Recipient command on the File menu to send a fax with Shared Fax Service. This menu item is intended for use with the stand-alone version of Microsoft Fax and does not work in Small Business Server 2000 Shared Fax Service.

---

NOTE:
To enable a user to send faxes from Microsoft Access, change the spool settings of the client computer’s fax printer to a Windows Enhanced Metafile (EMF).

---

Faxing a Message from Outlook 2000

A message can be sent from Outlook 2000 to fax and e-mail addresses separately or concurrently. Messages are composed and documents can be inserted as in any other message, either from Outlook 2000 or from your desktop by using the Send-To command.

Almost any type of file can be sent through Outlook 2000 as an e-mail message; however, the file must be rendered properly to be sent to a fax contact. To send a fax from Outlook 2000, follow the steps below.

To fax a message from Outlook 2000

1. Compose an e-mail message.
2. In the To or Cc fields, specify one or more fax addresses.
3. If you are sending messages to both fax and e-mail addresses, specify the e-mail addresses.
4. Click Send to send the message.

To fax a message from your desktop

1. Right-click a document, point to Send To, and then click Mail Recipient.
2. The Outlook New Message dialog box appears with the Global Address List and Personal and Shared Contact lists available. Specify your recipient, and then click Send. The document is routed to the fax server.

Faxing a Document from Office 2000 Applications

Faxes can also be sent from Office 2000 applications. This is typically accomplished by using the Print command, as described previously. For more information, refer to the Microsoft Office 2000 Resource Kit or Online Help for any Office 2000 application.

Shared Fax Service—Remote Administration

This section discusses the remote administration of the Shared Fax Service. The service has two components: remote administration setup and client setup.

• Remote Administration Setup. When installed on an additional Windows 2000–based computer (connected through a network to the server running Shared Fax Service), this configuration enables a technology consultant to remotely configure and monitor the system, set security permissions, define routing methods, send and receive faxes, and view, manage, and archive faxes in the server’s queues.

To install the Shared Fax Service on another Windows 2000–based computer

a. On the remote computer, insert the Small Business Server 2000 Disc 2 into the disc drive, and then in the \FAX\Server folder, double-click setup.exe.

b. On the Welcome page, click Next.

c. On the Customer Information page, type a user name in User Name and an organization name in Organization, and then click Next.

d. On the Setup Type page, select Complete, and then click Next.

e. On the Ready to Install the Program page, click Install.

f. On the Completing the Microsoft Shared Fax Setup Wizard page, click Finish.

g. On the desktop of the computer on which Shared Fax Service was installed, right-click My Computer, and then click Manage.

h. In the Computer Management snap-in, right-click Computer Management (Local), and then click Connect to another computer.

i. In the Select Computer dialog box, select the computer running Shared Fax Service to manage, and then click OK.

j. Expand the Services and Applications folder, and then select Microsoft Shared Fax to manage the Shared Fax Service on the remote computer.

• Client Setup. This configuration installs only the Shared Fax Console, including the necessary printer drivers and the Outlook extensions required to send faxes. After the console is installed, the user can send and receive faxes and can view and archive faxes in the server’s incoming and outgoing fax queues.

Shared Modem Service

The Shared Modem Service enables Small Business Server users to use modems installed on the server and to connect to remote networks, bulletin board systems, and online services hosted by Internet service providers. When modems installed on the Small Business Server computer are shared, hardware costs are reduced because users do not need modems for their individual computers. Users can connect to and use the modem pool in the same way they use modems connected to the Component Object Model (COM) ports on their computers. When users need access to a remote network or online service, the modem sharing application is started. This application uses a COM port connected over the network to a modem pool on Small Business Server.

Shared Modem Service also enables you to pool together modems on the Small Business Server computer. When a modem from the modem pool becomes available, it dials the remote network or online service. If there is more than one modem in the modem pool, the server automatically uses the next available (idle) modem in the pool.

Administering the Shared Modem Service

The technology consultant has the option of installing the Shared Modem Service as part of Small Business Server Setup. The following section explains how to administer and configure the Shared Modem Service.

To manage the Shared Modem Service

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Shared Modem Service to start the Shared Modem Service Admin application.
3. You can now perform the following tasks:
• Add, remove, and configure modem pools.
• Add or remove a modem from a pool.
• View the status of a modem pool.
• Troubleshoot modem pool problems.

Viewing and Configuring Modem Pools

To view the modem pool from the Small Business Server 2000 server computer, you must specify the modem pool name when connecting to it on the server. You can view modem pool names on the Shared Modem Service Admin Configuration tab.

After installing Small Business Server, you must configure the modem pool in Shared Modem Service if you plan to use this capability.

To manually configure modem pools on the server

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Shared Modem Service to start the Shared Modem Service Admin program.
3. Click the Configuration tab.
4. In the Pool pane, select the modem pool name.
5. Add or remove COM ports as follows:
• To add a COM port to the modem pool: In the Available for Pool box, select the COM port, and then click the right arrow. The COM port appears in the Assigned to Pool box along with the other COM ports assigned to the pool.
• To remove a COM port from the modem pool: In the Assigned to Pool box, select the COM port, and then click the left arrow. The COM port appears in the Available for Pool box.

6. Click Apply.
7. Click the General tab, click Stop, and then click Start to restart the service and apply the changes to Shared Modem Service.

You can also automatically configure the modem pool. If your server has no modem pools configured, you can use the Auto Configure option to configure a modem pool. Auto Configure scans your server for modem devices and groups them into modem pools according to the modem type. If a modem is not defined on a port, the serial port is added to the list of available ports.

You can manually start the application by performing the following steps.

To use the Auto Configure option

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Modem Sharing.
3. Click the Configuration tab, and then click Auto Configure.
4. Click Apply.
5. Click the General tab, click Stop, and then click Start to restart the service and apply the changes to Shared Modem Service.

Configuring Clients for Modem Pool Connection

Shared Modem Service supports client computers running Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Me, Microsoft Windows NT^® 4.0 Workstation, and Windows 2000. The modem sharing client must be installed by the Set Up Computer Wizard, and a modem driver (the same as the one on the server) must be configured before connecting to the modem pool.

Connecting Windows 2000–Based Clients to the Modem Pool

During client setup, a modem sharing port is installed on the client computer. To use this shared port, you must first add the shared port, then install a modem, and then configure it to use the shared port. This configuration starts after you open the following file:

\\%servername%\ClientApps5\Modem Sharing Client\win2k\netsetupwin2k –a install –c client –i \\server\share\win2k\netsetupwin2k\netsrdr.inf

• Follow the on-screen instructions to complete the configuration. For more information about how this is accomplished, refer to Microsoft Knowledge Base Article Q224791 at: http://www.microsoft.com/technet/.

Connecting Windows NT 4.0 Workstation–Based Clients to the Modem Pool

During client setup, a modem sharing port is installed on the client computer. To use this shared port, you must first install a modem and then configure it to use the shared port by performing the following steps.

To install a modem

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Modems.
3. Follow the on-screen instructions to install a modem. Install the modem that matches the modem attached to the server computer.

To configure the modem sharing port

• Run the following command, and then follow the on-screen instructions:

\\%servername%\ClientApps5\Modem Sharing Client\nt4\mpsetupnt4.cmd \\%servername%\ClientApps5\Modem Sharing Client\nt4\

Connecting Windows Me, Windows 98, and Windows 95–Based Clients to the Modem Pool

During client setup, a modem sharing port is installed on the client computer. To use this shared port, you must first install a modem and then configure it to use the shared port by performing the following steps.

To install a modem

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Modems.
3. Follow the on-screen instructions to install a modem. Install the modem that matches the modem attached to the server computer.

To connect Windows Me, Windows 98, and Windows 95–based computers to the modem pool

• Run the following command, and then complete the on-screen instructions:

\\%servername%\ClientApps5\Modem Sharing Client\win95/setup.exe

After the client computer is connected to the modem pool, the remote serial port is used as if it were a local serial port. To run client applications that require a shared modem—for example, Routing and Remote Access Service (RRAS) or an Internet service provider (ISP)–hosted service—you must first install a modem on the newly connected remote port. For more details, refer to Small Business Server Online Help.

Status Monitoring

Follow these steps to view the status of a modem pool, including the number of active connections and the users that are connected.

To view the status of a modem pool

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Shared Modem Service.
3. Click the Status tab.
4. In the Modem Pool list, select the modem pool you want to view. The status of the modem pool, including connection information, appears.
5. Click OK.

Exchange 2000 Server

Exchange 2000 Server is a client/server messaging system that integrates e–mail, rules, group scheduling, electronic forms, groupware, and Internet connectivity. As an integrated application of Small Business Server 2000, the Exchange Server platform is scaled and optimized for the typical small business application. When Small Business Server 2000 is installed, Exchange Server is set up automatically to support the small business configuration.

When Small Business Server is up and running, Exchange is managed with console wizards to create the appropriate operating configurations for Exchange and other integrated applications. However, Exchange Server is also accessible as a stand-alone application on Small Business Server, which gives the technology consultant more manual control of certain Exchange features and interactions beyond the Small Business Server automatic configuration.

This section discusses several Exchange features and tools available to the technology consultant for fine-tuning the messaging system of the small business network.

System Manager Interface

All Exchange Server components can be accessed through System Manager. System Manager displays the small business organization hierarchically, making it easy to navigate and manage the elements at each level. System Manager is the tool displayed when you select First Organization (Exchange) in the Small Business Server Administrator Console.

Mailboxes

You can configure end-user mailboxes manually through Active Directory Users and Computers (available from the Small Business Server Administrator Console). By selecting the properties for an end user, you can see the additional Exchange Server–related tabs, as shown in Figure 18.5.

Figure 18.5 Exchange Server–related user properties (Image unavailable)

Mailboxes can be used as a repository for a wide range of data about each employee in the small business.

Distribution Groups

Distribution groups are groups of users combined into one list, allowing the users to be addressed as one user. A large mail system might include many distribution lists, often totaling more than the number of single mailboxes. Distribution groups are created with Small Business Server wizards, but can also be generated manually with Active Directory Users and Computers, available from the Small Business Server Administrator Console.

End-User Management of Distribution Groups

The Exchange permissions model can be used to delegate management of certain distribution lists to specified users, providing an element of decentralized control in a centralized administration model. The model also facilitates departmental distribution lists, allowing members to be added to a team-specific distribution list, controlled at the team level.

To create or add users to a distribution list

• From the Small Business Server Personal Console, click the Add E-mail Group taskpad.

-Or-

• From the Small Business Server Administrator Console Favorites tab, click Small Business Server Tips, click Exchange 2000 Server, and then click Add E-mail Group.

Distribution List Options

Exchange Server automates distribution list management, making it cost effective for the small business to offer users a wide range of distribution list options.

Custom Recipients

Custom recipients are addresses of users on other mail systems that appear in the Exchange Server address book because they are used frequently by users in the small business network. The technology consultant can use Active Directory Users and Computers to create custom recipients.

Address Formats

Custom recipient addresses can appear in two ways:

• In a format that clearly depicts them as users of another mail system.
• In a format indistinguishable from Exchange Server user addresses.

The latter is particularly useful in a migration/coexistence scenario in which users will be migrated to Exchange Server gradually. For instance, representing IBM PROFS users in the Exchange Server format sets the stage for a seamless migration strategy.

When users are migrated to Exchange Server, their display names remain unchanged in the address book. Therefore, other users do not need to change the way they communicate with migrating colleagues.

Custom recipients appear in the address book in the same way as users of Exchange Server. They can be sent mail or included in distribution lists in the same way as regular Exchange Server users. You can create, manage, and delete custom recipients by using the same methods employed for mailboxes and distribution lists.

Address Lists

Address lists are virtual containers that enable the technology consultant to group recipient objects together logically, based on common directory attributes. By grouping recipients together in views, the technology consultant can sort recipient lists according to tasks or functions.

For example, the technology consultant needs to scroll to a particular recipient or use the Find feature to modify or obtain information in a directory with a large number of entries. Although there are tools to do this easily, having users grouped specifically by job functions allows the technology consultant to locate the entry in a manner more suitable to the small business context. Views do not provide filtering; they provide only groupings of users.

To create address lists by using System Manager

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Click Recipients.
3. Right-click All Address Lists, point to New, and then click Address List.

The technology consultant can create a display name for the Address List and can control how the address view is grouped, based on filters assigned to the mailbox user (city, state, site, custom attributes, and so on).

Recipient Policies

Recipient Policies is an object found in the System Manager’s Recipients container. It allows an organization to manage numerous Internet e-mail identities by Internet domain names. For example, a small business might use more than one Internet domain name because several small businesses in the same office space use the same Small Business Server network. By using Recipient Policies, the Exchange Server in Small Business Server can manage the distribution of e-mail to different Internet domain names. This happens when a customer has registered multiple domain names, a common occurrence in the business community. For example, a customer might have registered adatumcorporation.com and adatumcorporation.net. Recipient policies would then allow Exchange 2000 Server to manage and distribute Internet e-mail bound for recipients of either of the Internet domains.

Public Folders

The public folder is another object on an Exchange Server that can be configured manually by using System Manager. Although the technology consultant can create public folders from either System Manager or the e-mail client, public folders are managed from System Manager in the same way as other end-user objects.

Exchange public folders can be created by using Outlook 2000. They can contain company-wide shared fax and e-mail contacts, which can then be configured as a shared contacts list (address book) for use in Outlook 2000. Individual users can add contacts to this public address book. In contrast, however, the Global Address List can only be configured by using the Exchange Administrator application, which is used to administer Exchange 2000 Server

To start Exchange 2000 Server

• Click Start, point to Small Business Server Administrator, and then click First Organization (Exchange). The Exchange Administrator application appears in the Detail Pane. Note that First Organization is the default name. After you select it, however, its name refreshes to reflect your network basic input/output system (NetBIOS) domain name (for example, ADatumCorp).

To create a company-wide shared contacts list in Exchange Server by using Outlook 2000, perform the steps below.

To create a shared contacts list in Exchange Server by using Outlook 2000

1. In Outlook 2000, expand Public Folders.
2. Right-click All Public Folders, and then click New Folder.
3. In the Name field, type a name for the shared contacts list, and then in the Folder contains list, select Contact Items.
4. Click OK.

Off-Line Folder Synchronization

Exchange Server enables users to automatically perform two-way synchronization between a server folder and a copy of that folder on a local computer. Offline folder synchronization enables users to maintain up-to-date information without having to be continuously connected to the small business network.

For example, a user can create an off-line folder (a snapshot or replica) of a customer-tracking application to take along on a business trip. He or she can then update the folder based on customer interactions during the trip. By reconnecting to the server—either remotely through a modem or through the small business local network when the user returns to the office—the user can bidirectionally synchronize the off-line and server folders. Changes made on the local computer, including forms and views, are updated to the server, and changes to the server-based folders automatically show up on the user’s computer.

Creating an off-line folder is different from simply copying a server folder to the hard disk because an off-line folder remembers its relationship with the server folder and uses that relationship to perform the bidirectional update. Only changes are copied—not the whole folder. This helps minimize network traffic and congestion.

An off-line folder is created in Outlook. First, users specify that they want an off-line folder (.ost), and then they set up offline synchronization in the folder properties. For more information, refer to Outlook Help.

Off-line folder synchronization provides an alternative to continuous network connection. Exchange Server supports off-line folder synchronization sessions from many different locations simultaneously. Built-in conflict resolution for public folders ensures that all changes are added. The owner of the folder is notified of any conflicts and is asked which version to keep.

Protecting Exchange Data

Exchange Server includes an enhanced version of the Windows 2000 Backup utility. This utility includes all the standard file and directory backup functions and includes the ability to back up and restore Exchange Server directories and information stores.

Backups are performed while Small Business Server is up and running, so downtime is not necessary to secure the data. The new Windows 2000 Backup utility recognizes Exchange Server and backs up the directory and/or information store as an object. It is not necessary to know which files make up the service; you must know only the components that are to be backed up.

Backups can be full, differential, incremental, or copy. Exchange Server backup capabilities are also included in the command-line mode of Windows 2000 Backup, which allows backup tasks to be batched and scheduled. For more information about using the Backup utility, refer to Chapter 26, "Disaster Recovery," or the Small Business Server Help.

Exchange Administration Tips

This section provides several tips for Exchange Server administration, including the automation of e-mail forwarding and Web access to Exchange.

Automating E-mail Forwarding

You can configure automatic e-mail forwarding by performing the steps below.

Configuring e-mail forwarding

1. Click Start, point to Programs, and then click Small Business Server Administrator Console.
2. Select Active Directory Users and Computers.
3. Select the Users folder.
4. Right-click on a user, and then click Properties.
5. Click the Exchange General tab.
6. Click Delivery Options.
7. Select Forward to, and then specify the forwarding e-mail address for the user.
8. Click OK to close the Delivery Options dialog box.
9. Click OK to close Properties for the user.

Web Access to Exchange

Exchange Server can be accessed over the Internet by using a Web browser. This feature, also known as Outlook Web Access (OWA), is automatically installed and configured when Small Business Server is set up. OWA is shown in Figure 18.6.

Figure 18.6 Outlook Web Access (Image unavailable)

Accessing Exchange from the Internet does not compromise security because ISA Server blocks all access to client computers on the small business network. When OWA establishes a connection to Exchange Server, the user can do the following:

• Send and receive e-mail.
• Use Calendar.
• Use Contacts.
• Review and publish to public folders.
• View the Global Address List.

When an e-mail message, public folder, Global Address List, or other Exchange resource is viewed with a browser, OWA converts it to HTML. In addition, inbound access to Exchange resources (through a browser) requires conversion from HTML to a MAPI-based call. OWA uses Exchange Active Server Pages (ASP) and Collaboration Data Objects (CDOs) for the conversion.

Monitoring the Performance of Exchange Server

Small Business Server 2000 includes tools for monitoring the performance of Exchange Server. Two such tools are System Monitor and Health Monitor, both of which are discussed in the sections that follow. The technology consultant can use the performance monitoring information to make decisions about improving the performance of Exchange Server.

System Monitor

Windows 2000 System Monitor is a tool that enables the technology consultant to collect and analyze performance data on the Exchange Server. This tool was used to preconfigure several key performance monitors supplied with Exchange Server, and it enables the technology consultant to maintain an accurate view of the overall health of Exchange Server in the small business network.

System Monitor (which can be accessed on the Start menu by pointing to Programs, clicking Administrative Tools, and then clicking Performance) provides quick system feedback and statistics to help the technology consultant detect and eliminate problems before they occur.

System Monitor can provide the technology consultant with statistics on more than 300 system characteristics for processor, process, memory, disk, and network objects. The counters in System Monitor can be used to view such things as access bottlenecks and errors, browse operations, reads/writes, and thread use on the Exchange directory, Exchange Information Store, and other Exchange services. By using the features of System Monitor, the technology consultant can easily determine the load and activity of users requesting addresses or updating directory information in the small business network.

Exchange Server Performance Monitoring

Figure 18.7 provides an overview of the processes involved in setting up accurate and meaningful performance monitors for Exchange Server.

Figure 18.7 Exchange Server performance monitoring process  (Image unavailable)

Health -Monitor 2.1, accessed from the Small Business Server Administrator Console, has several performance counters for monitoring Exchange Server in real time. Sample Exchange Server performance counter data groups include Exchange Server Information Store, Exchange Server Message Transfer Agent, and SMTP Server. You can also create your own performance counter data groups for Exchange Server in Health Monitor.

Ways to Monitor Performance

The sections that follow describe ways in which you can use System Monitor to assess Exchange Server performance.

Data Collection and Analysis

Exchange 2000 Server is a complex application with multiple components that place varying performance demands on Small Business Server. For example, the Information Store must manage all communication with the various clients connecting to the server. To understand how this and other demands translate to actual system performance in the small business environment, it is useful to collect and analyze data.

Data collection involves running a number of performance monitor tests over defined periods and logging the results to a file for analysis. If the correct set of counters is used in the tests, you can easily assess the major performance characteristics of Exchange Server. It is recommended that you perform this process periodically to identify long-term trends in server performance.

When using the counters for data collection, you create performance monitor charts that write performance data to log files. The duration of the logging process depends on user capacity. In most cases, the data collection period is a minimum of one day and a maximum of one week. It is important to consider the counter sampling rate. The sampling frequency must be short enough to get a realistic average, but not so long that you run the risk of missing temporary spikes. In general, sampling ranges between 20 minutes and 120 minutes are suitable for data collection purposes.

Disk space requirements must also be considered because log file growth will vary proportionally with the sample frequency selected. For more information about log configuring, refer to "Configuring Log Files for Data Collection" later in this chapter.

In Small Business Server, Exchange 2000 Server and Windows 2000 Server are tightly integrated. As a result, several areas of both servers should be monitored. The critical subsystems are:

• System memory
• Disk input/output (I/O)
• System CPU
• Information Store (IS)

The first three in the preceding list deal with standard Windows 2000 Server counters used to detect degradation in performance. The fourth deals with counters that monitor user access to the IS.

Collecting and analyzing data is invaluable for developing a comprehensive understanding of Exchange Server performance characteristics. Such understanding is essential for defining realistic baselines for Exchange Server usage and capacity.

When a performance problem is detected, System Monitor can be used to identify the system component that may be the cause of the problem. However, the effectiveness of using System Monitor in this way is greatly dependent on the technology consultant’s level of understanding.

Performance Baseline Definition

The predefined performance monitors included with Exchange Server are set up with counters, but not with counter thresholds, because counter threshold levels are uniquely dependent on the usage characteristics of the small business network. Before using the predefined Exchange performance monitors, you need to establish an Exchange usage, capacity, and performance counter threshold profile by collecting initial data on the system.

By using the information gathered in the data collection process, baseline performance thresholds can be defined. These thresholds are based on the load characteristics present during the data collection period. It will become obvious if these thresholds are incorrect—thresholds set too low will generate unnecessary alerts, and those set too high might result in undetected problems.

After thresholds have been defined, System Monitor can be configured to alert the appropriate support group when a particular threshold has been exceeded. Methods for configuring System Monitor are discussed in Chapter 17, "Monitoring and Optimizing Small Business Server Components."

Exchange Usage Characteristics

Over time, the usage characteristics of Exchange Server may change, impairing performance. Changes in usage levels can be detected early if they are measured on a regular basis.

For example, a common characteristic of e-mail systems is the gradual increase in the average message size. Continuous monitoring of message size can provide early warning of any trends. To detect changes in usage levels, you must first define basic service expectations so you can establish a substantial basis for comparison.

Defining Service Levels

Defining baseline service levels is the most effective way to measure future performance. Some service levels that you may want to define are as follows:

• Service delivery parameters, including:
• System availability
• Average message delivery time
• Average time to read a message
• Average time to send a message

• Service usage assumptions, including:
• Maximum user mailbox size
• Average message size
• Average number of active users
• Average number of messages sent per user per day

When these levels are defined and understood by both the service delivery and user groups, a clear framework in which to work can be established.

Conducting Performance Monitoring

The technology consultant should read the following resources to create appropriate system monitors in System Monitor and to engage in performance analysis:

• Microsoft Exchange 2000 Server Resource Kit
• Microsoft Windows 2000 Professional Resource Kit, Part 6, "Performance Monitoring"
• Microsoft Windows 2000 Server Resource Kit, Operations Guide, Part 2, "Performance Monitoring"

Configuring Log Files for Data Collection

By default, Exchange Server performs basic logging, which includes information events such as backup and restore success or failures, service initialization or shutdown, and background maintenance notifications. More importantly, it also logs events such as low disk space warnings or IS and directory services database errors. Exchange Server generally logs any event errors or warnings that may cause degradation or disruption of service.

To implement the initial data collection phase, you need to set up a System Monitor log file for the counters and an alert log.

During normal Exchange Server operation in the network, alerts should be reported to the Event Log to maintain a record of alerts in real time. Figure 18.8 provides an overview of the processes involved when setting up Exchange Server logs for both the initial data collection phase and thereafter.

Figure 18.8 Exchange Server logging processes (Image unavailable)

Health Monitor 2.1 and Exchange Server Monitoring

Small Business Server’s Health Monitor 2.1 provides built-in sample monitors for monitoring and alerting the technology consultant about Exchanger 2000 Server performance. The sample monitors can be accessed in Exchange 2000 Server by using the steps that follow.

Using Exchange Server sample monitors in Health Monitor

1. Click Start, point to Programs, and then click Small Business Server Administrator Console.
2. Select Health Monitor.
3. Expand All Monitored Computers.
4. Expand the server icon named after your Small Business Server 2000 server computer (for example, ADC1).
5. Expand Health Monitor Sample Monitors.
6. Expand BackOffice Application Monitors.
7. Expand the Exchange 2000 Server 2000 folder, and then observe the predefined monitors in the Performance Counters and Services folders.
8. Right-click on any performance counter, and then click Properties to observe how the performance counter has been configured.

---

NOTE:
Health Monitor is discussed in more detail in Chapter 17, "Monitoring and Optimizing Small Business Server Components."

---

Internet Security and Acceleration Server

ISA Server is an extensible firewall with high-performance content caching that provides secure and managed Internet access for small business client computers. As an integrated application of Small Business Server 2000, the ISA Server platform is optimized for the typical small business application. When Small Business Server 2000 is installed, ISA Server is set up automatically to support the small business configuration.

Protection features used by ISA Server that contribute to its ability to provide security on a single Small Business Server 2000 computer include:

• Dynamic port filtering; ports are opened only when needed.
• Domain filtering to restrict visited domains.
• Network Address Translation (NAT) to shield the internal network from external browsing.

After Small Business Server is up and running, the ISA Administration Tool, available from the Microsoft ISA Server program group, allows management of Internet access permissions on a per-user basis.

This section discusses several key ISA features that can be configured manually by the technology consultant to enhance small business Internet access management. This information is supplementary to the ISA online documentation. ISA Server system monitoring is also discussed.

User Access Control

A small business might be concerned that too much employee time is spent surfing the Internet, which detracts from productivity, and might want a way to control Internet access selectively. You can use ISA Server to limit employee Internet activity on the small business network or to deny access altogether.

With ISA Server, the technology consultant has control over Internet and intranet resources. Access privileges can be applied to the entire small business organization or only to individual users.

For example, the technology consultant may allow browser-based World Wide Web access for all employees, yet permit only certain managers to use the Internet for conferencing or other multimedia services. By configuring the access protocol for users, the technology consultant controls the type of resources users can access on the Internet.

Windows 2000 Active Directory and User Access Control

User names and domain information in the Windows 2000 Server Active Directory^™ directory service is the basis for user access control, because ISA Server is tightly integrated with this directory service. As a result, the technology cons ultant does not have to maintain a separate database or directory of Internet users.

Security

To configure ISA security—including packet filtering, site and content rules, alerting, and logging—select Internet Security and Acceleration Server 2000 in the Small Business Server Administrator Console. The technology consultant can configure these services manually to enhance or customize ISA in several ways.

Dynamic Packet Filtering

Packet filtering is a security feature of ISA Server. When packet filtering is enabled, all ports in the firewall are closed until opened by an access request. After the request, the ports are shut again unless a response is required, in which case the port stays open until the request is received. When a request opens a port, only certain types of packets are allowed to be interchanged at the external interface, depending on the protocols specified.

Dynamic packet filtering is configured by using the Small Business Server Internet Connection Wizard for most Small Business Server needs. You can manually configure dynamic packet filtering by using the ISA Administration Tool. To create an Internet protocol (IP) packet filter, perform the steps that follow.

To create an IP packet filter

1. Click Start, point to Programs, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Access Policy.
4. Right-click IP Packet Filters.
5. Click New, and then click Filter.
6. Follow the on-screen instructions to create the IP packet filter.

1. Click Start, point to Programs, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Access Policy.
4. Right-click IP Packets Filters, and then click Properties.
5. Click the General tab, and then select the Enable Packet filtering check box.
6. Click OK.

If intrusion detection is enabled, you can configure alerts to occur on rejected packets. These alerts are usually a sign that a network intruder is trying to breach the server. (Even though the ports are closed, they are still monitored.) To configure alerting, perform the steps that follow.

To enable intrusion detection and alerting

1. Click Start, point to Programs, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Access Policy.
4. Right-click IP Packets Filters, and then click Properties.
5. Click the General tab, and then select the Enable Intrusion detection check box.
6. Click the Intrusion Detection tab. Configure the options on the Intrusion Detection tab, as shown in Figure 18.9, and then click OK.

Figure 18.9 Configuring intrusion detection (Image unavailable)

7. Expand the Monitoring Configuration folder.
8. Click Alerts. In the Details Pane, observe the alerts that have been configured.
9. Double-click on an alert.
10. Click the General tab, and then click Enable.
11. Click OK.

Alerts are reported to the Event Viewer, which the technology consultant should monitor regularly, especially for attempted intrusion events. Alert notification can be sent by SMTP mail to a recipient. Click the Action tab in an alert’s property dialog box to configure e-mail notification.

Site and Content Rules

Site and content rules in ISA Server allow the technology consultant to selectively deny or allow small business network access to specific Web sites, computers, or groups of computers. This rule-based filtering feature applies to sites on the Internet or on the small business intranet. The technology consultant has the ability to indicate a specific IP address, a range of IP addresses for a group of computers, or a domain name for any ISA service (Web, Winsock, or SOCKS). Defaults can be set to grant access with exceptions or to deny access with exceptions. The following steps describe how to create a site and content rule.

To create a site filter

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Access Policy.
4. Expand the Site and Content Rules folder.
5. In the Details Pane, click Create site and content rule, and then follow the on-screen instructions to create the site filter.

Value-Added Site Filtering Services

With new Web sites going live every day, it can be an ongoing challenge for a technology consultant to know the address of every Internet site that has material that should be filtered for users. This has initiated the development of value-added services that complement the core site-filtering features of ISA Server.

Third-Party Filtering Services

Third-party solution developers that use the extensibility of ISA Server can offer subscription services that plug in to ISA Server site filtering. With these services, a technology consultant does not need to know the Web address for every undesirable Web site to be able to deny user access to those sites. Instead, the technology consultant can use a check box to select the categories of Web content to be filtered. The third-party companies offering filtering services maintain continuously updated lists of those sites by category as a value-added service.

Logging

ISA log files are text files that display ISA Server traffic activity. The technology consultant can configure several ISA log file parameters useful to the small business by performing the following steps.

To configure ISA Server logging

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Monitoring Configuration.
4. In the Details Pane, double-click a component (log type). The properties for the log type appear.
5. Click the Log tab, and then select whether to log to a file or a database. The File option logs to a text file. The Database option logs to a database table.
6. Click OK.

---

NOTE:
By default, logs are compressed to save space on the local hard disk.

---

Reporting

ISA Server provides reports that the technology consultant can review to monitor firewall and Web browsing activity. The following reports are included with ISA Server:

• Summary
• Web Usage
• Application Usage
• Traffic and Utilization
• Security

To view ISA Server Reports

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Monitoring.
4. Expand Reports, and then select the report of your choice.

ISA Local Address Table

The Local Address Table (LAT) maintains a record of the IP address range that spans the internal network address space. This tells ISA Server whether client-requested IP addresses are to be found on the intranet or Internet so appropriate routing can occur. When a client computer in the small business network makes a URL request from the Internet, the LAT tells ISA Server to route that request outside the local address space and to the Internet. When the resource is retrieved, ISA Server consults the LAT, which then tells it where to route the request to the requesting network client.

The IP address range for the Small Business Server computer (the static IP address assigned to the internal network card) in the ISA LAT is also configured by default during Small Business Server Setup. The only time the LAT may need to be reconfigured is if the base IP address of Small Business Server is changed. If this is required, the IP address range in the LAT must be changed for compatibility with the new base IP address of the server. This is also necessary because the LAT enables ISA Server to distinguish between internal non-routable network IP addresses and external Internet-routable IP addresses. This is a security feature that prevents direct client connection with Internet hosts (having external IP addresses). Before the LAT is modified, the Dynamic Host Configuration Protocol (DHCP) Server scope must be changed to accommodate the new IP address range. The appropriate changes to the LAT can then be added automatically by performing the following steps.

To modify the LAT

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Network Configuration.
4. Right-click Local Address Table (LAT), and then click Construct LAT.
5. In the Construct LAT dialog box, configure the LAT, and then click OK.

---

NOTE:
You can add and delete IP address ranges manually.

---

Viewing Active Internet Sessions

The technology consultant can monitor ISA Server active sessions by performing the steps that follow.

To view active Internet sessions

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Monitoring.
4. Click the Sessions folder.

Caching

Caching is enabled by default during Small Business Server Setup. Caching helps to minimize the number of Internet accesses on frequently visited sites. However, it is not recommended that small businesses with dial-up Internet connections use active caching because this results in nonstop dial-ups at regular intervals to the Internet to update the cached sites.

To configure caching

1. Click Start, point to Programs, point to Microsoft Small Business Server, and then click Microsoft Small Business Server Administrator Console.
2. Expand Internet Security and Acceleration Server 2000.
3. Expand the Servers and Arrays folder, expand the array named after your Small Business Server, and then click Cache Configuration.
4. In the Details Pane, click Configure cache policy, and then follow the on-screen instructions to configure the cache.

---

NOTE:
The size of the cache can be limited to conserve disk space.

---

Using FTP

By default, File Transfer Protocol (FTP) for inbound requests from the Internet is not installed by Small Business Server 2000 Setup, although an optional installation procedure is provided in the Small Business Server 2000 Planning and Installation guide. Only FTP Read service is enabled on Small Business Server 2000 for outbound requests.

To use the FTP protocol for inbound requests, the FTP service must be installed and the FTP default site properties must be configured by performing the steps that follow.

To install FTP

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. In the Currently installed programs list, select Microsoft Small Business Server 2000.
4. Click Change/Remove.
5. Click Next until the Component Selection page appears.
6. Expand the Windows 2000 Optional Components folder.
7. Expand the Internet Information Services folder.
8. Configure Action to Maintenance.
9. Configure Action to Install for the FTP Service.
10. Click Next until the Completion page appears.
11. Click Finish.

To configure FTP

1. From the Small Business Server Administrator Console, expand the Internet Information Services folder.
2. Right-click the server object, click New, and then click FTP Site.
3. Follow the on-screen instructions to configure the FTP.

---

NOTE:
Technology consultants should be aware that using the FTP protocol with a full-time Internet connection to accommodate inbound requests poses a security risk to the small business network. This is not an issue for typical Small Business Server installations in which the ISP hosts the Web site. Also note that you will need to run the Small Business Server Internet Connection Wizard and select the FTP check box on the Configure Firewall Settings page to open Port 21 for FTP traffic.

---

Configuring System Monitor Alerts for ISA Server

ISA Server is heavily instrumented for performance counters. Several of these can be set up for ISA services to monitor Internet-related activities on the server and provide performance data and alerts that are meaningful to the small business application. To learn more about configuring System Monitor for ISA Server services, refer to the Microsoft Internet Security and Acceleration Server Resource Kit.

Firewall Client

The Firewall Client can be installed on the client computers from the Set Up Computer Wizard, which is integrated with the Add User Wizard when users are added. Alternatively, the Firewall Client can be installed by selecting Define Client Applications from the Small Business Server Administrator Console To Do List. The Firewall client directs Internet-bound traffic from the client computer through ISA Server on the Small Business Server network. By doing this, you can restrict what Internet activity is allowed and also protect client computers from potential outside intruders. The Firewall Client can be configured on the client computer by opening the Firewall Client icon in Control Panel.

SQL Server 2000

SQL Server 2000 is a component of Small Business Server 2000. It contains a very powerful and scalable database designed to facilitate solutions, ranging from mobile laptops running Windows 95/98/Me to small user group applications to terabyte symmetric multiprocessor clustering environments. As the small business expands, SQL Server 2000 easily supports growth in transactions, data handling, and users while maintaining essential security and reliability necessary for mission-critical business systems.

Migrating Access to SQL Server 2000

Access 2000, included with Microsoft Office 2000, is a relational database application for desktops that works best for individuals and workgroups who manage data in the scale of megabytes. The small business might be using Microsoft Access as a client database, or might want to create an Access 2000 prototype database by using the Microsoft Data Engine (MSDE), before migrating to SQL 2000.

Access enables multi-user access to the same database by using the file-server architecture (rather than client/server architecture). However, if the small business encounters one of the following situations by using either Access 2000 or an earlier version, upgrading to SQL Server 2000 is recommended:

• The database expands to more than 2 gigabytes (GB).
• The database must support a mission-critical application.
• The application’s usage grows beyond the individual or small group it was intended to support.
• The data must be accessed through the Internet.
• The application requires a more comprehensive security infrastructure.

SQL Server 2000 resolves these problems for the small business owner. It provides scalability, advanced database management, replication, advanced and easy-to-manage security features, and Web page–building wizards to support the small business application. When migrating data to SQL Server 2000, the small business can continue to use Access as the development environment, or the database application can be redeveloped by using Microsoft Visual Studio^®. For more information about Access to SQL Server migrations, refer to Chapter 25, "Migrating Data to SQL Server 2000."

Small Business Database Scenarios

One of the following scenarios might apply to database planning in the small business network. Follow the directives specified for the respective scenario to prepare for implementation of the small business database.

• A new database application will be created by using SQL Server 2000.

For information about setting up a database, refer to the SQL Server Web site for SQL Server 2000 online documentation and various white papers at: http://www.microsoft.com/sql/

• Access 2000 will serve as the new database.

If you are planning to use Access 2000 as your new database in the small business network and future expansion is anticipated, MSDE should be used instead of Microsoft Jet 4.0. This will better accommodate migration to SQL 2000 when the small business has expanded to the point at which it can take advantage of the advanced features of SQL Server. For more information about setting up a database, refer to Access 2000 online documentation.

When you are ready to migrate to SQL Server 2000, the Access 2000 Upsizing Wizard (available in Office 2000) can be used to move Access tables and queries into SQL Server 2000. For Access 2000 migration procedures, refer to Chapter 25, "Migrating Data to SQL Server 2000."

SQL Server 2000 Administration

Whether you have developed a new database application for SQL Server 2000 or you have migrated Access to SQL 2000, all the administrative techniques necessary for a small business implementation are found in the SQL online documentation provided with Small Business Server 2000.

The online SQL documentation describes key counter statistics recorded by predefined performance monitors for SQL 2000. The performance monitors, which gather the data, are discussed along with how to set them up for alert notification when critical operating threshold points are exceeded. This allows the technology consultant to oversee the health and status of the server and to be notified of problematic trends in server usage.

Outlook 2000

Outlook 2000 is a messaging and collaboration client for Small Business Server 2000 users. It supports Internet and Exchange Server e-mail standards, combining them with integrated calendar, contact, and task-management features. The Exchange Server and Outlook 2000 combination is an ideal platform for creating collaborative applications by using your existing messaging infrastructure.

Team Interaction

Collaborative applications facilitate team interaction, enabling individuals and teams to do such things as share information, coordinate projects, and conduct online meetings across the network. To help individuals and teams in the Small Business Server network interact, the following information is discussed in this section:

• Configuring Outlook 2000 with public folders for information sharing
• Publishing to a public folder
• Creating discussion groups
• Testing a discussion group
• Allowing anonymous access to public folders
• Setting up group task and contact lists

Configuring Outlook 2000 with Public Folders

Public folders are configured for accessibility to small work groups or the entire small business network. They can contain any type of information, including e-mail messages and documents. They are well suited to be accessed by discussion groups in the organization or made public on the Internet. Public folders reside on the Exchange Server. However, they can be synchronized to the local hard drive for offline access. To create a public folder, perform the following steps.

To create a public folder in Outlook 2000

1. Click Start, point to Programs, and then click Microsoft Outlook.
2. On the View menu, click Folder List. The Folder List appears.
3. Double-click Public Folders.
4. Right-click All Public Folders, and then click New Folder. The Create New Folder dialog box appears.
5. In the Name field, type a new folder name.
6. In the Folder contains drop-down list, select the type of folder you want.
7. Click OK.
8. When asked to add this folder to the Outlook 2000 bar, click Yes.
9. In the Outlook 2000 Folder List, right-click the newly created folder, and then click Properties. The Folder Properties dialog box appears.
10. On the Administration tab, click Personal Address Book to add the folder to your personal address book, which is usually your Outlook 2000 Contact folder.
11. Click OK.

Publishing to a Public Folder

To publish to a public folder, you can either drag it to the public folder in the Outlook 2000 bar or send an e-mail to the folder, as described in the following steps.

To publish to a public folder by dragging and dropping

1. In Outlook 2000, click Inbox.
2. Select a message, and then drag it onto the Outlook 2000 bar public folder that you created in the previous procedure.
3. In the Outlook 2000 bar or Folder List, click the public folder, and then verify that the message appears there.

---

NOTE:
You can drag any type of item to the public folder, including Word documents.

---

To publish to a public folder by sending an e-mail

1. On the Outlook 2000 Actions menu, click New Mail Message. The Untitled - Message dialog box appears.
2. Compose a message, and then in the Subject box, type a subject for the message.
3. Click To. The Select Names dialog box appears.
4. In the Show names from the drop-down list, select Public Folders.
5. Select the public folder to which you are publishing, and then click To.
6. Click OK.
7. In the Message dialog box, click Send.
8. In the Outlook 2000 bar or Folder List, select the public folder, and then verify that the message appears there.

Creating a Discussion Group

Discussion groups enable users to collaborate and share information. They can also be used to host list servers and knowledge bases for use by coworkers, business partners, and customers. Discussion groups are accessed by using any Internet newsreader, a Web browser, or Outlook 2000.

To create a discussion group, perform the following steps.

To create a discussion group in Outlook 2000

1. Click Start, point to Programs, and then click Microsoft Outlook.
2. On the View menu, click Folder List.
3. On the File menu, point to Folder, and then click New Folder. The Create New Folder dialog box appears.
4. In the Name field, type a name for your discussion group.
5. In the Folder contains drop-down list, select Mail Items.
6. Click OK.
7. When asked to add this folder to the Outlook bar, click Yes.

Testing the Discussion Group

You can test the discussion group you just created by posting messages to the discussion group folder by performing the following steps.

To test the discussion group

1. On the Outlook 2000 View menu, click Folder List.
2. From the Folder List, double-click Public Folders, click All Public Folders, and then select the discussion group folder created in the previous procedure.
3. Click New above the Outlook 2000 bar. The Untitled - Discussion dialog box appears.
4. Create several messages with different subject fields. To do so, on the Actions menu, click New Post in this Folder when you want to open more Untitled - Discussion dialog boxes.
5. In each open Discussion dialog box, click Post, and then observe that postings are automatically filtered by message topic.
6. On the Outlook 2000 View menu, point to Current View, and then select By Conversation Topic to group the postings according to conversation topic.

Allowing Anonymous Access to Public Folders

To be able to open a discussion group to customers of the small business and other users on the Internet, you must allow anonymous access to the public folder. With anonymous access, users do not need a Windows 2000 account on Small Business Server to participate in discussions. To allow anonymous user access to Exchange Server public folders, perform the following steps.

To configure anonymous user access to public folders

1. On the Outlook 2000 View menu, click Folder List.
2. From the Folder List, double-click Public Folders, click All Public Folders, and then right-click the discussion group folder. The Folder Properties dialog box appears.
3. On the Permissions tab, select Anonymous.
4. In the Roles drop-down list, select Author.
5. Click Apply, and then click OK.

Before anonymous users can access a public folder, the Hypertext Transfer Protocol (HTTP) public properties of Exchange Server must be configured with a shortcut to the public folder. To do so, perform the following steps.

To configure public folder shortcuts on the Exchange Server

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the site object, expand Servers, expand the server object, expand Protocols, expand HTTP, and then expand Exchange Virtual Server.
3. Right-click the public folder, and then click Properties.
4. Click the Access tab.
5. Click Authentication.
6. In the Authentication Methods dialog box, select Anonymous access.
7. Click OK, and then quit all open dialog boxes.

To verify anonymous user access to the discussion group folder

1. On the Start menu, point to Programs, and then click Internet Explorer to start the Microsoft Internet Explorer 5.x Web browser.
2. In the Address field, type http://CompanyServerName/Exchange to display the Outlook Web Access page.
3. Click click here to display the Outlook All Public Folders view.
4. Click the public discussion group folder you created with anonymous access.
5. In the Compose New drop-down list, select Posting to this Folder to post a message to the discussion group folder.
6. Click Compose New. The New Post - Microsoft Internet Explorer dialog box appears.
7. In the dialog box, type all appropriate information, and then on the File menu, click Post.
8. Verify that the posted message appears in the Outlook discussion group folder.

Setting Up Group Task Lists and Contact Databases

Public folders can be used to host other shared information such as task and contact lists, thus creating easy ways for users or groups to manage projects or contact databases. Perform the following steps to set up a group task list and a contact database.

To configure Outlook 2000 for a group task list

1. Click Start, point to Programs, and then click Microsoft Outlook.
2. On the View menu, click Folder List. The Outlook Folder List appears.
3. From the Folder List, double-click Public Folders, and then click All Public Folders.
4. On the File menu, point to New, and then click Folder. The Create New Folder dialog box appears.
5. In the Name field, type Group Tasks
6. In the Folder Contains drop-down list, select Task Items.
7. Click OK.
8. When asked to add this folder to the Outlook 2000 bar, click Yes.

To create a group task in Outlook 2000

1. On the Outlook 2000 bar, click Group Tasks. The Outlook 2000 Group Tasks list appears.
2. On the File menu, point to New, and then click Task. The Untitled - Task dialog box appears.
3. In the Untitled - Task dialog box, type all appropriate information, and then in the Subject box, type a task name.
4. Click Save and Close.
5. Verify that the task appears in the Outlook 2000 Group Tasks folder.

To configure Outlook 2000 for a group contact database

1. Click Start, point to Programs, and then click Microsoft Outlook.
2. On the View menu, click Folder List. The Outlook 2000 Folder List appears.
3. From the Folder List, double-click Public Folders, and then click All Public Folders.
4. On the File menu, point to New, and then click Folder. The Create New Folder dialog box appears.
5. In the Name field, type Group Contacts
6. In the Folder Contains drop-down list, select Contact Items.
7. Click OK.
8. When asked to add this folder to the Outlook 2000 bar, click Yes.

To create a group contact in Outlook 2000

1. On the Outlook 2000 bar, click Group Contact to display the Outlook 2000 Group Contacts list.
2. On the File menu, point to New, and then click Contact. The Untitled - Contact dialog box appears.
3. In the Untitled - Contact dialog box, type all appropriate information, including a contact name.
4. Click Save and Close.
5. In the Group Contact list, verify that the new contact appears.

---

NOTE:
If you want to define permissions for the Group Contact list, right-click the Group Contact folder, click Properties, and then click the Permissions tab.

---

Outlook 2000 Team Folders

Outlook 2000 team folders make it easy for any user to create and manage a team collaboration application by using Outlook 2000 and Exchange Server public folders. A team folder combines the ease of use of a Web-style user interface with the powerful collaboration features of Outlook and Exchange Server.

After running a simple setup program to install the Team Folders Wizard in Outlook 2000, the user opens the Outlook File menu, clicks New, and then clicks Team Folder. The wizard guides the user through the steps of building the Team Folder application, including creating an Exchange Server public folder, publishing Web files, and even sending out an announcement to team members. Users can choose from six standard templates or custom templates that they create.

Depending on the type of application installed, the Team Folders application can contain one or all of the following modules:

• Threaded discussion
• Document repository
• Team calendar
• Team task list
• Contacts list

Because the Outlook 2000 Team Folders application was designed with end users in mind, the user who creates the team folder can also administer it by using a simple, wizard-like Web page. The user/administrator can add and remove team members, assign access permissions, and manage messages displayed by the team folder home page. Because it is easy for users to manage their own applications, the network administrator is relieved of having to manage the collaboration applications used by workgroups and teams throughout the organization.

Downloading the Outlook 2000 Team Folder Kit

You can download the Outlook 2000 Team Folder Kit from the Microsoft Web site at: http://www.microsoft.com/outlook/.

The Outlook 2000 Team Folders Kit consists of four components:

• An invitation form and a utility for installing the form in the Organizational Forms Library.
• Microsoft ActiveX^® controls and utility files to allow the controls to be accessed from an organization’s intranet.
• Team Folders Wizard setup.
• Supporting documentation.

Invitation Form

After a user creates a team folder by using one of the Outlook 2000 team folders templates, the user can send a message to team members that tells them about the team folder and provides a button they can click to add a shortcut to the team folder on their Outlook Bar. To prevent users from receiving a warning about macros in the invitation message, the form this message is based on must be published in the Microsoft Exchange Server Organizational Forms Library. The Team Folders Kit includes a personal folders file (Invite.pst) that contains the form and a utility (Vbinvite.exe) that an Exchange Server administrator can run to publish the form automatically.

ActiveX Controls

The folder home pages of the team folders templates use two ActiveX controls: the Microsoft Outlook View Control and the Microsoft Outlook Permissions Control. By default, the folder home pages download these controls from the Microsoft Web site (http://www.microsoft.com/). However, organizations in which users do not have access to the Internet can configure the folder home pages to download the controls from a server on the organization’s LAN. The Team Folders Kit includes .cab files containing the controls and utility files (Codebase.bat and Codebase.ini) that are used to specify the location of the source files.

Team Folders Wizard Setup

Before a team folder can be created, the user must install the Team Folders Wizard and the team folders templates. Team Folders Wizard Setup is a self-contained executable file (Oltfwiz.exe) that a user can run from a network share or receive as an e-mail attachment.

Supporting Documentation

In addition to this guide, the Team Folders Kit contains programmer’s reference files for the View Control (Ovctl.chm) and the Permissions Control (Oltfacl.chm), which is located in the Docs folder. There is also a Readme file in the installation folder, which contains information that developed too late to be included in this guide.

Installing the Team Folders Wizard

After the Team Folders Kit has been downloaded and installed on your computer, you start the Install Team Folders Wizard from the Outlook 2000 Team Folders Kit. From here, you can create a team folder by using Outlook 2000.

You must have Owner permissions to this public folder to be able to install the Team Folders application. You also must create a folder on the server that is shared as a Web folder where you have Full Control permission.

Building Outlook 2000 Team Folders

After the Install Team Folders Wizard is complete, you use Outlook 2000 to create a team folder as follows.

To create a team folder by using Outlook 2000

1. Click Start, point to Programs, and then click Microsoft Outlook.
2. On the File menu, point to New, and then click Team Folder. The Outlook Team Folders Wizard appears.
3. Click Next.
4. Select the type of team folder you want to create, and then click Next.
5. Type a name for the team folder, and then click Next.
6. Click Choose Folder, and then select a public folder in which that the team folder will be located, as shown in Figure 18.10.

Figure 18.10 Selecting the public folder to host (Image unavailable)

7. In the Web page destination box, replace <YourServerName> with the NetBIOS name of your server.
8. Click Next.
9. Select members for the team, set permission levels (see Figure 18.11), and then click Next.

Figure 18.11 Selecting team folder members (Image unavailable)

10. Review the summary information, and then click Finish, as shown in Figure 18.12.

Figure 18.12 Reviewing summary information for team folders (Image unavailable)

11. Click OK when the Ready to administer Team Folder dialog box appears.
12. Click Yes when the Security Warning dialog box appears, warning you that the Microsoft Outlook View Control (consisting of the olTFACL.ocx and oltfacl.inf files) will be installed over the Internet. This is shown in Figure 18.13.

Figure 18.13 Internet security warning about downloading the ActiveX controls (Image unavailable)

After the installation is complete, you are ready to administer and use team folders, as shown in Figure 18.14.

Figure 18.14 Team folders are ready for administration and use  (Image unavailable)

Extending Team Folders

You can extend team folder usage beyond that available in the Team Folders Kit. For more information about extending team folders, refer to the Microsoft Outlook 2000 Team Folders Online Help.

Summary

This chapter discussed several key Small Business Server 2000 components from an administration perspective, including SQL Server, Exchange Server, ISA Server, and Outlook.