Technical Support - Detail
The installation options are as follows:
1. You can set up a server with JAWS speech active on the local server console where JAWS can be used directly on the console itself or can be used remotely via Terminal Services or Citrix Neighborhood. To do this, install JAWS as a standard user typical install. By default JAWS 7.10 will install all of the components necessary for JAWS to be usable as a remote JAWS server. Once installation is completed be sure you reboot the server machine so that all of the remote components become active. There is nothing more you will need to do on the server side.
2. You can install JAWS directly on the console as a server without speech. This will have the effect of not installing any of the JAWSVID DCM Video intercept components other than the FSRDP Remote server video hooks. You still get speech and braille via remote Terminal Services/Citrix access. To do this open the Run dialog and type in the path to the JAWS installer and use the "/type remote" installation switch. For example "d:\JAWS\setup\J7.10.417U_ILM.exe /type remote". Just proceed with a typical installation and JAWS will install all of the components necessary for a remote JAWS server to work. Once the installation is complete, you must restart the server. There is nothing more you need to do on the server side.
3. If users do not need JAWS access for the server console, you can install JAWS remotely. To do this, connect via Terminal Services or Citrix Neighborhood and install JAWS using the "/type remote" installation switch. With this type of installation, JAWS does not install the JAWSVID DCM video hooks other than the FSRDP remote hooks. For example, to do this type of installation copy the J7.10.417U_ILM.exe installer from your CD to c:\ and from the run dialog you can type "c:\J7.10.417U_ILM.exe /type remote". Then proceed with a typical installation. Be sure to restart the server once installation is completed. There is nothing further you need to do to make the Remote JAWS server work.
Regardless of which method you use, you must have administrative privileges for the server
In versions of JAWS prior to JAWS 7.10 it was necessary to select the Remote client option from the Guided or Advanced installation options either during installation or via Installation Maintenance. For JAWS 7.10 or later you no longer need to run the installer to install the Remote JAWS Client components. JAWS 7.10 and later automatically includes all of the client component files necessary during installation. However, while the client components are installed during installation these components are not enabled by default. This means you can install Citrix Network Neighborhood Client after JAWS 7.10 or later is already installed. Whereas in versions of JAWS prior to 7.10 you needed to install Citrix Network Neighborhood before you installed JAWS.
To make any installation of JAWS function as a Remote JAWS Client capable of connecting to a Terminal Server or Citrix server, the "Enable Remote Access Client" check box has been added to the Advanced dialog box (accessed from the Basic Settings dialog box). If you select this check box, JAWS will make the changes necessary to make your installation of JAWS capable of functioning as a Remote JAWS Client. If you disable this option, JAWS will remove the changes and your local JAWS will no longer function as a Remote JAWS Client. This is useful when you had checked this option because you used it for Terminal Services but now want to install and use a Citrix Network Neighborhood client. Here are the steps:
- Install the Citrix Neighborhood Client.
- Clear the Enable Remote Access Client check box.
- Choose OK for all open JAWS dialog boxes.
- Go back into the JAWS Basic Settings dialog and select the "Enable Remote Access Client" check box. JAWS will make the changes necessary to enable you to use both Remote Terminal Services Client and citrix Network Neighborhood Client.
Last updated July, 2006
Version: 7.10 plus
Category: Remote Access