Note: This article pertains to Mac OS X Server versions 1.x, which were released prior to May 2001.
Some functions of AppleShare IP that are not part of Apple File Services include:
- Duplicate user, import, export
- Batch-change user options
- Log on greetings
- Multi-homing support
- Dynamic server name change (You must restart Apple File Services to change the server's AppleTalk name)
- Setting access privileges on read-only volumes, such as CD-ROM
- Support for HFS or UFS volumes
- Application launch limit support
- DOS short names support
- ProDOS support
- Cannot enable or disable just AFP/TCP or AFP/AppleTalk
- Idle disconnect
- Automatic reassignment of access privileges after a user is deleted
- Web-based administration from OmniWeb browser on Mac OS X Server platform
- Clear text authentication only; no extensible UAM mechanism
- Ejectable media is not shared automatically. When it or its sub-directory is shared explicitly, the access privileges are set to read-only for everyone
- Password related convenience features:
- Password expiration
- Minimum password length
- Disable account after a specific number of failed attempts
- Change ability to allow user to save password for automatic log on
- There is no serial number for Apple FIle Services as there was for AppleShare IP
Cache
Previous versions of AppleShare for the Mac OS 8 used a RAM cache to increase performance. As files were copied from the server, AppleShare would store them in RAM so that the next time the files were copied, the server would be faster finding and transferring it from RAM instead of the disk. Apple File Services does not use this mechanism. Instead, it leverages on the speed of the underlying OS to provide fast file transfers. There is no cache setting to adjust, and the Apple File Services process on the server allocates RAM as it needs it.