Versions Compared

Old Version 5

changes.mady.by.user BrightSign TechDocs

Saved on

compared with

New Version Current

changes.mady.by.user BrightSign TechDocs

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColor#3D3D3D
bgColor#F4F4F4
titleColor#3D3D3D
borderWidth0
titleBGColor#3D3D3D
borderStylesolid

ON THIS PAGE

Table of Contents
indent20px

After installing the required software, you will need to take some preliminary steps before installing BSNEE. Please complete all steps before moving on to the Installation page.

Mail Server

A mail server (STMP) is used to send application notifications such as error logs, new/restored passwords, and user creation notifications. These notifications are sent to end users and administrators. To set up the mail server during installation, you will need to prepare the following parameters:

  • Server Name: e.g. localhost

  • User Name: e.g. mailUser

  • Password

  • FROM Address: e.g. from@mydomain.com

  • Port: 25 (by default)

  • TLS: This is disabled by default.

Note

The User Name and Password may be empty if the mail server supports it.

Base Domain Name

BSNEE requires a Base Domain Name, which will be used to manage the application once it is installed. Four separate strings will be used by different internal services to regulate BSNEE:

  • Website

  • Device Handlers

  • Web Services

  • Web Storage

title
Note

Note

Each service uses its own sub-string to build the complete connection string.

During Step 6 of the installation process, you must enter the Base Domain Name. There are no supported IP addresses, so you must input only the domain name. The other strings will be automatically generated using the domain name.

BSNEE will not function properly until all strings are registered in the DNS, pointed to your BSNEE server IP address, and are resolvable by both server and client. You may do this prior to, or immediately after, installation. The example chart below shows which DNS records you need to register. It uses "mydomain.com" as the BSNEE Base Domain Name and 10.0.0.1 as the IP address for the BSNEE server.

FQDN

Type

Value

mydomain.com.

A

10.0.0.1

www.mydomain.com.

CNAME

mydomain.com.

handlers.mydomain.com.

CNAME

mydomain.com.

api.mydomain.com.

CNAME

mydomain.com.

webstorage.mydomain.com.

CNAME

mydomain.com.

storage.mydomain.com.

CNAME*

mydomain.com.

*If this server already exists, but doesn’t have a corresponding DNS record, use the “A” Type instead of “CNAME”.

The default sub-domain names for “api”, “handlers”, and “storage” can be changed during installation. If you attempt to register the strings after installation, you will receive the following error message upon completing Step completing Step 6.Image Removed

...

Persistent Root and Temporary Storage Folders

BSNEE requires persistent storage and temporary storage. You can select the storage location on your hard drive during Step 5 of the installation process. You can either create new persistent storage and temporary storage folders or configure ones that you already have to match the parameters outlined below. 

...

If you want to configure BSNEE to use persistent storage located on the networked shared folder (NAS), complete the following steps before installing BSNEE:

  1. Configure network sharing for BSNEE persistent storage so that it is accessible for BSNEE services.

  2. Configure HTTP access for BSNEE persistent storage.

title
Note

Note

To learn more about configuring network sharing and HTTP access to your persistent storage folders, please refer to your server/NAS documentation.

...

Security Permissions at the File System Level 

Anchor
security_permissions
security_permissions

  • DOMAIN\INSTALLATION_USER (Full Access): “DOMAIN” refers to a domain that the current server is a member of, and “INSTALLATION_USER” refers to the domain user that you use to install the BSNEE services server.

  • DOMAIN\BSNEE_SERVER(Full Access): This is required for accessing the BSNEE services for file sharing.

  • (optional) AUTHENTICATED USERS (Read): This is required for the IIS site on the shared server.

Security Permissions at the Network Share Level

  • DOMAIN\INSTALLATION_USER (Full Access): "DOMAIN" refers to a domain that the current server is a member of, and "INSTALLATION_USER" refers to the domain user that you use to install the BSNEE services server.

  • DOMAIN\BSNEE_SERVER (Full Access): "BSNEE_SERVER" refers to the computer object in domain. This is required for accessing the BSNEE servers for file sharing.

Note
title

Note

Note that the DOMAIN\INSTALLATION_USER permissions are only temporary requirements for installation, and can be removed after the installation process is completed.

...

We recommend you do the following during installation:

  1. Install BSNEE as a domain user with administrative permissions.

  2. Use the “sysadmin” role for MS SQL Server login if you are using Windows authentication for MS SQL Server during installation.

  3. Run BSNEE application pools as the Network Service system user.

MIME Types for IIS 
Anchor
mime_types_for_iis
mime_types_for_iis

When IIS is used as a content server, only registered file formats can pass from the BSNEE Persistent Storage site to the web. By default, the IIS web server may not recognize certain media formats. You may also wish to use some custom extensions. Make sure to register the following special MIME types (in addition to any other desired MIME types) with the persistent storage web server.

Note
title

Note

Make sure to register special MIME types with the storage web site only. Registering MIME types with other BSNEE sites on the same server (or on the server level itself) may cause conflicts.

  • .bpf – text/plain

  • .bsfw – application/x-file

  • .bsp – text/plain

  • .brs – text/plain

  • .vob – video/mpeg

  • .rok – application/octet-stream

  • .flac – audio/flac

  • .bvw – text/plain

  • .mkv – video/x-matroska

  • .woff2 - font/woff2 

These additional MIME types are required for Windows Server 2008 / 2008 R2 (IIS 7 or 7.5):

  • .mp4 – video/mpeg

  • .ts – video/mpeg

  • .m2ts – video/mpeg

  • .ogg – audio/ogg

  • .woff – font/x-woff

  • .svg – image/svg+xml

Once all MIME types are registered and all other preliminary steps are complete, you’re ready to install BSNEE.

Active Directory

Warning
title

Important

Complete this step only if you plan to integrate BSNEE with your LDAP system.

...

  • {NetworkName}=admin, {RoleName}=System Administrators: This group corresponds to the System Administrator Role on the “admin” Network in BSNEE. 

Tip

...

Example

BSNEE-admin-System Administrators 

  • {NetworkName}=admin, {RoleName}=Order Administrators: This group corresponds to the Order Administrator Role on the “admin” Network in BSNEE. 

Tip

...

Example

BSNEE-admin-Order Administrators

BSNEE has two sets of predefined system Roles:

  • Administrative Roles (on 'admin' Network):

    • System Administrators

    • Order Administrators

  • User Roles:

    • Administrators

    • General Managers

    • Network Managers

    • Creators

    • Publishers

    • Viewers

To add more users to BSNEE, you will need to create at least one additional BSNEE Network (being logged into BSNEE as a member of the “admin” Network) and one security group in the Active Directory for Administrators Role. One BSNEE Network can then be used for multiple BSNEE users assigned to different BSNEE Roles on that Network.

BSNEE will automatically import Active Directory users to the BSNEE database when those users first login, and it will continue updating user profiles with changes as they occur on the LDAP server.

Additional Information

  • BSNEE does not support nested security groups.

  • A single Active Directory user can be a member of only one Role on one Network, but a person on BSNEE may have different Roles on different Networks.