Using the Web Administrator (<Mac OS X Server name>:311), we were able to add and manage users of Apple Filing Services. Users we added in this interface were not allowed to log into the server console or Macintosh Manager clients, which provides administrators with a handy way to restrict user access. Once users were created, we were able to log in from a client via the chooser. Browsing and copying files to and from the server was no different than on our AppleShare IP 6.1 server.

When mapping out your file system plans for a new Mac OS X Server installation, keep in mind that Apple Filing Services work only on HFS+ (Hierarchical Filing System Plus) volumes, not UFS (Unix Filing System) volumes. So, at the very least, you will need two partitions--UFS for boot and HFS+ for filing services. If you would like to serve your UFS volumes over Apple Filing Services, you will need a third-party package, such as Helios' EtherShare.

Managing the Network of Macs
"The next logical step for managing Macintosh workgroups" is the phrase Apple used to describe Macintosh Manager. Users of At Ease for Workgroups in an AppleShare environment will find Macintosh Manager a similar tool for Mac OS X Server environments. With Macintosh Manager, we were able to force a login to our clients and customize the environment based on user. We also installed the Macintosh Manager client on a non-NetBoot PowerMac 7100 to bring it into the management fold. No matter which machine we logged into, our preferences and environment were preserved.

By default, our NetBoot clients were configured to use Macintosh Manager services. We just needed to add user accounts and dole out privileges through the Macintosh Manager utility before logging in on the Macintosh Manager client. We created an account (Kohlhepp) and a workgroup (Editorial). When we added the Kohlhepp account to the Editorial workgroup, it inherited all the workgroup's rights and restrictions. We then had to modify only the rights to the workgroup to update every member.

Using the Macintosh Manager application, we restricted users' access to the system and files. For example, we configured locked-down network configurations and disabled access to the control panels, such as "Memory." Make sure only necessary files are preserved between logins--browser cache probably isn't all that important.

We spotted this oversight in our Netscape Navigator configuration as our login times quickly grew from 10 seconds to more than a minute. We quickly realized that our Navigator cache (about 7.5 MB and 450 files) was being copied from and to the server every time we logged in and out. We quickly configured Macintosh Manager to discard browser cache files. To speed Web browser performance, you should install a networkwide cache server in this environment.

Web Server/WebObjects
Apache 1.3 ships with Mac OS X Server and is installed automatically. With a click of the mouse in NetworkManager.app and a reboot, our Web server was up and running. (We also could have elected to start Apache manually without a reboot.) Other than the directory structure of Mac OS X Server, administration should be familiar to anyone who has used Apache on other platforms. (For more on WebObjects, probably the most important addition to Apple's Web services, see "WebObjects Toolset Simplifies App Building" on page 112.)

Because the bundled Apache Web server offers nothing new from the standard distribution, we spent very little time working with it. Be aware that security under Apache is enforced only on documents that are stored on a UFS volume. This will make it harder for your Macintosh clients to manage your Web site. We updated our site by FTPing files to and from the server. Alternatively, you could install Helios EtherShare (which serves your UFS data via AFP), or use the HFS+ volume (via Apple Filing Services) for staging and have an automated script copy the data to your document directory on UFS.

Mac OS X Server, $499, Apple Computer, (800) 538-9696, (408) 996-1010. www.apple.com

Send your comments on this article to Robert J. Kohlhepp at rkohlhepp@ nwc.com.