Administering relay servers and dependent hosts on different networks

When a user starts the FH Web Edition Connection Manager on a relay server or a dependent host, the FH Web Edition Connection Manager connects to the relay server and attempts to authenticate the user using integrated Windows authentication. If the FH Web Edition Connection Manager is running on a dependent host and the associated relay server is located on a different network, a message such as the following is displayed:

Failed to log you on to Server8. This computer (Server4) and Server 8 may be located on different networks. Would you like to log onto Server 8 and administer it remotely?

Clicking No returns you to the FH Web Edition Connection Manager, and its All Hosts list. Clicking Yes initiates a special remote administration session on the relay server as follows:

1. The FH Web Edition Connection Manager on the dependent host starts the FH Web Edition client.

2. The client connects to the relay server and starts a session.

   The Sign In dialog box appears to the user.

3. The user signs in, specifying the user name and password of an account that is a member of the Administrators group on the relay server.

4. The FH Web Edition Connection Manager starts on the relay server.

   The user can now administer the relay server and all of its dependent hosts. A maximum of two administration sessions can run on the relay server at any given time, regardless of the Maximum sessions on this host setting in the FH Web Edition Connection Manager, and regardless of license restrictions.

Dependent hosts inherit their list of published applications, server settings, and user settings from the relay server. Applications must be installed in the same directory on all dependent hosts.

Caution: Applications do not need to be installed on the relay server.

When a FH Web Edition server is connected to a relay server, all of its server settings are synchronized with those of the relay server. When any changes are made to the relay server’s settings, they are also made to all hosts connected to that relay server. The only settings allowed to vary are the maximum number of sessions and the name of the relay server. All other settings in the Host Options and Application Properties dialog boxes are grayed out and cannot be modified.

When setting up a relay server, if an application is installed but not published on the dependent host, the application needs to be published on the relay server through the FH Web Edition Connection Manager.

Example: Suppose Adobe Reader 7.0 is installed on the dependent host at C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe. You would need to open the FH Web Edition Connection Manager on the relay server, access the Add Application dialog box, and type this path location in Executable Path.

Note: Before publishing an item on a mapped drive, verify that the drive is mapped to the same drive letter and location on the dependent hosts as it is on the relay server.