Enterprise access control for organizations that need scalable security management, browser clients, cloud options and extensive integrations.
Products and selection guidance
OnGuard spans on-premise, Enterprise multi-server and AWS-hosted OnGuard Cloud deployments. A design must define server/cloud ownership, database topology, regional synchronization, operator clients, monitoring, identity/visitor modules, integrations and upgrade/support entitlement.
- OnGuard Access, Enterprise and Cloud architecture
- Browser Monitor, Credentials, Visitor and Surveillance clients
- HR, elevator, video, intrusion and building-system interfaces
- Version compatibility, database backup, hardening and disaster recovery
- Door, lock, free-egress, accessibility and fire-alarm requirements
- Network, power, standby battery and outage behavior
- Current licenses, subscriptions, firmware and integrations
- Administrator training, backup, documentation and maintenance
Site-specific design
Boston High Tech inventories existing equipment and validates current manufacturer compatibility before specifying reuse, migration or replacement. Qualifications may be confirmed privately when needed; license numbers, certificate copies and named certificate-holder details are not published.
Request a manufacturer-specific consultation
Projects are supported from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For LenelS2 OnGuard, OnGuard Cloud and Enterprise, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions about OnGuard deployment choices, operator clients, interfaces and the ownership decisions an enterprise access design has to record.
When would we run OnGuard on our own servers instead of OnGuard Cloud?
It turns on server or cloud ownership, which the design has to state either way. OnGuard spans on-premise, Enterprise multi-server and AWS-hosted OnGuard Cloud deployments, so the deciding questions are who operates the servers, where the database and regional synchronization sit, and which group carries the upgrade and support entitlement. Settle those with your IT group before the architecture is fixed.
Which OnGuard clients does each of our teams need?
Map roles to clients during design. The family lists Browser Monitor, Credentials, Visitor and Surveillance clients, and the design defines operator clients and monitoring along with the identity and visitor modules. A guard station, a badging desk and a lobby reception do not need the same client, so the entitlement should follow that map rather than a headcount.
Can OnGuard take cardholder records from the HR system we already run?
HR is one of the interface categories the family lists, together with elevator, video, intrusion and building-system interfaces, so a feed from HR belongs in the design rather than being added afterward. Whether your specific HR platform is covered depends on the OnGuard version and the integrations in your entitlement, so name the platform and version while the architecture is still open.
We have sites in three regions. How do they stay in step?
Through the Enterprise multi-server design, where database topology and regional synchronization are defined before deployment. Decide which records are held centrally and which regionally, and what a region does while the link to the central database is unavailable. Operator clients and monitoring are then placed to match, so a regional team is not left waiting on a distant server.
Who backs up the OnGuard database and hardens the servers?
Assign that in writing before cutover. Version compatibility, database backup, hardening and disaster recovery sit together as one decision, so name an owner for each part: who applies updates, who verifies that a restore actually works, who keeps the recovery runbook, and who is called when the server does not come back.
Which parts of an OnGuard project are IT work, and which are door work?
Split the schedule early. The IT side covers server or cloud ownership, database topology, operator clients, monitoring and the interfaces to other systems. The field side covers the number and type of controlled openings, controller, reader, lock and credential compatibility, and the door, lock, free-egress, accessibility and fire-alarm requirements at each opening. Both sides meet at commissioning.
LenelS2 owner, administrator and buyer resources
Discuss LenelS2 installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official LenelS2 OnGuard software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.