Review these considerations before you install Faculty Access for the Web.
□ | Make sure your hardware meets the minimum processing speed and memory requirements. Visit our website at support.blackbaud.com for more information about system requirements. Hardware requirements are subject to change and we update as necessary. |
□ | We recommend a separate web server for Faculty Access for the Web. We support Faculty Access for the Web on Windows Server 2003 with IIS 6.0 or Windows Server 2008 with IIS 7.0. Before you begin the installation process, make sure IIS and SMTP are installed and running. You can set these services to start automatically upon reboot. |
□ | Faculty Access for the Web requires .NET Framework 2.0 SP1. If you do not have .NET Framework 2.0 SP1 already installed, it will be installed for you. |
□ | In Windows Server 2003, ASP.NET is part of the operating system. Make sure both ASP.NET and IIS are installed. You can install these from the Control Panel. Within the World Wide Web Service, make sure you also install Active Server Pages, Server Side Includes, and World Wide Web Service. |
□ | If you use Windows Server 2008, Internet Information Services 7 (IIS7) components are no longer installed by default. You must install IIS7 for use with Faculty Access for the Web. Before you install Faculty Access for the Web, you must install the IIS7 roles. For more information about how to install IIS7, see Knowledgebase Solution BB521642 at www.blackbaud.com/kb/. |
□ | You cannot change the date formats used by Faculty Access for the Web. The program uses the default format for the operating system in that locale. |
□ |
|
□ | Review your school’s LAN/WAN/Internet connectivity and decide on a topology for how to include the Faculty Access for the Web server. For example, if your school does not require teachers to access Faculty Access for the Web from home, you can set access to the Faculty Access for the Web Internet Information Services more securely to intranet traffic only. |
□ | If users will access Faculty Access for the Web from home or outside the school’s intranet, you must plan and implement a secure firewall strategy. We do not accept any responsibility for the unauthorized access of your system. You should use knowledgeable technical staff or consulting services to determine your organization’s security needs. We recommend the use of Secure Sockets Layer (SSL), a robust and secure Internet encryption and authentication method. SSL is a data security method available with IIS. Visit the Verisign website at www.verisign.com for more information about SSL. |
□ | To set up an Internet connection, contact a local Internet Service Provider (ISP). Your ISP can also register your domain name. We do not advise that your ISP hosts Faculty Access for the Web. Faculty Access for the Web is closely integrated with the |
□ | Determine the protocol to use to connect the web server and the database server. We recommend TCP/IP; however, the protocol you use depends on the protocol specified on the |
□ | Set up a permanent connection between the web server and the |
□ | For security reasons, we recommend you install both |
□ | Install a W3C-compliant browser on the web server and each user's workstation. |
□ | A network connection is required for each workstation to access Faculty Access for the Web. |
□ | Faculty Access for the Web requires a mouse to navigate to some fields and screens and should be viewed on monitors with an 1024 x 768 or higher sreen resolution. |
□ | Plan for daily backups of the |
□ | If you use Online Campus Community 3.12 with |