Les
Wed Nov 19 23:07:01 CST 2003
Hi Henry,
What I was meaning is that you will only be able to connect *to* xp, so if
you have w2k workstations then you'd be outa luck as they do not have the
rdp server end.
I have used the rdp client (from the xp cd) on w98 and it works fine.
--
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Henry Craven" <IUnknown@d.com> wrote in message
news:OUu02oxrDHA.1196@TK2MSFTNGP12.phx.gbl...
> You may be able to overcome that.
> ie: Run Remote Desktop on pre-XP machines
>
> Remote Desktop Connection Client
> By Charlie Russel
>
http://www.microsoft.com/windowsxp/expertzone/columns/russel/02january28.asp
>
> ( Note: I haven't tried it yet )
> --
> Henry Craven.
>
> ========= Post It Appropriately: ============
> SBS 4/4.5 : microsoft.public.backoffice.smallbiz
> SBS 2000 : microsoft.public.backoffice.smallbiz2000
> SBS 2003 : microsoft.public.windows.server.sbs
> =====================================
>
> "Les Connor [SBS MVP]" <les.connor@cfiveDEL.ca> wrote in message
> news:OyRSpAvrDHA.560@TK2MSFTNGP11.phx.gbl...
> > Not so fast .....
> >
> > Now hear this:
> >
> > Remote Control is a small add-on that adds the option to right-click a
> > computer account in the Active Directory MMC and choose Remote Control
> on
> > that computer by opening a Terminal/Remote Desktop connection to that
> > computer. Remote Control relies on the Remote Desktop Connection
> software
> > that must be installed in order to use this add-on.
> >
> >
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=0a91d2e7-7594-4abb-
> > 8239-7a7eca6a6cb1&DisplayLang=en
> >
> > But it probably only works on XP workstations.
> >
> > --
> > Les Connor [SBS MVP]
> > -------------------------------------
> > SBS Rocks !
> >
> >
> >
> > "Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in
> message
> > news:OPMHc3srDHA.3416@tk2msftngp13.phx.gbl...
> > > Hello,
> > >
> > > SBS2K. Win2000/XP clients.
> > >
> > > I decided to go with TightVNC for remote desktop management. I have a
> few
> > > installation questions though:
> > >
> > > 1. Is it possible to deploy it (in service mode) to multiple machines
> > > remotely? I know that I can place the program file in a shared folder
> and
> > > send all users a message having them execute it, but to be honest, I
> don't
> > > really trust the users to do it.
> > >
> > > 2. Also, according to the documentation here
> > > (
http://www.tightvnc.com/winst.html), you can use the same password
> across
> > > multiple machines by copying a registry key. Does anyone know how to
> do
> > > this? I have had no experience with copying registry keys to other
> > machines.
> > > Also, can that be done remotely?
> > >
> > > If it is not possible to deploy it remotely, and I have to move to
> each
> > > machine to do it, is it at least possible to write a script that runs
> the
> > > installation command "tightvnc-1,2,9-setup.exe /sp- /verysilent"
> (this I
> > can
> > > do), then import that registry setting the article referenced above
> > > mentions, then perform a reboot (this I also know how to do) so that
> the
> > > service can go ahead and start?
> > >
> > > If I'm not making sense, please let me know, but I do appreciate any
> help.
> > > Thanks,
> > >
> > > Chris
> > >
> > >
> > >
> >
> >
>
>
>