Perform the following steps, in order, to configure Faculty Access for the Web (FAWeb) and/or NetClassroom (NC) to access/store Downloadable Documents on a separate server:

On the server that will be hosting the Downloadable Documents:

  1. Create a folder to be used to store the shared class documents and share it on the network.
  2. Assign Modify, Read, and Execute NTFS rights to the folder, created in step 1 above, for a specific domain user account. Remember this domain account and use it in all steps below where a domain account is specified.

On the server where FAWeb and/or NC is installed:

  1. In registry, edit HKEY_LOCAL_MACHINE\SOFTWARE\Blackbaud\FAWeb7\ClassDocsPath to point to the Downloadable Documents shared network location, created in the above steps (Note: a UNC path is preferred).
  2. In Internet Information Systems (IIS), (A) edit the ClassDocuments virtual directory to point to the location specified in the previous step, (B) specify the domain user in the "Connect As" option for the ClassDocuments virtual directory, and (C) change the "Blackbaud Apps (.Net 2.0)" application pool identity from NETWORK SERVICE to the domain user. To do this:
    • IIS 6.0 (Windows Server 2003):
      • Right-Click on the ClassDocuments Virtual Directory, located under Web Sites and choose Properties from the menu that appears.
      • Under the Virtual Directory tab, change the option so that the content comes from A share located on another computer.
      • In the Network directory text box, input the UNC path to the shared Downloadable Documents location on the other server (A).
      • Click the Connect As... button, uncheck the Always use the authenticated use's credentials option, and enter in the domain account credentials (B). Click OK to save the changes.
      • Under Application Pools, right-click on the "Blackbaud Apps (.Net 2.0)" entry and choose Properties from the menu that appears.
      • Under the Identity tab, choose the Configurable option and specify the domain user account (C). Click OK.
    • IIS 7.0 (Windows Server 2008):
      • Click to highlight the ClassDocuments Virtual Directory, located under Sites.
      • In the Acton panel, that appears to the far right of the page, choose Basic Settings...
      • In the Physical path text box, input the UNC path to the shared Downloadable Documents location on the other server (A).
      • Click the Connect As... button, select to use a specific user, and enter in the domain account credentials (B). Click OK to save the changes.
      • Under Application Pools, right-click on the "Blackbaud Apps (.Net 2.0)" entry and choose Advanced Settings from the menu that appears.
      • Under the Process Model heading, click on the Identity entry.
      • Click the eclipses button (...) that appears and select the Custom Account option.
      • Choose Set to enter the domain account credentials. Click OK three times to save all changes.
  3. Add the domain user to the "Log on as a service" policy. To do this:
    • Go to Start, Run, and type in secpol.msc.
    • Under Security Settings, Local Policies, User Rights Assignment, locate the Log on as a service option.
    • Double-click on the entry and click the button to Add User or Group.
    • Enter the domain user name and click OK.
  4. Add the domain user to the IIS local security group. To do this:
    • Windows Server 2003:
      • Right-click on My Computer and choose Manage.
      • Under Server Manger, Configuration, Local Users and Groups, Groups, double-click on the IIS_WPG group.
      • Add the domain user account to the Members list and click OK.
    • Windows Server 2008:
      • Right-click on My Computer and choose Manage.
      • Under Server Manger, Configuration, Local Users and Groups, Groups, double-click on the IIS_IUSRS group.
      • Add the domain user account to the Members list and click OK.
  5. Assign NTFS rights to all locations specified for FAWeb and NetClassroom, replacing NETWORK SERVICE with the domain user account:

Note: A webserver restart may be required in order to apply the Local Security Policy user rights to the system.

Note : Incorrect changes to registry settings can cause serious system problems that may be irreversible without reinstallation of the operating system. You must back up your registry before making any registry changes. We are not responsible for damage resulting from incorrect use of the Registry Editor.