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 CMSE deployment, follow these guidelines:

• Designate an x86-based Windows device to host the ScreenBeam CMS (SCMS) server.
 
• Ensure that no firewall is blocking the SCMS ports (default: 7237 / 7238 / 5001 / 8890), the web server access port (default: 8888), the Service Platform ports (default: 8889 / 6388) or the SQL server port (default: 1433).
 
• It is highly recommended that the device hosting the ScreenBeam CMS server has a fixed IP address.
 
• Designate an HTTP server to host the firmware and miscellaneous files, used for upgrading or customizing ScreenBeam Receivers. The server should be commercial caliber, capable of handling large number of simultaneous connections and bandwidth, although scheduling smaller groups of receivers to upgrade firmware can mitigate the impact.
 
• Ensure that the policies allow TCP traffic on the CMS ports across the network routers and if necessary port forwarded accordingly.
 
• Note the ScreenBeam CMS server address. This is generally the IP address (or FQDN) of the CMS server. If the PC is behind a NATed router, then the SCMS IP Address is the WAN IP address to which the PC is mapped to. Use this IP (or FQDN) to provision ScreenBeam receivers.
 
• Determine which parameters must be globally changed and which need to be modified on individual receivers. Tracking inventory of ScreenBeams and mapping them to their locations (sites) should be planned in advance.

1.2 Sites

ScreenBeam CMS uses sites to group receivers according to their locations or other criteria which helps CMS users manage receivers efficiently. ScreenBeam CMS users can manage multiple hierarchical levels of sites. It is recommended to create sites that correspond to actual locations. Assign receivers to sites, and then assign users to sites to manage the receivers.

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, it is recommended though not required, to allow those users to share the same login to allow the site admin and backup site admin to edit each other's tasks (which is tied to user), and for one administrator to take over from another that leaves the organization.
• Actions are displayed for SB Monitor users even though SB Monitor users cannot make modifications. Receivers that a user cannot configure are grayed out.

1.5 Compatible ScreenBeam Receivers

The following ScreenBeam receivers are compatible with ScreenBeam CMS Enterprise:

• ScreenBeam 1100
• ScreenBeam 1000 EDU
• ScreenBeam 1100P
• ScreenBeam 960B (license required)
• ScreenBeam 960A (license required)
• ScreenBeam 950A (license required)
• ScreenBeam 750A (license required)