Services for Macintosh Best practices

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Best practices

  • Avoid sharing the root directory of hard drives

    While it is easy to share the root directory of a hard drive, it makes troubleshooting the volume much more difficult. When a volume is not working, you can move it to a new directory and delete the old volume and directory. Once the old volume is moved, you can rename the new volume with the old name. This is extremely fast and easy to do, but it will not work on root volumes.

  • Verify routing

    Verify with your network administrator that your routers are routing AppleTalk if you want communication across the LAN. Also verify, if you will be seeding your network with a computer running Services for Macintosh, all ranges must match for the range. There can be no overlapping between segments and each segment's seed router must contain identical range numbers. Also, it is more efficient for a router to seed an AppleTalk network than it is for a computer running Services for Macintosh.

  • Using POSIX file names

    Do not use POSIX file names in the same directory tree that Macintosh users can access through Macintosh-accessible volumes. The POSIX subsystem is case-sensitive (that is, you can create one file called accounts, one called ACCOUNTS, one called Accounts, and so on.).

  • Do not share the interrupt setting for the LocalTalk card

    The interrupt setting used for the LocalTalk card should not be shared with any other device.