Hi David: I may be producing a Step By Step as I did for the Globalization
process.
I have gained enough understanding to at least know some of the things I
dont know which is actually a major problem when learning a new set of
technicals.
I put my question on this list as I am trying to develop scripts for a
fellow at another, remote, location and need to do it on his machine. Thus,
the tie in to scripting. These questions are a prerequisit to any actual
code related scripting problems I may have in this remote environment.
I would have put them on the general GW WE list but I doubt most people over
there have reason to use Remote Desktop and especially not as a remote
script development environment.
So far the process is a little complicated and I am now researching one of
the blurbs about not being able to read the Logon Window on the Host machine
if we use Virtual Channel whichactually sounds like a requirement for any
use like programming on the host machine from a remote machine because of
performance considerations.
The MS docs talk about using a MMC SnapIn on the host, I think, to disable
this feature by setting some Group Policy settings all of which is new to
me.
I do remember that a few years ago MMC was not accessible with WE or one of
those SnapIns I was trying to use with something called IIS which is the
internet server for a local machine.
Anyway, if I get this puppy working, I intend on putting up a simple to
understand step by step document even though it will be for a set up for 2
Windows XP Professional systems. At least it will demonstrate the process
which is still pretty much the same for Windows 7 as far as I can tell
except for some navigation features of the diferent OS features.
So far:
1) Enable Remote Desktop, a simple checkbox.
2) Ensure the Firewall is opened for the service.
3) Open a port in the Router.
4) get a static IP address or use one of the DNS services.
5) Add a user to the Host Machine.
6) Set up this user as enabled for Remote Desktop access via the Remote
Desktop windows.
7) Disable the Logon Window request on the Host machine.
8) Enable the Audio/Video Support for WE on the appropriate machine, I
forget off the top of my head just now.
9) Enable Virtual Channel on the appropriate machine, think on the Remote
machine.
10) Set up a RDP file with all the necessary info on the Remote machine.
11) Am not any further in the analysis process yet.
I will, of course fill in all the exact details if I make it work for the
above steps with keystrokes, windows and all that jazz.
Oh ya, then there are the security and system restore questions for the
client who knows almost nothing about Windows and nothing about programming
but who will have to implement several of the above operations.
I am not at all sure about debugging a remote session if it doesnt work but
that is another accessibility question for another day.
Rick USA
----- Original Message -----
From: "David" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 08, 2012 3:04 AM
Subject: Re: How To start WE Via A Remote Session
Do have a feeling, we are a good handful of people, who would like a bit
of clarification on th e matter. Maybe not a scripting question, but
definitely would be of general interest to the comunity. Maybe a more
exact example would have been in its place, in the article on the KB.
What I mean is: Instead of talking in a load of general terms, saying
things like - on the server do so, and on the client perform this - you
might want to give specifics. Rewrite the article, telling that on my
computer do this, and on my friend's computer, this and that has to be
done. Then chances are, that there won't be the same amount of uncertainty
as to which computer would be the server, and which would be the client.
Or, make it a project for one of your new Video tutorials. I do agree, the
article as it stands, is not exactly easy for a newbie, and could
definitley have been doing with some kind of more easy presentation. Just
a friendly note.
unfortunately, this is a techie topic, and sometimes it is hard to make a
good article, that is easy to understand, when dealing with techie things.
That was said from personal experience in writing and teaching techie
stuff. But that is where real-life examples, and good illustrations comes
in handy. They make it far more easy for the reader or student to grasp
what you are trying to tell. And, unfortunately, when folowing this
thread, I haven't got much help either. The questions raised have been
real-life enough, but I still feel bewildered from the rather general
answers that have come out. So, for the staff - or anyone else with
experience on the matter - let's please have a real-life step-by-step
explanation. Be it here on this list, the main GWInfo list, or in a
somehow updated KB article or video. Doesn't really matter where, long as
it is clear and straight forwardly dealing with the matter. Please.
----- Original Message -----
From: "Johannes Grib" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 08, 2012 7:25 AM
Subject: RE: How To start WE Via A Remote Session
Hi Stephen, Please copy me in, I'm also very much interested in getting a
we remote session running.
Thanking you and kindest
Johannes
Skype: johannesgrib
-----Original Message-----
From: Stephen Clower [mailto:[email protected]]
Sent: Wednesday, March 07, 2012 2:52
To: [email protected]
Subject: Re: How To start WE Via A Remote Session
Rick,
I will answer you off list on this as the topic doesn't relate to WE
scripting.
Regards,
Steve
On 3/7/2012 4:20 AM, RicksPlace wrote:
Hi Steve:
I am not clear about how to start WE Via A Remote Session.
Since I would have already started WE on my Client machine before
starting to attempt any Remote Session hookup to a host machine which
would be running Remote DeskTop I am not sure what "start WE via a Remote
Session" means or how I would do that
unless that ment starting it on the host machine after logging on to it.
Exactly how do you perform this step?
Note that I couldnt find anything in the WE docs, the article inquestion
or any specific UI element in the WE Control Panel about this particular
step.
Rick USA
--
Stephen Clower
Product support specialist & App Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
