Skip to main content
Matrix42 Self-Service Help Center

Silversync Guide I: System Requirements

Silversync Server

Hardware 

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

Operating System

  • Windows Server 2008 R2,  2012 R2 or 2016
    • Windows Server 2008 R2 is supported until 09/2019
    • Windows Server 2019 is under review
  • 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 US English language, date and time settings (How-To) 
  • Enabled TLS 1.1 and TLS 1.2 (How-To

For both  How-To's you need to be logged in

Roles and Features

Silversync requires the following Roles and Features:

  Windows Server 2016 Windows Server 2012 R2 Windows Server 2008 R2
Server Roles
  • Web Server (IIS)
  • Web Server (IIS)
  • Web Server (IIS)
Features
  • .NET Framework 3.5 Features
    • NET Framework 3.5 (includes .Net 2.0 and 3.0)
  • .NET Framework 4.6
    • ASP.NET 4.6
  • .NET Framework 3.5 Features
    • NET Framework 3.5 (includes .Net 2.0 and 3.0)
  • .NET Framework 4.5 Features
    • .Net Framework 4.5
    • ASP.NET 4.5 
  • .NET Framework 3.5.1 Features
    • .NET Framework 3.5.1
  • .NET Framework 4.5.2 (Download)

Web Server Role (IIS)

Role Services

  • Web Server
    • Common HTTP Features
      • Default Document
      • Directory Browsing
      • HTTP Errors
      • Static Content
      • HTTP Redirection
    • Health and Diagnostics
      • HTTP Logging
    • Performance
      • Static Content Compression
    • Security
      • Request Filtering
    • Application Development
      • .NET Extensibility 3.5
      • .NET Extensibility 4.6
      • ASP.NET 4.6
      • ISAPI Extensions
      • ISAPI Filters
      • WebSocket Protocol
    • Management Tools
      • IIS Management Console
  • Web Server
    • Common HTTP Features
      • Default Document
      • Directory Browsing
      • HTTP Errors
      • Static Content
      • HTTP Redirection
    • Health and Diagnostics
      • HTTP Logging
    • Performance
      • Static Content Compression
    • Security
      • Request Filtering
    • Application Development
      • .NET Extensibility 3.5
      • .NET Extensibility 4.5
      • ASP.NET 3.5
      • ASP.NET 4.5
      • ISAPI Extensions
      • ISAPI FIlters
      • WebSocket Protocol
    • Management Tools
      • IIS Management Console
  • Web Server 
    • Common HTTP Features
      • Static Content
      • Default Document
      • Directory Browsing
      • HTTP Errors
      • HTTP Redirection
    • Application Development
      • ASP.NET 
      • .NET Extensibility
      • ISAPI Extensions
      • ISAPI FIlters
    • Health and Diagnostics
      • HTTP Logging
    • Security
      • Request Filtering
    • Performance
      • Static Content Compression
    • Management Tools
      • IIS Management Console

Browsers

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

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

Account Requirements

  • In a Domain Environment: To install Silversync, a domain account that is a member of the Local Administrators group is needed.
  • In a Workgroup Environment: To install Silversync, a local administrator account is needed.

File access methods

Silverback has two methods of access files for users. These are called Server Authenticates and User Authenticates. Depending on your decision the Silversync configuration will be split into different ways. So before you start to install Silversync, make the decision what you want to apply. 

Server Authenticates

Server Authenticates is the functionality that the legacy Silversync system used. This means that the Silversync computer object needs permissions on all files users will synchronize. Access to the files is governed by assigned Tags. 

Using this method, the server will access the content for the user. This requires that the Server has READ permissions to the file locations.

Server authenticates operates complete in Read Only mode. Administrators can provide content in folders and users are able to upload files via Personal File Management console. Consuming on end user devices will be in read only mode. 

User Authenticates

User Based authentication means that the individual user’s file permissions are used. This means that a user must be granted minimum read permissions on files and folders before they will be able to sync it.

Administrators can assign content to users and users can upload files to accessible folders and shares. Any content where the user does not have proper NTFS permissions will not be listed or blocked from uploading

Files can be accessed with Read/Write permissions. Administrators can provide content in folders and users are able to upload files via Personal File Management console and M42Mobile application

Firewall Rules

Traffic source (from) Destination (to) Port Protocol
Devices (Internet) Reverse Proxy 443/tcp
Reverse Proxy Silversync  Server 443/tcp
Admin Workstation Silversync Server 3389/tcp
Silversync Server Domain Controller 389,636/tcp
Silversync Server Silverback Server 443/tcp
Devices (Wi-Fi) Silversync Server 443/tcp

DNS

The Silversync server needs to be accessed from the Internet and the internal network; therefore, you need to create DNS entries in your respective DNS servers (where imagoverum.com is equal to the external company domain name).

  • The external DNS name for Silversync is silversync.imagoverum.com
  • The internal DNS name for Silversync is silversync.imagoverum.com

An authoritative DNS aliases needs to be created for silversync.imagoverum.com and it must resolve to IP the external interface of the Reverse Proxy or DMZ Proxy. An internal DNS aliases needs to be created for silversync.imagoverum.com and it must resolve to the Silversync server interface.

SSL

The Silversync solution allows users to securely synchronize content to their devices and requires an established trust relationship between the device and server. The Silversync web service requires one certificate signed by a Certificate Authority trusted by the devices. The certificate must also match the DNS Name outlined in previous section

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

The Silversync Website Certificate is a core requirement for Silversync to function, so please have the PFX/P12 Certificate Bundle available during installation.

  • Was this article helpful?