Note that this help is for the General Settings Tab in Profiles Mode
Profiles Activation
Checking this box is required for Profiles Mode -- You can un-check to return to basic configuration, which should only be performed in the case that Profiles Mode has introduced undesired side effects in your environment.
Base Profiles Folder
This defaults to a folder on the server in the ProgramData folder, which is by default a hidden folder. For clustered servers, it is recommended that this be set to a shared location accessible by each clustered server. See Sharing Folders, below for tips on configuring your servers to support shared folders.
Cluster Configuration Synchronization Folder
This is shown when your server is a member of a cluster--because some elements, like the local registry and web.config file, cannot be shared in a networked environment, exports of these configuration stores are made as part of a change and copied to the synchronization folder.
Replicating the objects in the folder (web.config copy and registry export file) can then be performed by an administrator using a Powershell script or Remote Desktop sessions on each of the other clustered servers. See Sharing Folders, below for tips on configuring your servers to support shared folders.
Wizard Actions - Add a New Host Definition
For convenient access, a button is provided to run a New Host Wizard on the General Settings tab--this is the same as clicking the Server+ icon on the Host Connections Tab at the upper right of the page. The New Host Wizard provides immediate diagnostics and assistance in defining a host connection.
Wizard Actions - Add a New Terminal Emulation Profile Definition
For convenient access, a button is provided to run the New Profile Wizard. The New Profile Wizard provides immediate feedback as fonts, CSS and other options are selected as part of creating the profile.
Sharing Folders in Clustered Environments
There are two ways that sharing works with Windows Servers--one is when the servers are members of a Windows Domain, while the other is when the servers are not members of a Windows Domain.
Members of a Windows Domain
In this mode, a domain account will be needed that has sharing rights to the shared folders. This can be a system account but must be a member of the domain and not simply the local windows configuration.
Not Members of Windows Domain
This requires a simple trick--on each clustered server, create an account with the same name for purposes of sharing, and be sure to use the same password on each server.
Once a domain account or common local account has been created and/or identified, it should be set as the account for the FVTerm v4.0 Application Pool using the Advanced Settings for the pool in the IIS Management Console. Then for each shared folder, be sure that this account has full access (create/read/update) to the folder.
