Best Practice Summary
- Client Access Licenses—Purchase a sufficient number of User CALs to cover all the employees in the organization. Only look at Device CALs in a shift-work environment where employees are sharing terminals.
- Terminal Services—If terminal service access is needed, install and configure a separate terminal server computer on the network. SBS 2003 cannot run Terminal Services in Application mode.
- Network configuration—Build the SBS server with two network cards and use a router/firewall device to connect the SBS server to the public Internet.
- DHCP configuration—Use the DHCP service from the SBS server and disable DHCP services on all other devices on the network (such as the router/firewall). Configure all workstations on the internal network to get a dynamic IP address from the DHCP service on the SBS server.
A highly generalized overview recommendation for the implementation of an SBS installation might look like this:
- Network layout—A hardware router/firewall connects to the ISP for Internet access. An SBS server with two network cards connects the router/firewall and an internal switch. All networked computers, including wireless computers needing normal access to the SBS server, are connected to the switch.
- Server storage—The SBS server has two spindles or partitions for data storage. The C: drive or partition is 12GB–16GB in size. The data drive or partition is as large as necessary to accommodate the organization’s data storage needs.
- Backup storage—If using a tape drive for data backup and the capacity of the tape drive is less than the data size on the server, implement a third-party backup solution or customize a backup schedule using NTBackup (covered in detail in Chapter 18). If using removable disk drives, try to use a FireWire connection to an external disk enclosure with a drive large enough to store all the server data.
These are just guidelines. The actual implementation depends on the needs and restrictions of the installation site.