Hi:
I am going to implement the Remote Desktop feature of Windows XP Pro.
In the WE Docs I am confused which machine is which.
In my mind the Host Machine would be the machine running Remote Desktop and the 
Client machine the machine logging into the Host machine from a remote location 
which does not have to run Remote Desktop locally.
Before I try and implement this puppy for testing and (subsequently have a 
small business client implement it at their corporate headquarters) I would 
like to ensure my understanding of the docs and thus have a few short questions:
>From the Docs and short questions:
To enable Remote Desktop access in Windows XP Professional, use the following 
steps:
... Rest removed for brevity.
Enabling Window-Eyes Video Support
...
Question:
Do we enable Video Support on a standard Windows XP Pro machine hosting the 
Remote Desktop Utility?
The docs look like this step is only for a Server OS like Windows 2003 or 2008.

Window-Eyes Virtual Channel
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) 
Question:
Does this mean the machine where Remote Desktop is enabled or the machine that 
will connect to the computer hosting the Remote Desktop service?
I am not sure where it is launched. I would think an app would be launched on 
the Host machine by the Remote Client machine but that is not what it sounds 
like.

To enable the virtual channel support for your synthesizer and Braille display, 
use
the following procedure:
1. Run Window-Eyes on the client machine.
2. Run Window-Eyes via a remote session.
...
Question:
Here, is the Client Machine the Remote DeskTop enabled host or some external 
machine logging into the Remote Desktop hosting Machine or even the host 
machine but the user logging on to the host machine using the Remote Enabled 
name and password?
Again, I am confused by which machine is to be the Client and which the Host.
 At this point, the remote copy of Window-Eyes will begin transferring speech 
to the
local copy of Window-Eyes. 
Question: Is the local copy of WindowEyes on the machine logging into the host 
machine (hosting the Remote Desktop session) or on the host machine itself?

Neither audio redirection nor data redirection need to be
enabled for Window-Eyes Virtual Channel support to work. 
Question:
Does this include the sounds feature as described in a later section and noted 
below?

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 control panel with 
CTRL-BACKSLASH.
...
Can this be done by a remote client logged on to the host machine or is it to 
be done by someone logging on to the Host machine Desktop from the host machine 
itself?

Client Side Configuration
Question does this section on "Client Side" refer to the computer which will be 
logging on to the machine hosting the Remote Desktop Service or the host 
machine itself?
Microsoft Remote Desktop Connection Utility
...
Data Redirection
To ensure that sound events occurring on the server machine are directed to the 
client
machine, use the following steps:
Question:
Does this refer only to Remote Desktop running on a Server OS rather than a XP 
Pro machine?
Also, as noted above, is this still relevant if we use the Virtual Channel?
...

To ensure that serial communication on the server machine is directed to the 
client
machine, use the following steps:
Question:
Again this mentions a "Server" machine, does this apply to an XP Machine as 
well?
If Virtual Machine is used is this still relevant?1. 

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.
Question:
Again, which machine is the Client? The machine hosting Remote Desktop or the 
machine logging into the machine hosting Remote Desktop?

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.
Question:
Does this only apply to Server OS or does this include XP since the below blurb 
would indicate someone could not be working on the host machine if a remote 
user was also using it on a Windows XP Machine.
Remote Access Caveats
...
Login Restrictions
Only one login per session is allowed when logging into Windows XP Professional,
Windows Vista, or Windows 7 remotely. 
...
End Of Questions.
Thanks:
Rick USA
If you reply to this message it will be delivered to the original sender only. 
If your reply would benefit others on the list and your message is related to 
GW Micro, then please consider sending your message to [email protected] so 
the entire list will receive it.

GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage 
your list subscription at http://www.gwmicro.com/listserv.

Reply via email to