Setup - Part 1: Planning

This article applies to ScreenBeam CMS Enterprise product.

Sections in this document:

Section 1.1: Basic
Section 1.2: Sites
Section 1.3: Administrative Users (Roles)
Section 1.4: Deployment Flow Section 1.5: Compatible ScreenBeam Receivers

Careful and comprehensive planning can help you better deploy Central Management System Enterprise (CMSE) and ScreenBeam receivers.

 

1.1 Basic

To plan CMS Enterprise deployment, follow these guidelines:

• Assign an x86-based Windows device to run the ScreenBeam CMS Enterprise (CMS-E) server.
• Confirm that firewalls allow the required ports for CMS-E (default: 7237, 7238, 5001, 8890), web server access (default: 8888), Service Platform (default: 8889, 6388), and SQL server (default: 1433).
• It is strongly recommended to use a fixed IP address for the CMS server host.
• Select an HTTP server to host firmware and related files for upgrading or customizing ScreenBeam receivers. The server should be commercial grade to support numerous concurrent connections and adequate bandwidth. When possible, schedule firmware upgrades in smaller batches to manage network load.
• Ensure network policies permit TCP traffic on CMS ports across routers, with necessary port forwarding configured.
• Record the CMS server address—typically its IP or fully qualified domain name (FQDN). For installations behind a NAT router, use the WAN IP address mapped to the device. This IP or FQDN is used for provisioning ScreenBeam receivers.
• Plan which configuration settings will apply globally, and which should be set per receiver. Prepare an inventory management strategy to map and track ScreenBeam devices by location.

 

1.2 Sites

ScreenBeam CMS organizes receivers into sites based on location or other criteria, streamlining receiver management for CMS users. The platform supports multiple tiers of site hierarchy, making it easy to mirror your organizational structure. For optimal management, create sites that represent actual locations, then assign both receivers and users to the appropriate sites.

CMS users should plan appropriate naming convention for the sites and define the hierarchy.

Example:

• HQ
  • Building 1
    • Floor 1
    • Lab
  • Building 2
• Seattle Office
  • Building 1

 

 

1.3 Administrative Users (Roles)

CMS Enterprise has several types of user (roles), the users differ in their ability to interact with CMS  Enterprise and their ability to interact with ScreenBeam receivers.

CMS SysAdmin (CMS System administrator)
This account type is an administrator over the CMS Enterprise program and an
administrator over all ScreenBeam receivers. It can create, delete, and modify user
accounts, set up Sites and assign ScreenBeam receivers to them, and assign CMS
Users as ScreenBeam Admins or ScreenBeam Monitors for particular sites.

CMS User - CMS Admin
This account type is an administrator over ScreenBeam receivers assigned to the Site(s)
that the ScreenBeam Admin has access to. A CMS SysAdmin must create a CMS User
account and then assign that account to be a ScreenBeam Admin for one or more Sites.
A CMS User does not have administrator privileges within CMS Enterprise to create or
modify other users.

CMS User - CMS Monitor
This account type is an observer of ScreenBeam receivers assigned to the Site(s)that
the ScreenBeam Monitor has access to. A CMS SysAdmin must create a CMS User
account and then assign that account to be a ScreenBeam Admin for one or more Sites.
A CMS User does not have administrator privileges within CMS Enterprise to create or
modify other users.

Default Administrator (default user)
The default user is Administrator. This is usually the IT person that installs and configures the PC or VM. The Administrator may or may not be the same person that manages the ScreenBeam receivers.

The following table shows the functions that different administrative users can access:

 

 

 

1.4 Deployment Flow

The following is a typical deployment flow:

1. Default Administrator installs CMS.
2. Default Administrator logs in using default username/password: Administrator/Screenbeam.
3. Default Administrator changes default Administrator Password (recommended).
4. Default Administrator creates the CMS SysAdmin user.
5. CMS SysAdmin logs in to https://<CMS-server_IPaddress>:8888.
6. CMS SysAdmin provisions receivers to connect to CMS.
7. CMS SysAdmin goes to Member Management page and adds CMS members, specifying them as CMS Users (SB Admin or SB Monitor) or CMS SysAdmin (for backup).
8. CMS SysAdmin navigates to the Receivers page.
9. CMS SysAdmin adds sites if required.
   Note: When creating sites, SB Admin manages level 1 sites and below.
10. CMS SysAdmin adds ScreenBeam receivers to sites.
11. CMS SysAdmin adds users to sites and specifies their roles.
12. SB Admin and SB Monitor users can login with their credentials and manage their receivers.

Notes:

• If multiple users will be managing the same sites, consider allowing shared logins. This approach enables both the site admin and backup admin to edit tasks and ensures a smooth transition if a site administrator leaves the organization.
• SB Monitor users can see available actions, but cannot make modifications. Any receivers that a user does not have permission to configure appear grayed out.

 

1.5 Compatible ScreenBeam Receivers

The following ScreenBeam receivers are compatible with ScreenBeam CMS Enterprise:

• ScreenBeam 1xxx-Series
• ScreenBeam 960-Series (license required)
• ScreenBeam 750-Series (license required)