Sage 50 Workstation Setup: What to Get Right the First Time

Choosing the right installation type

Sage 50 workstations generally fall into two categories: a machine that will access shared company data over the network, and a machine that hosts the data itself. Installing the wrong component type, or leaving a workstation set up as a standalone installation when it should be joining a shared multi-user environment, is a common source of access confusion that is easy to avoid by confirming the intended role before installation.

Network path consistency across workstations

• Use the same method, either mapped drive letter or UNC path, consistently across all workstations to simplify troubleshooting
• Avoid drive letters that could conflict with other mapped resources on that user's machine
• Document the exact path used so it can be quickly recreated if the workstation is rebuilt or replaced
• Confirm the path resolves correctly by browsing to it in File Explorer before opening Sage 50 for the first time

Network connection quality for the new workstation

Because Sage 50 is sensitive to network latency, as covered in our Sage 50 network performance guide, a new workstation should be connected by wired Ethernet wherever the office layout allows it. If Wi-Fi is unavoidable, use the strongest available access point and monitor performance closely during the first week of use rather than assuming it will be fine.

Permissions and security setup

1. Confirm the user's Windows account has the correct share and NTFS permission level for the Sage 50 data folder before their first login
2. Apply antivirus exclusions scoped narrowly to the Sage 50 data folder and executable processes, not the entire drive
3. Ensure the workstation's operating system and security patches are current before installing Sage 50
4. Confirm the workstation is enrolled in the firm's standard endpoint protection and monitoring, consistent with the rest of the environment

Testing before the workstation goes into daily use

• Open the company data successfully from the new workstation alongside at least one other active user
• Print a sample invoice or report to confirm printer and template configuration
• Confirm backup software, if run locally, is correctly configured and excluded from conflicting with Sage 50
• Verify the workstation appears correctly in any centralized monitoring or patch management tools used by the firm's IT provider

Planning ahead for growth

Each new workstation added to a Sage 50 environment adds a small amount of load to the file share and the hosting machine. Firms adding several new workstations at once, or growing beyond what a basic file-share setup was designed for, should revisit whether the current hosting approach still fits, a decision that connects directly to the planning covered in our Sage 50 server migration checklist.

Dividing responsibility clearly

Sage is responsible for the installer and application behaviour once correctly installed. The network path, permissions, antivirus configuration, and general workstation health are an IT provider's responsibility, and getting them right at setup avoids the majority of Sage 50 access complaints that come up later. Our supported technologies page outlines the broader standard we set up new workstations to.

Frequently asked questions