Extract - If running Terminal Services, Please read this Extract from the Ostendo Installation Specification regarding Ports, Registry Keys, etc:-

All computer networks must have at least UTP Category 5 Cable and 100mbps network speed.

Ensure all workstations are running “Microsoft TCP/IP” network protocol in a networked environment.

(See your Windows documentation for information on installing TCP/IP).

Turn on file sharing and share the folder where Ostendo is to be installed on the server or main workstation. Please allow full access to the shared folder under security for all client or workgroup workstations.

The “Firebird Server” and “Firebird Guardian Service” (Services) use the “Local System” account to logon. If you decide to install the database to a separate physical hard disk on your server or workstation, that is not your system disk, you will need to make sure the “Local System” account has sufficient access rights to the disk and directory which you have installed the database.

• Open ports 3050 TCP and 4380 TCP on the firewall to allow network communication to the Firebird Database, as follows:

      Open Control Panel/Security Center/Windows Firewall

      Click on the exceptions tab and click the Add Port button

      Name:  Firebird                         Name:  Firebird

      Port Number:  3050               Port Number:  4380

      Select TCP                                Select TCP

• From the Client or Workgroup workstations, Run the Client installation by double clicking on the  setup executable file “X:\Clients\Setup.exe” or “VistaClient.exe” for Windows Vista Clients (where X: is the drive you have mapped in 12 above) to the Server or Main Workstation. The set up program guides you through the installation process. Please install the Firebird Database and the Ostendo Software Application. Please run the network tests at the end of each client or workgroup workstation installation to ensure correct database communication. 

 Note:    Installing Ostendo in a terminal server environment is similar to a client server network installation, with these additional checks required.

 On the Terminal Server Platform Please Ensure:

1. The terminal server is in Application Server Mode (Windows 2000 Server) or has the role of Terminal Server (Windows Server 2003 or 2008) before installing Ostendo (unless this server is used specifically for remote administration).
2. The terminal server is in "Install Mode" before installing Ostendo.  This can be accomplished by initiating the install routine via "Add/Remove Programs" or by manually placing the server in "Install Mode" with the cmd prompt utility "change user /install".  After the install is complete you place the server back in "execute mode" via "change user /execute".  You must perform the last step prior to placing the server back into “execute mode”.
3. Run the Ostendo installation from the CD or download link provided (Setup.exe) choosing the Terminal Server option and follow the installation wizard.
4. IMPORTANT: Run Ostendo once before clicking Finish in Add\Remove Programs (or before running change user /execute).  Update Ostendo with your Company License Key.  This will cause Ostendo to create the necessary registry settings.
5. NB: Please add "Everyone" to the Permissions list of these 2 registry keys.

Registry Keys used by Ostendo 32 bit platform:

• HKEY_CURRENT_USER\Software\Ostendo
• HKEY_LOCAL_MACHINE\SOFTWARE\Development-X Limited\Ostendo

Registry Keys used by Ostendo 64 bit platform:

• HKEY_CURRENT_USER\Software\Ostendo
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Development-X Limited\Ostendo

**Please read this Special Note…(Ostendo Versions Prior to Update 121)

**This registry value is read to obtain a folder location for Ostendo to store licence files, this must be user writeable and is normally set to the following:
 (Windows Vista, Windows 7 and Windows Server 2008) %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Cookies
 (Windows XP and for Windows Server 2003) %USERPROFILE%\Cookies

       HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Cookies