Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed version navigation menu

...

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 6.

...

This storage is used for uploading large files. You should allocate no less than 5 GB for the temporary storage folder and locate the folder on the same server where BSNEE services will be installed.

 


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

...

Note
titleNote

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

...


Your networked shared folder should have the following permissions (this example uses Windows Server 2008 R2 as the NAS):

...

Note
titleNote

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

...


If you plan to locate persistent storage on the same server used for BSNEE services, you need to manually set up an additional IIS site. You can do this before or after installation, but we recommend completing this task after installation because the installer will create all required folders. See the Post-Installation steps at the end of this guide for details.

...

  • .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.

...

  • 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 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.

...