> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/reference/minimum-specifications.md). # Minimum Specifications This topic provides an overview of Computer Specifications that meet the normal requirements of Small, Medium and Large Systems to run Gallagher Security Enterprise software The final system together with its network infrastructure will be managed by the Customers IT department in liaison with their authorized Gallagher Channel Partner. Gallagher offer further information and utilities to support this process including: * Hardening Guide * Security Health Check * Details of supported operating systems, databases, and relevant service pack. Refer to the relevant version of the Gallagher Command Centre release note. * Additional information on this site, including software backups to be stored on separate machines. Refer to [Archiving and Backups](/knowledge-hub/products/cc-software/configure/archiving-and-backups.md) ### Server Specifications #### **Small configuration for up to 3 Operator Workstations and 20 Gallagher Controllers**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) ![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)Processor: 8 core 8 threads * Memory: 8 GB RAM min * Graphics Card: Standard * Hard Drive: 500GB * USB Ports: 3 or more (for printer, camera, encoder, dongles) * Network: 1 Gbps * Operating System: See Command Centre Installation and Upgrade Release notes for the supported operating systems. * Database: Microsoft® SQL Express (see release notes for supported versions) * Photo ID Camera: Direct show supported camera * Note: Unnecessary preloaded software (bloatware) may be present in workstations that run a non-server OS; we recommend removing unneeded bloatware in this instance. #### **Medium configuration for up to 10 Workstations and 50 Controllers**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) ![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)Processor: 8 core, 16 threads * Memory: 16 GB RAM * Graphics Card: Standard * Hard Drive: NVMe SSD, 1 TB * USB Ports: 3 or more (for printer, encoder, dongles) * Network: 1 Gbps * Operating System: See Command Centre Installation and Upgrade Release notes for the supported operating systems. * Database: Microsoft® SQL Standard (see release notes for supported versions) #### **Large configuration for up to 30 Workstations and 150 Controllers**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) ![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)Processor: 12 core, 24 thread * Memory: 32GB RAM * Graphics Card: Standard * Hard Drive: 2 x NVMe SSD, 1 TB (The quantity of 2 allows for RAID redundancy mirroring). * USB Ports: 3 or more (for printer, encoder, dongles) * Network: 1 Gbps * Operating System: Server level Operating Systems are recommended for large configurations. See Command Centre Installation and Upgrade Release notes for the supported operating systems. * Database: Microsoft® SQL Standard or Enterprise (see release notes for supported versions) #### **Extra large configuration**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) Please contact your local Gallagher representative. Support for server specifications for extra large site servers varies depending on the size and amount of activity on the site. Here is a page on a bespoke server specification guide - [LINK](/knowledge-hub/products/cc-software/reference/server-bespoke-minimum-specification.md) ### **Workstation Specifications** #### **Operator Workstation** The below specification is based on typical functions performed by operators e.g. cardholder management, alarm management, basic reporting. For any functions such as video monitoring and large reporting, more resources may be needed. Processor: 8 Core, 8 Thread * Memory: 8 GB RAM min * Graphics Card: Standard * Hard Drive: 250GB * USB Ports: 3 or more (for printer, camera, encoder if needed) * Network: 1 Gbps * Operating System: See release notes for the supported operating systems Optional For minimum display resolution, it is recommended to use a monitor with at least 1080p. Using a monitor that is lower than the recommended could cause areas of the Command Centre application to be hidden from view. #### **Visitor Management**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) ![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)Processor: 8 Core, 8 Thread * Memory: 8 GB RAM min * Graphics Card: Standard * Hard Drive: 250GB * USB Ports: 3 or more (for printer, camera, encoder if needed) * Network: 1 Gbps * Operating System: See release notes for the supported operating systems Optional * Photo ID Camera: Direct show supported camera * Touch-screen: Touch screen must support Windows® multi-touch gestures #### **Gallagher Visitor Management Kiosk**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) ![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) * Processor: 8 Core, 8 Thread * Memory: 8GB RAM min * Graphics Card: Standard * Touch-screen: Touch screen must support Windows® multi-touch gestures * Hard Drive: 80 GB * USB Ports: 3 or more (for printer, camera, business card scanner if needed) * Network: 1 Gbps * Supported Camera: Direct show supported camera * Operating System: See release notes for the supported operating systems **Note:** The printer (used for printing visitor labels at the kiosk), business card scanner (for speeding up visitor data entry at the kiosk) and the web camera (for capturing visitor photos at the kiosk) are all optional features. The kiosk can run without these. ### **Virtual Servers running Command Centre**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif) Gallagher Command Centre software stores information in Microsoft® SQL databases on the same Server or separate SQL Server. The Specifications below assume the SQL database is on the same Server as Command Centre. There can be good reasons for running larger sites on multiple Servers. Command Centre software sees no difference between a physical Server and a virtual Server. Gallagher do however require the following: * Resources be dedicated to the virtual server running the Gallagher Command Centre * Resources such as RAM and HDD etc NOT be dynamic * The virtual Server management system does not run snapshots of the virtual computer running the Gallagher Command Centre software * Due to virtual Server environment configuration variability, if initial fault resolution is inconclusive, Gallagher reserves the right to request customer replication of any errors in a non-virtual environment. The Customer and their Channel Partner have the flexibility to add performance, security and resilience criteria to these Specifications. Should you require further information please contact your local Gallagher representative. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/reference/minimum-specifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.