SafeCom server minimum requirements
• Windows Server 2016 or 2012 R2.
• Virtualization software, such as VMware and Microsoft Virtual Server, is supported as long as it supports the Operating System.
• 8 GB RAM or more (16 GB is a recommended minimum for larger deployments).
• 20 GB or more disk space to allow for database growth and print job storage (depends on utilization).
• TCP/IP protocol installed and configured.
• The Ethernet Card Reader Service REQUIRES Microsoft .Net Framework 4.6.
• SafeCom license key code.
• Capability for SHA-2 code signing
Network names - Ensure that the computer names in the SafeCom environment are shorter than 16 characters, to avoid connection issues due to NetBIOS limitations.
• Microsoft SQL Express 2014 SP1 is distributed with the software and REQUIRES Microsoft .Net Framework 3.5 SP1 and Windows Installer 4.5. Please visit microsoft.com to download and install these prior to the installation of SafeCom G4.
• In a SafeCom multiserver installation (Multiserver installation) the SQL primary server must run Microsoft SQL Server Microsoft SQL Server 2014 or 2016. It must be licensed and installed (including replication option). Microsoft SQL is quite memory intensive and basically the more memory the better. 8 GB RAM is a good start.
Important When using a standalone SQL Server 2016, ensure that you have the Management Tools– Basic component of the SSMS 2014 installed on the same machine as the SafeCom server before you start installing SafeCom. If SSMS is not installed, replication may not work properly.
Important When using SQL Server 2014, ensure that you have the Management Tools – Basic component of the SSMS installed on the same machine as the SafeCom server. If the SSMS is not installed prior to SafeCom, it requires a restarting of the SafeCom service. If SSMS is not installed, replication may not work properly. The SSMS version must match the version of the external SQLserver to be used.
• Decide on the authentication type before installation, as you will be prompted to choose by the installer. If you select Windows authentication, the account is required already during the installation and must have the “Logon as service” rights. The service account credentials also need to be provided, if necessary.