Skip to main content
pdf?stylesheet=default
Blackboard Help

Complete the Pre-Installation Checklist for Windows in a Load-Balanced Configuration

The installation checklist below and the installation worksheet should be completed before installing Blackboard Learn in a load-balanced configuration. Completing both the checklist and the worksheet prior to installation will help ensure a successful installation.

Blackboard Basics

Review the following list to make sure that Blackboard has provided everything necessary to begin installation.

  • A valid Blackboard Learn license file is accessible from the application servers. To receive a license file, contact your Blackboard Client Representative.
  • The Installer has been downloaded to the application servers. To receive instructions for downloading the Installer, contact your Blackboard Client Representative.
  • The administrator has contact information for Blackboard Technical Support and a login for Behind the Blackboard at https://behind.blackboard.com.

Application Servers Checklist

Review the following list to make sure that each application server is prepared for installation.

  • The machine is connected to the network and powered on.
  • The machine meets the minimum hardware requirements.
  • A supported version of the operating system is installed on the machine.
  • The supported version of the JDK is installed on the machine.
  • The supported version of IIS is installed. If a remote content directory will be used, a domain user has been created and IIS security configured appropriately.
  • The machine is dedicated to Blackboard Learn and has no unnecessary software installed.
  • The administrator has a plan for managing log files.
  • The administrator has a plan for backing up the application file system.
  • The DNS (Domain Name Server) is set to resolve the name of the load balancer. Note that the load balancer name should not contain underscore characters. Some versions of Microsoft Internet Explorer block cookies from machines with an underscore in the name.
  • Blackboard Learn application servers must be part of the Windows domain. An alternate scenario involves the DNS service may be enabled on Blackboard Learn application server with a forward lookup record created for it on the application server.
  • If the database is running on a separate server, the SQL Server Client libraries are installed on the application server.
  • Blackboard Learn connects to the SQL Server instance over TCP/IP. The SQL Server network utility must be used to enable the TCP/IP protocol before installation. Blackboard recommends use of the Named Pipes protocol.
  • Any firewalls are configured to allow access to Blackboard Learn ports. These ports are defined when the Installer is run. It is not possible to use a firewall to redirect to a different port. Blackboard Learn must be available to users on the ports specified during the installation and not served through an alternate port.
  • The server clock is synchronized with the other servers used in Blackboard Learn configuration. If the server clocks are not synchronized, there may be differences between the displayed availability of time-sensitive content and the actual availability of time-sensitive content.
  • The Windows file system is set to NTFS. Blackboard Learn will not work with a FAT32 file system.
  • The Installer can connect to the SMTP server.
  • If using a load balanced environment, the Server Groups and Ports have been configured. This is especially important when upgrading an existing load balanced environment.
  • Windows User Account Control is disabled in a 64-bit environment. For instructions, see http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx.

Database Server Checklist

Review the following list to make sure that the database server is prepared for installation:

  • The machine is connected to the network and powered on.
  • The machine meets the minimum hardware requirements.
  • A supported version of the operating system is installed on the machine.
  • A supported version of SQL Server was installed on the root directory with Mixed Mode Security authentication using a local account.
  • If using a SQL Server failover cluster, the cluster is configured and SQL Server is running properly.
  • The person installing Blackboard Learn knows the SQL Server administrator password and what instance of SQL Server will support Blackboard Learn.
  • The machine is dedicated to Blackboard Learn and has no unnecessary software installed.
  • SQL Server is running. If SQL Server was installed just prior to Blackboard Learn, restart the database machine after installing SQL Server and prior to installing Blackboard Learn.
  • The database administrator has a plan for backing up the database and managing database log files.
  • The file system is set to NTFS. Blackboard Learn will not work with a FAT32 file system.
  • If a database instance other than the default will be used, the instance name includes only alphanumeric characters. Do not use punctuation or other characters, including underscores.
  • Verify that the SQL Server Database job agent can be successfully started up before installing or updating the database. To learn more, see Configure SQL Server Agent Automatic Startup. If the job cannot be run, notify the Database administrator so that it can be fixed before running the Installer.

(Optional) File System Server Checklist

If file system storage will be set up on a separate storage device, review the following list to make sure that the file system server is prepared for installation.

  • The administrator has a plan for backing up the application file system.
  • A directory to store the Blackboard content is configured and shared. Another directory for content managment content (available only if your institution licenses content management) is configured and shared, if desired.
  • The domain user that will run the application services has full access to the shared directories.

(Optional) Collaboration Server Checklist

If the Collaboration server will be set up on a Separate Device, make sure that the Collaboration server uses a different DNS name than that of the application servers.