If you've worked in the reseller channel, you know how painful growing and upgrading technology in a small business environment can be. In "Introducing Microsoft BackOffice Small Business Server" (December 1997), I evaluated Small Business Server (SBS), Beta 2 in the Windows NT Magazine Lab. As part of that review, I installed and configured an SBS system with seven client workstations to simulate Dr. John's Health Services, a typical small business environment. This month, I'll revisit some of those tasks with the release candidate (RC) version of SBS, and I'll examine the application services, Internet connectivity, and remote administration options that SBS offers.
To refresh your memory, Microsoft designed SBS to let someone with intermediate computer skills configure a business network environment that supports as many as 25 client connections. Microsoft targets the product for small businesses with fewer than 100 employees and no full-time MIS technician. Small companies can implement file sharing, printer sharing, modem sharing, fax serving, email, database applications, and secure Internet connectivity with one integrated, easy-to-use package.
A Little Background
In part 1 of my review, I ran some trials to get a feel for how the product compared with what Microsoft promised. However, based on what I saw in SBS, Beta 2, Microsoft had some work to do to smooth SBS's rough edges. I encountered problems with installation, including an error message stating that SBS could not locate enough space on a 4GB SCSI disk during setup. I also encountered unreasonably long response times for sending and receiving email, and network traffic slowed considerably with only three connections to the server from client workstations. Finally, the SBS system consistently crashed while trying to generate reports with the Crystal Reports component.
After the Microsoft SBS team reviewed my problems, I received the release candidate (RC) for SBS. The Microsoft team briefed me and gave me some strict warnings: SBS requires NTFS formatting to operate correctly; do not apply NT Service Pack (SP) 3 (SBS already incorporates it); do not uninstall Internet Explorer (IE) from the server; IE 4.0 is not compatible with SBS. Armed with the latest version of SBS and Microsoft's advice, I started my tests.
Basic Setup and Operation
I wanted to give this RC a fair shake, so I checked out a new server for my tests. I chose a Compaq Professional Workstation 5000 configured with dual 200MHz Pentium Pros, 128MB of RAM, a 4.3GB Fast/Wide SCSI-2 hard disk, an 8X CD-ROM, and the Gloria-L 3D Graphics Controller. (For details on the Professional Workstation 5000, see Lab Reports: "Professional Workstation 5000," July 1997.) The network adapter card was a Compaq Integrated Netelligent 10/100 TX PCI, and the modem was a U.S. Robotics Courier v.Everthing external; both products appear on Microsoft's SBS Hardware Compatibility List (HCL).
For connecting to client systems, I used two trustworthy Cogent S-1200 TX 100Base-TX Class II repeaters. The client machines consisted of six Compaq Deskpro 5100 workstations, three HP Vectra LV Series 4 workstations, one Dell OptiPlex GXMT 5166, and one DTK Computer workstation. All clients have at least a 100MHz Pentium and 32MB of RAM.
With the RC, installation went much more smoothly than with SBS, Beta 2. I called the domain CLINIC and my server HOPE. The only problem I encountered during installation was a warning that Proxy Server 1.0 had not been successfully installed. I corrected this problem by selecting the reinstall component option from the SBS CD-ROM. Once installation was complete, I began configuring my fictitious company, Dr. John's Health Services. The interface for adding user accounts was flawless and smooth, and I created shared folders for Patient Records, Finance, Insurance, Billing, and Payroll without a hitch. The interface is simple, and I liked being able to individually assign access to shared folders, shared modems, and the Internet, instead of having to assign membership in global groups for permissions and rights. For example, I allowed only three users to open the Payroll shared folder; all other users received an Access Denied warning.
I added workstations to the domain through the Set Up a Computer Wizard, which creates a user setup floppy to configure a user's account and connection from a client computer. The setup floppy configures Outlook 97 with the user's email account, places shortcuts on the desktop for the user's personal folder and company shared folders, and installs SBS client applications. You can also use this wizard to add another user to a computer already set up for SBS. Several users can use the same client computer, though not at the same time. The process worked much faster this time than the 20 minutes I experienced when I set up clients with SBS, Beta 2. During a 9-minute period, I simultaneously configured four workstations with no visible slowdown in network traffic.
After I configured a client system, I immediately opened Outlook 97 to evaluate Exchange and the mail services. I was able to get all 11 clients to access their mailboxes and begin sending interoffice mail.
Screen 1 displays a user's default address book that I created during the installation. The network performed admirably, sending and receiving mail instantaneously—including attachments of images, text, and binary code. The network slowdown prevalent with the beta code was not visible with the RC. The only problem I encountered was that some of the shortcuts SBS placed on the user's desktop did not point to the user's individual folder on the server. Deleting the shortcut and creating a new one solved this problem.
After I established the first five connections with server HOPE, SBS prompted me to add client licenses. SBS defaults to five connections during installation. Microsoft supplies additional licenses in sets of 5 (up to a maximum of 25) on floppies. Adding 10 extra licenses was extremely easy. Each client received a warning message that stated the server would be down and directed users to close all connections to HOPE. You must restart the server after adding licenses.
For this portion of my evaluation checklist, I was pleased with the performance of SBS. I went from a cold start through installation, configuration, sharing resources, and using an 11-client network with email in less than 3 hours.
Applications Support
For evaluating applications support, I installed Microsoft Office 97 with the SR-1 Patch into a shared folder on the server. Each user was able to open the shared applications folder and start a session of Word or Excel. From each client workstation, I created shortcuts for these applications on the user's desktop. I placed sample data into the Patient Records, Finance, Insurance, Billing, and Payroll shared folders. Using Word or Excel, each user accessed the sample data and performed read and write operations if the privilege was set in the user profile. If a user did not have certain privileges with a folder or file, the computer answered with the Access Denied warning.
Operations were flawless, and I was able to copy and paste data into email messages and forward the messages to other users. Network traffic held up fine—email exchanged instantaneously, and I downloaded and saved sample data with no noticeable slowdown on the server or the client workstations. One comment I'll make as an evaluator is that because of the audience SBS is intended for, Microsoft needs to include the applications support in the user setup floppy. SBS would benefit from the functionality in Microsoft Systems Management Server (SMS) that lets you push applications (such as Word, Excel, or third-party programs) to the clients. Setup would be much easier for end-users if applications and selected shortcuts to shared folders downloaded to the client systems, in addition to the SBS client software and shortcuts that SBS installs during setup.
Connecting to the Internet
The next step for Dr. John's Health Services was to connect to the Internet. Because the domain was functioning fine and SBS was performing well, I proceeded to sign up with an Internet Service Provider (ISP). Selecting this option from the To Do List (SBS's friendly user interface for configuration and maintenance operations, shown in Screen 2, page 74) automatically launches the Internet Connection Wizard, which locates an ISP, configures Exchange to work over the Internet, and registers a company over the Internet. I was prompted for my area code and the first three digits of Dr. John's Health Services' phone number.
To further refine the Internet connection process, Microsoft includes an Internet Referral Service. The RC lists two companies: Verio Small Business Services and SPRYNET. Both companies provide special offers for the BackOffice SBS beta sites. Microsoft expects to have additional ISPs by the product release date.
Through SBS, I selected Verio as my ISP, and the computer automatically dialed the toll-free number to begin the sign-up process. The registration information required for Dr. John's Health Services included my full name; the organization name, address, and phone number; and my password, domain name, and billing option.
During the registration process, the ISP passed its account and dialing properties to server HOPE. Next, the ISP configured the mail server to receive and hold mail for Dr. John's Health Services. The email protocol used on the Internet, Simple Network Management Protocol (SNMP), expects a persistent connection; the ISP cannot hold a small business's email. Microsoft created an ISP Kit based on ETRN (an Internet standard Request for Comments 1985) to let ISPs configure their site to support the ability to hold mail. Exchange Server will automatically default to establishing a connection with the ISP every hour to check for email. This way, a small business doesn't need a dedicated phone line constantly connected to an ISP. The server will also automatically dial out to the ISP when a client activates IE and a connection does not already exist. SBS presents clients with the SBS Home Page shown in Screen 3, a single interface for communications options.
Previous
Register
