Help Center>Foundation Help

Applies to:

Installing Foundation User Governance in a load-balanced, high-availability environment

Foundation User Governance 11.x installation

The following information applies if you are installing Winshuttle Foundation User Governance on multiple machines in a network load-balanced (NLB), high-availability (HA) environment.

On this page

To do this you will need to install Winshuttle Foundation User Governance on multiple machines.

However, if Winshuttle Foundation User Governance is installed on multiple machines in a load-balanced network, then certain features (such as session state management) will not work if the request is redirected to different machines where User Governance is installed.

For this to work, you must make certain changes (described below) because the Winshuttle Foundation load balancing is not handled by the Sharepoint Farm.

Installing Winshuttle Foundation User Governance in an NLB/HA environment (overview)

Back to top
  1. Make sure the SQL Server Agent service is running.
  2. Install Winshuttle Foundation User Governance on multiple IIS servers. Note:
    • During installation, do not create a new database for each server.
    • While creating site using the installer, be sure to provide same folder structure path for each web front end.
  3. On the Foundation User Governance database configuration screen, click Uncheck to connect to an existing database.

  4. Make sure the Site ID is the same for each web front end.

Creating a SQL TABLE on the SQL Server

Back to top
  1. Run aspnet_regsql.exe in a command line from the from the .Net framework location. For example: c:\Windows\Microsoft.NET\Framework\v4.0.30319>

    Command example: aspnet_regsql -ssadd -d <DBName> -S <DB Server Name> -E -sstype c
    (Replace <DBName> with the name of the database.)

    See the following MSDN article for additional information: ASP.NET SQL Server registration tool

  • Set the machine key and Session state in the web.config file.

    Generate a new machine key using the following instructions at Microsoft Technet: Generate a machine key (IIS7)

    A machine key may look something like the following:

    <machineKey validationKey="86DA9AF40862E1E542318D9C3A8646A9F6D88840BBC906F64C922B6CBE9906C30ECBE7E7D891F8FC25D94F627A2EF8748A31E4FB7C31C5DB2B1367F829542AC5" decryptionKey="5993C1A05E1B7F9B70AE968F1487FAA2B44E537B10CE97974BFD73A0C5802286" validation="SHA1" decryption="AES" />

  • Add the machine key in the web.config file inside the <system.web> tag
  • Add the SQL connection entry in the web.config file inside <system.web> tag

    <sessionState mode="SQLServer" timeout="20" allowCustomSqlDatabase="true" sqlConnectionString="Data Source=< DB Server Name>;Initial Catalog=<DBName>;User ID=;Password=;Integrated Security=true" cookieless="false" />


  • Replace <DBName>in the example above with the name of the database.
  • Provide the same values you receive when you create the session database.
  • Replicate these values in the web.config file for each web front end.
  • Run an IISRESET on all web front ends.