Constant Contact Customers: Join our partnership program to save 20-30%. Sign up on our Constant Contact Partnership Portal.

Not a Constant Contact customer? Try it for free. When your trial ends, you'll automatically be enrolled in our partnership program to continue saving.

Page tree

The following sections include recommended system settings for optimal program performance.

First, you can view the HeadMaster System Requirements.

Improving Network and System Performance

You can improve performance by optimizing your network settings, protocols, and workstation configuration. ACS Technologies® recommends the following for optimal performance:

  • Avoid 3-D screen savers, especially on the server, since many screen savers do not release memory when not in use.
  • Let Windows manage your virtual memory.
  • Set power schemes to Never turn off hard disks.
  • Set power schemes to Never for System Standby.
  • Set virus protection programs to scan program files instead of all files.

The following are recommendations for Windows performance:

  • Set the share for the HMaster directory and subdirectories to Full Control. Set the NTFS permissions to Full Control.
  • Use only TCP/IP protocols. You can use DHCP or static IP addresses.
  • Set full duplex connections to work with switches and half duplex connections to work with hubs.
  • Set the paging file to at least 12MB higher than the physical RAM.

Mapping Network Drives

Peer-to-Peer Networks

You can set up your Windows® 2000 and Windows® XP operating systems as peer-to-peer networks. If you choose to use the Windows 2000 or Windows XP servers as workstations, you can map them to the root of the drive where the HMaster directory is located or map directly to the HeadMaster directory. If mapping directly to the HeadMaster folder, make sure that the server’s mapped drive is consistent with others. For example, the server will need to be mapped back to itself.


Windows 2000 Professional and Windows XP have limits of allowed simultaneous inbound connections. See your operating system’s documentation or go to for more information.

Peer-to-peer networks are supported only for very small networks (less than five workstations).

Dedicated Server

You can map to the root of the HMaster directory. For security reasons, you can create a partitioned drive with only the HMaster directory on it.
HeadMaster has been designed to take advantage of the client-server processing capabilities in Windows 2000 and Windows 2003 Server. While HeadMaster can be installed on a file server, we recommend a Microsoft 2000 or Microsoft 2003 server for most network installations of HeadMaster.

Terminal Server can be a solution if you have older workstations or remote workers. With Terminal Server, all of the processing is performed on the server and the workstation requirements are reduced to any computer that can install the Terminal Server client. Please keep in mind that the server requirements for the Terminal Server version are much higher than the regular network version. Because of known conflicts and performance issues, Novell Netware® is not supported.


If you are running HeadMaster in a Terminal Server environment, be sure to run HeadMaster by connecting directly to the database.
Network Hardware.

The following hardware is required:

  • 100 Base T network connection
  • Category 5 or 6 UTP (Unshielded Twisted Pair) network cable

UNC (Universal Naming Convention)

HeadMaster does not support UNC even though Windows 2000 and Windows XP support it. The drive or directory on the server where HeadMaster is installed must be mapped as a logical drive.