[bcab] Re: Citrix mainframe.

Hi,
This doesn't help, I would have expected ATW do have done a propper assessment of needs. The Tender Holders should have the necessary knowledge. So who loolses out, the employee as usual, and of course the employer.
AS Richard Bartholomew states Window-eyes and JFW will do this, how effectively I don't know. 

I've inserted some of the Window-eyes documentation, I hope this helps.

Best,

Joe Paton

Insert starts here.....

The Basics
Publishing Window-Eyes on a Citrix MetaFrame XP server enables end users to hear other server-based applications, just as if both applications were running locally 
on the desktop.
Server-based deployment of applications has three key benefits:
·
Providing users with secure access to enterprise resources from anywhere at any time 
·
Maximizing IT efficiency with centralized administration
·
Ensuring a consistent set of applications and versions for all users, regardless 
of location, device or connection
For example, a company's IT department can install all the mission-critical applications (such as word processors, email, and order entry systems) on a centralized group of servers. Employees then access the applications on those servers from their own client devices (desktops, laptops, etc.). When the IT department updates a critical application, all users automatically connect to the updated version, without the 
need to install the new application on each individual workstation.
For more information about Citrix MetaFrame XP Presentation Server, visit
www.citrix.com
.
Server-Side Configuration
1. Installing Citrix MetaFrame XP Presentation Server
·
Please refer to the MetaFrame XP documentation for the installation and configuration 
procedures for installing MetaFrame XP.
·
MetaFrame XPe, XPs, or XPa Future Release 3 or greater must be installed on the server 
before you install Window-Eyes and any other applications.
2. Installing Window-Eyes
The steps for installing Window-Eyes on a server running MetaFrame XP are identical 
to the installation steps in
Section 2
 of the Window-Eyes manual.
3. Enabling Window-Eyes Video Support
There are two ways to enable Window-Eyes video support for Citrix MetaFrame XP sessions: 
1.
From the Advanced Options pull down menu in the Window-Eyes program group in the Start menu of the server machine, select the Video Support Maintenance. Select the button labeled "Enable Citrix ICA Video Support" and follow any prompts that may 
appear.
2.
Log on to the MetaFrame XP server remotely and run Window-Eyes. Window-Eyes will 
install Citrix ICA Video Support, and will prompt to restart the machine.
4. Window-Eyes Virtual Synthesizer
The Window-Eyes Virtual Synthesizer option provides the user with the best possible option for remote speech synthesis. Without the Window-Eyes Virtual Synthesizer, the only supported methods of speech during a MetaFrame XP session are serial and software synthesizers. The Window-Eyes Virtual Synthesizer allows the user to utilize any non-serial synthesizer that is installed on the local machine (the Triple Talk PCI, Triple Talk USB, DECtalk PC, and DoubleTalk PC are just a few examples), and is especially useful for maintaining a high rate of responsiveness when using SAPI or software speech. The Window-Eyes Virtual Synthesizer option uses a local copy of Window-Eyes for speech output, rather than relying on the synthesizer itself. 
The local copy of Window-Eyes (which must be running on the client device
?
the same place where the Citrix ICA Client was launched) will serve as a host between the local synthesizer and the remote copy of Window-Eyes. The Window-Eyes Virtual Synthesizer option is also the easiest to set up by following these instructions: 
1. Run Window-Eyes on the client device.
2. Run Window-Eyes through a remote session.
3. From the remote session, select the Virtual (Citrix MetaFrame) synthesizer from the Select Synthesizer dialog box located in the File menu of the Window-Eyes voice 
control panel.
At this point, the remote copy of Window-Eyes will begin transferring speech to the local copy of Window-Eyes. Commands for modifying voice rate, pitch, and tone (as well as the selection of other synthesizers where applicable) will still be executed in the remote session. For information about installing the Window-Eyes Virtual Synthesizer, please refer to the section below titled "Window-Eyes Virtual Server Installation." 
Serial Synthesizers ?
If the Window-Eyes Virtual Synthesizer is not an option, Window-Eyes users have the alternative choice of using any supported serial synthesizer during their MetaFrame XP session. To use a serial synthesizer, follow the steps below for serial port mapping. 
Software Synthesizers
- If the Window-Eyes Virtual Synthesizer is not an option, Window-Eyes users can still use a software synthesizer. Audio support will need to be enabled on either the server-side or client-side. For more information about the pros and cons of using software speech, please refer to the "Remote Access Caveats" section at the end of 
this appendix.
Serial Port Mapping ?
If a Window-Eyes user will be using a serial synthesizer during the Citrix MetaFrame XP session, the appropriate serial ports must be configured correctly prior to launching Window-Eyes to create and maintain a talking environment. After a serial port is mapped for a specific client, the mapping will remain in effect through all future connections from that client. Other clients will not be affected by serial port mapping. 
To map a serial port, use the following steps:
·
Enable serial ports through the Citrix ICA Client application (Citrix Program Neighborhood->Tools->Serial Devices->Add). Please refer to the Citrix ICA Client documentation for more information 
about setting up serial devices.
·
Using the Citrix ICA Client, log on to the appropriate Citrix MetaFrame XP server 
using the credentials of the user who will utilize the mapped serial port.
·
Go to the Start menu, and choose Run.
·
Type CMD and press ENTER.
·
At a command prompt, type the following and press ENTER:
       net use ComX: \\Client\ComY:
(where X is the number of the serial port located on the server and Y is the number 
of the serial port located on the client device.)
·
The following confirmation will display: The command completed successfully.
5. Running Window-Eyes Automatically
To enable automatic startup of Window-Eyes after a Citrix MetaFrame XP session is 
initiated, use the following steps:
1. Log on as the user for whom Window-Eyes is to load automatically.
2. Launch Window-Eyes- and access the Window-Eyes voice control panel with CTRL-BACKSLASH. 
3. Press ALT-F for File.
4. Press R for Startup Options.
5. TAB to the After Login for Current User, Run Window-Eyes radio button group
6. Arrow down to Always
7. Press ENTER to close the Startup Options dialog
When using this configuration, the logon screen will not be spoken automatically. Pass-through authentication is one solution to this issue. For more information about 
pass-through authentication, review the Citrix MetaFrame XP documentation.
Client-Side Configuration
1. Citrix ICA Client
The Citrix ICA Client software does not require any additional setup to support Window-Eyes 
(aside from what is required to connect to a Citrix MetaFrame XP server).
2. Citrix MetaFrame XP Web Access
Citrix ICA Win32 Client Software
If the client is accessing a Citrix MetaFrame XP server through the Web interface, the client will need to download and install the Citrix ICA Client software. This package, as well as any documentation pertaining to the installation of the Citrix ICA Client software, should be available through the Web interface, depending upon 
the configuration of the Citrix MetaFrame XP server.
Citrix ICA Java Client Software
Although the Citrix ICA Java Client software will perform the same as the Citrix ICA Win32 Client software (in terms of running Window-Eyes remotely), it will not support the Window-Eyes Virtual Synthesizer. To use the Citrix ICA Java Client software, the client will need to use either a serial synthesizer (please refer to the above 
section titled "Serial Port Mapping" for more information) or software speech.
3. Alternative Citrix ICA Clients
Citrix ICA Clients for alternative operating systems (Windows CE, UNIX, Macintosh, and so on) will support running Window-Eyes remotely. It is important to note, however, that the Window-Eyes Virtual Synthesizer option is available only with the Citrix 
ICA Win32 Client software.
4. Window-Eyes Virtual Channel Installation
To install the Window-Eyes Virtual Channel, use the following steps:
1.
From the Advanced Options pull down in the Window-Eyes program group in the start 
menu of the client machine, run the Virtual Channel Maintenance utility.
2.
TAB to the "Enable Citrix Virtual Channel Support For Window-Eyes" button, and press 
ENTER.
To uninstall the Window-Eyes Virtual Channel, use the following steps:
1.
From the Advanced Options pull down in the Window-Eyes program group in the start 
menu of the client machine, run the Virtual Channel Maintenance utility.
2.
TAB to the "Disable Citrix Virtual Channel Support For Window-Eyes" button, and press 
ENTER.
Running Window-Eyes Remotely
1. Important Hot Keys
·
Citrix ICA Client hot keys can be defined by modifying the options located in Citrix Program Neighborhood->Tools->ICA Settings->Hotkeys. These hot keys are required for accessing the remote desktop operating system Start menu, ALT-TAB list, task list, and so on. For more information about defining Citrix ICA Client hot keys, please 
refer to the Citrix ICA Client documentation.
·
Window-Eyes hot keys can be modified under the Hot Keys dialog in the Window-Eyes 
voice control panel. All Window-Eyes hot keys are defined in
Appendix A
 of the Window-Eyes manual.
2. Desktop Versus Stand Alone Application
Window-Eyes can be accessed by logging on to a published desktop, or by using Window-Eyes as a published application (depending on the configuration of the Citrix MetaFrame XP server). During a remote desktop session, Window-Eyes will interact with any other application launched in the same desktop area. As a published application (not accessed through a remote desktop session), Window-Eyes will only interact with other published applications launched in the same client's unique session. For example, if Window-Eyes and Microsoft Internet Explorer are both shared applications, and the client runs both applications during a unique session, Window-Eyes will be able to read and interact with the Microsoft Internet Explorer window. Running Window-Eyes as a published application will not read any local application that is run on the client device. Running Window-Eyes remotely through Citrix MetaFrame XP will only allow speech access to other remote applications run under the same unique session. Your local copy of Window-Eyes, however, 
can be used to interact with your local applications.
It is important to note that, while running Window-Eyes as a remote application, and as a local application, you will have two instances of Window-Eyes on the taskbar at one time. You will be able to tell the difference by examining the names of the 
applications.
3. Interacting with Other Applications
After a user initiates a Citrix MetaFrame XP session and is running Window-Eyes successfully, the interaction between Window-Eyes and any installed application will work identically to running Window-Eyes on a stand alone machine with that same application. For example, Window-Eyes keystrokes, hot keys, and reading options for Microsoft Internet Explorer will work the same whether Window-Eyes is running locally or through a remote Citrix 
MetaFrame XP session.
4. Multiple Window-Eyes sessions
Multiple users can run Window-Eyes under their own unique sessions with no conflicts with other instances of Window-Eyes running remotely in Citrix MetaFrame XP sessions. 
Running Window-Eyes Locally on Server
Window-Eyes can be run on the Citrix MetaFrame XP desktop with no conflicts with other instances of Window-Eyes running remotely in Citrix MetaFrame XP sessions. 
Remote Access Caveats
1. Software Speech
At the time of this documentation, support for SAPI speech synthesizers in a remote Citrix MetaFrame XP session is somewhat lacking. Although the voice quality can remain tolerable, the responsiveness (even over high bandwidth network connections) can lag behind up to two seconds behind a given key press. For a solution to this problem, review the Window-Eyes Virtual Synthesizer option listed in the Server-Side Configuration 
section.
2. Hot Key Conflicts
Window-Eyes users are often comfortable with the Windows hot keys (such as CTRL-ESC, ALT-TAB, etc.) that allow them easy access to commonly used areas in the operating system. Pressing these keys during a remote session will most likely cause the intended action to execute locally rather than in the Citrix MetaFrame XP session. It is important to note the Important Hotkeys section of the Running Window-Eyes Remotely section 
listed above.
3. Citrix MetaFrame XP Management Console
At the time of this documentation, the Citrix MetaFrame XP Management Console application (available only to the Administrator of the Citrix MetaFrame XP server) is written in Java. Window-Eyes, currently, does not support the Java language interface, and therefore does not provide access to the Citrix MetaFrame XP Management Console. 
4. Window-Eyes Local Versus Window-Eyes Remote
If a user runs Window-Eyes on a client device while at the same time running the Citrix ICA Client software, Window-Eyes will remain loaded, but in a suspended state. This will eliminate any hot key conflicts between the local copy of Window-Eyes and remote copy of Window-Eyes. To communicate with the local copy of Window-Eyes, or other local applications, the user will need to ALT-TAB out of the Citrix ICA Client to switch activation from the Citrix ICA Client to the local desktop. Window-Eyes will no longer be suspended once activation has left the Citrix ICA Client. Closing the Citrix ICA Client will also result in the local desktop regaining activation. It is possible, even after pressing ALT-TAB to move activation to the local desktop, for the remote copy of Window-Eyes to send information to the local copy of Window-Eyes through the Window-Eyes Virtual Synthesizer feature. This may cause some speech to 
bleed through.

At 11:53 26/09/2008, you wrote:
I don't know about magnification but for speech, both Window-Eyes and JAWS work with Citrix - albeit you need to pay extra for the privilege of JAWS in this environment. The manuals for both contain info on this topic but I would assume there should be something on their respective websites, too. 



Regards
Enterprise Middleware


 Richard Bartholomew
 ISOS Enterprise Middleware
 Standard Life Employee Services Limited
 8 Glenogle Road, Edinburgh, EH3 5HN
 Phone: 0131 245 1667




Léonie Watson <tink@xxxxxxxxxx>
Sent by: bcab-bounce@xxxxxxxxxxxxx

26/09/2008 11:49
Please respond to
bcab@xxxxxxxxxxxxx

To
"BCAB" <bcab@xxxxxxxxxxxxx>
cc
Subject
[bcab] Citrix mainframe.




Morning,
Can anyone advise which screen readers, if any, work comfortably 
with Citrix mainframes? BCAB have had an email on behalf of a Supernova user
who has begun working for an organisation which runs Citrix mainframes. In
their words, "This seems very hostile to assistive technology and for
example, with Dolphin Access?s Supernova, Citrix disables the audio
facility, disables the keyboard hot keys for magnification and also prevents
background colour changes for Word to allow access aggressive pale blue or
green."
This isn't an area I'm familiar with, so I thought I'd look into it. 
If anyone can point me at some information or resources, that would be
great. Thanks.

Léonie.

--
http://www.tink.co.uk/



***  BCAB List administration ***
If you wish to unsubscribe, set vacation,, request a digest or carry out routine maintenance on your subscription to the list then go to: 
http://www.bcab.org.uk/mailing-list.html
Alternatively, send an email to bcab-request@xxxxxxxxxxxxx with the word faqin the subject line. You'll receive an email with advice on managing your subscription to the list. 

If you wish to discuss the administration of the list then contact:
bcab-moderators@xxxxxxxxxxxxx
This e-mail is confidential and, if you are not the intended recipient, please return it to us and do not retain or disclose it. We filter and monitor e-mails in order to protect our system and the integrity, confidentiality and availability of e-mails. We cannot guarantee that e-mails are risk free and are not responsible for any related damage or unauthorised alteration of e-mails by third parties after sending.
For more information on Standard Life group, visit our website http://www.standardlife.com/
Standard Life plc (SC286832), Standard Life Assurance Limited* (SC286833) and Standard Life Employee Services Limited (SC271355) are all registered in Scotland at Standard Life House, 30 Lothian Road, Edinburgh EH1 2DH. *Authorised and regulated by the Financial Services Authority. 0131 225 2552. Calls may be recorded/monitored. Standard Life group includes Standard Life plc and its subsidiaries. 

Please consider the environment. Think - before you print.

The Basics
Remote access via Microsoft Terminal Services, generally speaking, allows users to access a specific machine's desktop from a remote location. For example, a consultant meeting with a client at a remote site may need to access a database installed on a machine located at the consultant's office. Having access to important information from any remote location can drastically reduce the amount of overhead for a traveling 
consultant.
Server Side Configuration
Windows 2000 Server
·
Please refer to the Windows 2000 Server documentation for the installation and configuration 
procedures for installing Microsoft Terminal Services.
·
Due to a limitation in Windows 2000 Server, data redirection (both audio and serial communication) is unavailable. Only the Window-Eyes Virtual Channel is supported 
during Remote Desktop connections to a Windows 2000 Server.
Windows Server 2003
Please refer to the Windows Server 2003 documentation for the installation and configuration 
procedures for installing Microsoft Terminal Services.
To enable data redirection in Windows Server 2003, use the following steps:
1.
Press CTRL-ESC to open the Start Menu
2.
Press R for Run
3.
Type gpedit.msc, and press ENTER. This will launch the Group Policy Object Editor. 
4.
Traverse to the Local Computer Policy->Computer Configuration->Administrative Templates->Windows 
Components->Terminal Services->Client/Server data redirection folder.
5.
Press TAB to access the content pane.
6.
Arrow Down to the "Allow audio redirection" option and press ENTER.
7.
Press ALT-E to select the Enabled radio button, and press ENTER.
8.
Arrow Down to the "Do not allow COM port redirection" option and press ENTER.
9.
Press ALT-D to select the Disabled radio button, and press ENTER.
10.
Press ALT-F4 to close the Group Policy Object Editor
Windows XP Professional
To enable Remote Desktop access in Windows XP Professional, use the following steps: 
1.
Press CTRL-ESC to open the Start Menu.
2.
Press M for My Computer (this step assumes the default start menu style).
3.
Press SHIFT-F10 to open the context menu for My Computer.
4.
Press R for properties.
5.
Press SHIFT-TAB to access the System Properties tab control.
6.
Arrow Right to the Remote tab.
7.
TAB to the "Allow users to connect remotely to this computer" check box.
8.
Press SPACE-BAR to check this check box.
9.
Press ENTER to close the Remote Sessions information dialog.
10.
TAB to the Select Remote Users button, and press SPACE BAR.
11.
TAB to the Add button, and press SPACE BAR.
12.
Enter the names of the users who should have remote access.
13.
TAB to OK, and press ENTER to close the Select Users dialog.
14.
TAB to OK, and press ENTER to close the Remote Desktop Users dialog.
15.
TAB to OK, and press ENTER to close the System Properties dialog.
Windows Vista
To enable Remote Desktop access in Windows Vista, use the following steps:
1.
Press CTRL-ESC to open the Start Menu
2.
Press TAB, followed by C until you select Computer
3.
Press SHIFT-F10 to open the context menu for Computer
4.
Press R for properties
5.
TAB to Advanced system settings, and press ENTER. NOTE: You may need to confirm a 
User Account Control dialog at this point.
6.
Press SHIFT-TAB to access the System Properties tab control
7.
Arrow Right to the Remote tab.
8.
TAB to the Remote Desktop radio button group
9.
Use your arrow keys to select either "Allow connections from computers running any version of Remote Desktop (less secure)," or "Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)," depending 
on which one you require
10.
TAB to the Select Remote Users button, and press SPACE BAR.
11.
TAB to the Add button, and press SPACE BAR.
12.
Enter the names of the users who should have remote access.
13.
TAB to OK, and press ENTER to close the Select Users dialog.
14.
TAB to OK, and press ENTER to close the Remote Desktop Users dialog.
15.
TAB to OK, and press ENTER to close the System Properties dialog.
For more information on advanced options for Windows XP Professional Remote Desktop 
access, please refer to the Windows XP Professional documentation.
Installing Window-Eyes
The steps for installing Window-Eyes on a server running Microsoft Terminal Services 
are identical to the installation steps found in
Section 2
 of the Window-Eyes manual.
Enabling Window-Eyes Video Support
There are two ways to enable Window-Eyes video support for Microsoft Terminal Services 
sessions:
1.
From the Advanced Options pull down in the Window-Eyes program group in the start menu of the server machine, run the "Video Support Maintenance" utility. Select the button labeled "Enable Microsoft RDP Video Support" and follow any prompts that may 
appear.
2.
Log into a Microsoft Terminal Services session, and run Window-Eyes. Window-Eyes will install Microsoft RDP Video Support, and will prompt to reboot the machine. 
Window-Eyes Virtual Channel
The Window-Eyes Virtual Channel option provides the user with the best possible option for remote speech synthesis. Without the Window-Eyes Virtual Channel, the only supported methods of speech during a Microsoft Terminal Services session are serial and software synthesizers. The Window-Eyes Virtual Channel allows the user to utilize any non-serial synthesizer that is installed on the local machine (the Triple Talk PCI, Triple Talk USB, DECtalk PC, and DoubleTalk PC are just a few examples), and is especially useful for maintaining a high rate of responsiveness when using SAPI or software speech. The Window-Eyes Virtual Channel option uses a local copy of Window-Eyes for speech output, rather than relying on the synthesizer itself. The local copy of Window-Eyes 
(which must be running on the client's workstation
?
the same place where the Microsoft Remote Desktop Client was launched) will serve as a host between the local synthesizer and the remote copy of Window-Eyes. The Window-Eyes Virtual Channel option is also the easiest to set up by following these instructions: 
1.
Run Window-Eyes on the client machine.
2.
Run Window-Eyes via a remote session.
3.
From the remote session, select the "Virtual (Microsoft RDP)" synthesizer in the Select Synthesizer dialog located in the File menu of the Window-Eyes voice control 
panel.
At this point, the remote copy of Window-Eyes will begin transferring speech to the local copy of Window-Eyes. Commands for modifying voice rate, pitch, and tone (as well as the selection of other synthesizers where applicable) will still be executed in the remote session. Neither audio redirection nor data redirection need to be enabled for Window-Eyes Virtual Channel support to work. For information on installing the Window-Eyes Virtual Channel, please refer to the section below titled Window-Eyes 
Virtual Server Installation.
Serial Synthesizers ?
If the Window-Eyes Virtual Channel is not an option, Window-Eyes users have the alternative choice of using any supported serial synthesizer during their Microsoft RDP session, assuming that serial port communication is available. To use a serial synthesizer, be sure to note the configuration options of the Microsoft Remote Desktop 
Connection utility in the Client Side Configuration section below.
Software Synthesizers
- If the Window-Eyes Virtual Channel is not an option, Window-Eyes users may still use a software synthesizer, assuming that audio communication is available. For more information on the pros and cons of using software speech, see the Remote Access 
Caveats section at the end of this appendix.
3. Running Window-Eyes Automatically
To enable automatic startup of Window-Eyes once a Microsoft Remote Desktop session 
has been initiated, use the following steps:
1. Log on as the user for whom Window-Eyes is to load automatically.
2. Launch Window-Eyes- and access the Window-Eyes voice control panel with CTRL-BACKSLASH. 
3. Press ALT-F for File.
4. Press R for Startup Options.
5. TAB to the After Login for Current User, Run Window-Eyes radio button group
6. Arrow down to Always
7. Press ENTER to close the Startup Options dialog
When using this configuration, the log in screen will not be spoken automatically. Automatic login via the Microsoft Remote Desktop Connection utility is one solution to this issue. For more information on this feature, please review the Remote Desktop 
Connection utility documentation.
Client Side Configuration
Microsoft Remote Desktop Connection Utility
Windows XP Professional, Windows Server 2003, and Windows Vista include the Microsoft Remote Desktop Connection Utility, which is located under the Start Menu, Programs, Accessories, Communications folder. Other operating systems will need to obtain the 
utility from the following website:
www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp
Data Redirection
Audio ?
To ensure that sound events occurring on the server machine are directed to the 
client machine, use the following steps:
1.
Launch the Remote Desktop Connection Utility.
2.
Press ALT-O for Options.
3.
TAB to the Remote Desktop Connection Utility tab control.
4.
Arrow Right to Local Resources.
5.
TAB to the Remote Computer Sound combo box.
6.
Press B for the Bring to this computer option.
7.
Press ENTER to connect to the specified server.
Serial ?
To ensure that serial communication on the server machine is directed to the client 
machine, use the following steps:
1.
Launch the Remote Desktop Connection Utility.
2.
Press ALT-O for Options.
3.
TAB to the Remote Desktop Connection Utility tab control.
4.
Arrow Right to Local Resources.
5.
TAB to the Serial Ports check box.
6.
Press SPACE-BAR to check this check box.
7.
Press ENTER to connect to the specified server.
Please refer to the Microsoft Remote Desktop Connection Utility documentation for 
additional configuration options.
Microsoft Remote Desktop Connection Web Connection
At this time, Window-Eyes will not support the Microsoft Remote Desktop Connection Web Connection method of accessing remote servers via the Microsoft Remote Desktop 
Connection Web Connection ActiveX control.
Window-Eyes Virtual Channel Installation
To install the Window-Eyes Virtual Channel, use the following steps:
1.
From the Advanced Options pull down in the Window-Eyes program group in the start 
menu of the client machine, run the Virtual Channel Maintenance utility.
2.
TAB to the "Enable Microsoft Virtual Channel Support for Window-Eyes" button, and 
press ENTER.
To uninstall the Window-Eyes Virtual Channel, use the following steps:
1.
From the Advanced Options pull down in the Window-Eyes program group in the start 
menu of the client machine, run the Virtual Channel Maintenance utility.
2.
TAB to the "Disable Microsoft Virtual Channel Support for Window-Eyes" button, and 
press ENTER.
Running Window-Eyes Remotely
Important Hotkeys -
While using the Microsoft Remote Desktop Connection Utility the system hot keys will apply to the remote system while in full screen, and the local system while in windowed mode. The following list of Microsoft Remote Desktop Connection Utility hot keys 
will assist in navigating the remote desktop under all operating systems:
ALT-PAGE UP ? Switches between programs from left to right.
ALT-PAGE DOWN ? Switches between programs from right to left.
ALT-INSERT ? Cycles through the programs in the order they were started.
ALT-HOME ? Displays the Start Menu.
CTRL-ALT-BREAK ? Switches the client between a window and full screen.
CTRL-ALT-END ? Brings up the Windows Security dialog box.
ALT-DELETE ? Displays the Windows menu.
CTRL-ALT-NUMPAD-MINUS
- Places a shadow copy of the active window within the client, on the Terminal server clipboard, which provides the same functionality as pressing PrintScrn on a local 
computer.
CTRL-ALT-NUMPAD-PLUS
- Places a shadow copy of the entire client window area on the Terminal server clipboard, which provides the same functionality as pressing ALT+PrintScrn on a local computer. 
Multiple Window-Eyes Sessions
Multiple users can run Window-Eyes under their own unique sessions with no conflicts with other instances of Window-Eyes running remotely via Microsoft Terminal Services sessions. For more information on running multiple Remote Desktop sessions under 
Windows XP Professional, refer to the Remote Access Caveats section.
Running Window-Eyes Locally on Server
Window-Eyes can be run on the Windows Terminal Services desktop with no conflicts with other instances of Window-Eyes running remotely via Microsoft Terminal Services 
sessions.
Remote Access Caveats
Software Speech
At the time of this documentation, support for SAPI speech synthesizers on a Microsoft Terminal Services session is slightly lacking. Although the voice quality is tolerable, the responsiveness (even over high bandwidth network connections) can lag behind. For a solution to this problem, please review the Window-Eyes Virtual Channel option 
listed in the Server Side Configuration section.
Windows 2000 Server Data Redirection
Windows 2000 Server does not support data redirection, meaning that neither audio services nor serial communication are available when connecting remotely to a Windows 2000 Server running Microsoft Terminal Services. This is a limitation of the Windows 2000 Server operating system. The only solution is to utilize the Window-Eyes Virtual 
Channel option listed in the Server Side Configuration section.
Windows XP Remote Assistance
Remote Assistance is not supported through Microsoft Terminal Services, and is therefore 
not supported by Window-Eyes.
Windows XP Professional/Windows Vista
Only one login per session is allowed when logging into Windows XP Professional or Windows Vista remotely. If a different user is already logged into that machine, the Microsoft Remote Desktop Connection Utility will prompt to continue the log in, which will consequently log out the currently logged in user. If the same user is already logged into that machine, the Microsoft Remote Desktop Connection Utility will automatically log out the current session, and continue the remote log in process 
with no warnings.
Windows XP Home
Windows XP Home does not have the necessary components to act as a server with either Microsoft Terminal Services or Microsoft Remote Desktop. This is a limitation of the Windows XP Home operating system. Windows XP Home can, however, support the Microsoft Desktop Connection Utility when used to connect remotely to other Microsoft Terminal 
Services servers or Microsoft Remote Desktops.

JPEG image

Other related posts: