Sections in this document:
Section 2.1: CMS Server
Section 2.1.1: System Requirements
Section 2.1.2: Enable Hyper-V
Section 2.1.3: Install Docker Desktop
Section 2.1.4: Set Up Docker Desktop
Section 2.1.5: Install ScreenBeam CMS Enterprise
Section 2.2: DNS Server and DHCP Server
Section 2.3: HTTP Server
2.1 CMS Server
CMS Enterprise requires deployment in a Docker container. Docker Desktop (Community Edition) 2.1.x.x for Windows is required.
2.1.1 System Requirements
Designate an x86-based Windows device to host the CMS server. The device that hosts the CMS server should meet the following requirements:
- Windows 10 (64-bit) Enterprise build 17763 or higher
- Hyper-V enabled
- 2 Core I5 2 GHz or higher
- 8 GB Memory
- 30 GB available Hard Disk Space
- Internet connection
- Windows Server 2019 build 17763 or higher
- Hyper-V enabled
- 4 Core Xeon 2 GHz or higher
- 16 GB Memory or higher
- 50 GB available Hard Disk Space
- Internet connection
This device is to be configured based on the number of receivers deployed.
Ensure the following ports are opened on the PC hosting ScreenBeam CMS:
- CMS communication port: TCP 7237 (or the port specified during CMS installation), used to communicate with the ScreenBeam receivers.
- Receiver log upload port: TCP 7238 (or the port specified during CMS installation), used for uploading receiver logs to the CMS server.
- Webserver port: TCP 8888, used for web browser access.
Ensure that network policies allow TCP traffic on the CMS ports across the network routers and if necessary port forwarded accordingly.
Note the IP address, hostname or fully qualified domain name belonging to the device hosting CMS server.
2.1.2 Enable Hyper-V
Microsoft Hyper-V is required to run Docker Desktop. Enable this feature on the CMS device by going to Control Panel > Programs and Features > Turn Windows Features on or off, and selecting Hyper-V to enable it.
- Windows 10 (64-bit) Enterprise, Pro, or Windows Server 2019
- 64-bit Processor with Second Level Address Translation (SLAT)
- CPU support for VM Monitor Mode Extension (VT-c on Intel CPUs)
- Minimum of 4 GB memory
The following items will need to be enabled in the system BIOS:
- Virtualization Technology
- Hardware Enforced Data Execution Prevention
To verify hardware compatibility, open PowerShell or a command prompt and type "systeminfo". If all listed Hyper-V requirements have a value of Yes, the device can execute the Hyper-V role. If any item returns No, check the requirements listed above and make adjustments where possible. If systeminfo is run on an existing Hyper-V host, the Hyper-V Requirements section will display the following: “Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.”
2.1.3 Install Docker Desktop
Docker Desktop is required to install and run ScreenBeam CMS Enterprise.
Download and install Docker Desktop version 126.96.36.199. This version of Docker Desktop can be downloaded here Docker Desktop Community 188.8.131.52, or from the direct link here.
A Docker ID may be required to download and run Docker Desktop, as will agreeing to the terms and conditions of use of Docker Desktop as provided by Docker. Once the Docker Desktop Installer is downloaded, initiate Docker Desktop installation and follow the installation wizard to completion.
2.1.4 Set Up Docker Desktop
To run CMS efficiently, Docker Desktop should be configured properly.
To set up Docker Desktop:
- Right-click the Docker Desktop icon in the notification area and select Settings on the pop-up menu to open the Settings window.
- Select Shared Drives on the left pane, and then select the local drives for the containers CMS will use.
- Select Advanced on the left pane, and then set at least 2 CPUs, 4 GB of memory, and 1 GB of swap space for the container, or more per the guidelines above.
2.1.5 Install ScreenBeam CMS Enterprise
To install ScreenBeam CMS Enterprise:
- Ensure Docker Desktop is running and the host device is connected to the Internet.
- Open the ScreenBeam CMS Enterprise installation file folder, navigate to the deployment folder, and run CMSDeployment.exe with Administrator privilege.
- During the installation, the software license agreement appears first. Read the agreement carefully. Enter Y (Yes) to agree, or enter N (No) or Q (quit) abort the installation.
Then, specify the following parameters:
CMS database password This is the password to access the CMS database. Enter N (No) to keep the default one, or enter Y (Yes) and type a new password. CMS database port The default port is 1433. If this port is already in use, enter Y (Yes) and specify a new one. MS SQL Server product key If a Microsoft SQL Server product key is available, enter Y (Yes) and enter the product key. CMS communication port This is port for a receiver to communicate with the CMS server. The default port is 7237. If this port is already in use, enter Y (Yes) and specify a new one. Valid port ranges from 5000 to 65535, provided these ports are not used by other devices on the network. CMS log upload port This is the port for uploading receiver logs to the CMS server. The default port is 7238. If this port is already in use, enter Y (Yes) and specify a new one. Valid port ranges from 5000 to 65535, provided these ports are not used by other devices on the network. WebApp port This is port for accessing the CMS server via a web browser. The default port is 8888. If this port is already in use, enter Y (Yes) and specify a new one. ApacheDS port The default port is 10636. If this port is already in use, enter Y (Yes) and specify a new one.
Ensure that any custom port numbers are noted for future reference.
- After the ports are specified, the remaining installation process is automated. If this is the first time ScreenBeam CMS Enterprise is being installed on the device, it may take some time depending on Internet connection speed.
2.2 DNS Server and DHCP Server
A DNS server, while technically optional, is strongly recommended for discovery of ScreenBeam receivers. DNS Discovery allows all ScreenBeam receivers discovered by the CMS server, requiring very little user interaction once the network is configured properly. Additional details on this method can be found in Section 3.2 Provisioning Receivers Using DNS Discovery Method.
2.3 HTTP Server
An HTTP server should be deployed in parallel with CMS Enterprise to host the firmware files and other miscellaneous files used for upgrading or customizing ScreenBeam Receivers.
The HTTP server should be commercial-grade, capable of handling large number of simultaneous connections and bandwidth as policy and network capabilities shall permit.
Note: While the same CMS host can technically be used to host a web server, this may result in unpredictable CMS and/or HTTP server behavior. Use of a different server is highly recommended to ensure optimal performance.