Re: Offer Remote Assistance Not Requesting Permission

From: Shenan Stanley (news_helper_at_hushmail.com)
Date: 03/31/04 

Date: Wed, 31 Mar 2004 05:18:59 -0600

Simon Purdue wrote:
> Thanks guys for your replies.
>
> The Offer Remote Assistance is only really intended for companies who
> want to be able to take remote control of an end user's desktop.
> It's this that I want to do.
>
> From the MS documentation, you set the Offer Remote Assistance only
> from a Domain Controller's Group Policy or by setting it manually on
> the novices PC using GPEDIT.MSC.
>
> Bill, you're right in saying that both machines must be in a domain or
> across domains where each domain trusts each other. Both machines
> are a member of the same domain. By the way, I'm editing the Default
> Domain Policy and changing the setting Computer
> Configuration\Administrative Templates\System\Remote Assistance.

I believe that Robert's confusion came from your first paragraph of your
original post.

<..snip..>
> I'm looking to implement the Offer Remote Assistance feature of
> Windows XP on our company domain and have hit a problem with the
> novice's computer not displaying the dialog window asking if they
> want to allow the expert to connect. All that happens is that the
> expert's computer shows a logon dialog window in the Remote
> Assistance window. If I logon using my admin account, it locks the
> novice's computer and I have control. However, I have also seen it
> log the novice user off their machine as well.
<..snip..>

While it is strange that you sometimes don't get a dialog window on the
client asking them if they want to allow the expert to connect when you
offer remote assistance, the latter part of the paragraph implies you then
choose to log in as an administrator and that can log the novice user off.

Well, as far as my experience with remote assistance, you either have the
client user accept your offer for help or you don't when you offer Remote
Assistance. The only way I know of that you can then continue and log on as
an administrator is to not offer remote assistance but to use remote
desktop. And when you use remote desktop, unless you log in as the user in
question, you DO log off that user. Also, with remote desktop, even if you
log in as the user in question, it will lock the screen and they cannot SEE
what you are doing.

I believe that may be what Robert was referring to earlier.

Now, as for your problem, have you looked at the resultant set of policies
on the machines giving you this trouble? Is it always the same machines or
is it user related? 

-- 
<- Shenan ->
--

Relevant Pages

  • Offer Remote Assistance Not Requesting Permission
    ... I'm looking to implement the Offer Remote Assistance feature of Windows XP ... on our company domain and have hit a problem with the novice's computer not ... dialog window in the Remote Assistance window. ... I've run the Resultant Set of Policies over my machine and the novice's ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: XP Home Remote Access and Virus Infection
    ... Rpdude typed: ... > Yes, remote assistance from one XP home machine to another, exactly. ... > my window to theirs. ...
    (microsoft.public.windowsxp.general)
  • Re: Offer Remote Assistance Not Requesting Permission
    ... I understand why you think this, but the "offer remote assistance" feature ... The novice end machines must probably also be joined to the domain, ... >> dialog window in the Remote Assistance window. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: rdesktop woes [SOLVED]
    ... Remote Desktop and Remote Assistance on both my XP Home and my XP Pro ... machines. ...
    (Fedora)
  • Re: rdesktop woes
    ... the user must also be a member of the remote desktop ... Windows XP Firewall on all 3 machines have checkboxes for both ... Remote Desktop and Remote Assistance on both my XP Home and my XP Pro ... set up on my XP Pro machine, just so I can see rdesktop work.... ...
    (Fedora)
Loading