Installation Guide I: System Requirements

Hardware 

• 64 Bit CPU, 2.6 GHz Xeon or faster
• 8GB RAM
• 10GB of free disk space
• SCSI or SAS speed disks or equivalent SAS
• 1GB Network Interface Cards

Operating System

• Microsoft Windows Server 2016, 2019, or 2022
• The server must exist in the same LAN as the SQL Server. 10ms latency minimum is required to the SQL Server
• The same date and time as the Silverback SQL Database Server
• The server must be configured for English (United States) language, date and time settings (How-To) 
• Executed Hardening Script for enabling and disabling appropriate for Protocols & Cipher

Roles and Features

Silverback requires the following Roles and Features:

Additional Software

• Minimum installed Microsoft .NET Framework Runtime Version 4.7.2

• Minimum installed ASP.NET Core Runtime Hosting Bundle Version 6.0.15

Browsers

Access to Silverback for End Users, Help Desk and System Administrators is via a web-based console. Supported browsers are:

• Google Chrome (recommended)
• Mozilla Firefox
• Safari
• Microsoft Edge
• Internet Explorer 11

To provision a device, users must have access to the Silverback Self Service Portal. If a web proxy processes the user’s web traffic, then ensure the proxy server can serve the Self Service Portal. If this is not possible, proxy server exclusions must be set to allow direct access to the site.

Accounts

The following accounts are needed:

Groups 

The following groups are required. The Silverback Mobile Device Manager groups contains either the Active Directory Computer Object of the Silverback or Cloud Connector Server. The second Silverback Enterprise Device Management group contains the group Silverback Mobile Device Manager and consequently also the computer object of the Silverback or Cloud Connector server.

Hardware

10GB of space per 1000 devices – This will change depending on individual requirements for logging and data retention.

Software

• SQL Server 2012 to 2022 or Azure SQL

• Database Compatibility Level must be 100 for SQL Server 2012 to 2022 and for Azure SQL 150
  • This is set by the script on the Silverback database automatically
• Server/Instance collation must be either
  • Windows Collation or
    • Latin_General_CI_AS
    • Latin1_General_CI_AS
  • SQL Collation
    • SQL_Latin_General_CP1_CI_AS
    • SQL_Latin1_General_CP1_CI_AS
• Database Collation must be set to:
  • Latin1_General_CI_AS
  • This is set by the script on the Silverback database automatically

SQL Account Permissions

Please review all SQL Account Permissions for On-Premise SQL and Azure SQL below:

Database

Silverback will create and configure its database during the Installation.

The following values can be specified.

• Use Azure SQL
• Data Server Address
• Failover Database Server Address
• Database Name
• Authentication Method 
• Username
• Password

Bandwidth

We recommend at least 100Mbps network connections, with latency under 10ms between all internal systems

Domain and Forest Level

• Silverback support the following Domain and Forest Level:
  • Windows Server 2003
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016

DNS

As Silverback requires devices to connect via DNS, appropriate DNS entries must be setup for your server.

SSL

Silverback utilizes device management protocols that require an established trust relationship between the device and server. This allows the server to provision and manage your mobile fleet securely. The Silverback web service requires a certificate signed by a Certificate Authority trusted by the devices. The certificate must also match the DNS Name outlined in Section DNS Setup. The Silverback Website Certificate is a core requirement for Silverback to function, please have the PFX/P12 Certificate Bundle available for the installation.

A full list of iOS trusted Certificate Authorities is available at: http://support.apple.com/kb/HT5012.

Web Proxy

Silverback is web based. Take it into consideration if there are any corporate web proxies in your network. If your end users are using a web proxy to browse the internet, then an appropriate configuration is needed to allow Silverback to function effectively:

• Ensure that each web browser (that has a proxy set) has an exclusion set for the Silverback server URL outlined in section DNS Setup.
• Configure each web proxy to allow traffic destined for the Silverback server to reach its destination unaltered.
• Ensure that any devices connected to Wi-Fi have access to the Apple push network, as outlined in Firewall Rules.
• Ensure that any Android devices enrolled in Silverback are able to access FCM, as outlined in Firewall Rules.

Reverse Proxy

If you are utilizing a reverse proxy, it is important to pass through the Client Request Headers, so that the backend can process the client. Additionally you need to ensure that the certificate chain is completed and fully trusted. As an example on the Sophos UTM Web Application it is required to enable the control "Pass host header" under the advanced configuration and to upload each trusted certificate from the trusted certificate chain in a *.pem format to the Certificate Authority section. If you are using the Microsoft Web Application Proxy publish a new Web Application with a Pass-through configuration.  

SMTP

Silverback will notify administrators about key events in the system if configured to do so. The SMTP Server details are required for alerts. The SMTP Server must allow anonymous relay within the company domain.

Active Sync

Silverback is used to manage deployment of Exchange ActiveSync client configurations. Ensure your Exchange ActiveSync is currently configured and in a working state.