Remote Assistance

Hi,

Windows XP Pro SP1a

We have a situation whereby we wish to offer remote assistance to machines
in two different domains, one NT4 type domain and the other Active Directory
(AD).

The helpdesk staff are located in the AD domain as are their machines. When
we use 'offer remote assistance' to other machines that reside in the AD
domain (logged on users also in AD domain) we are able to without any
problems. The GPO is used to configure the permissions allowing certain
users i.e. 'AD\helpdesk group' the rights to carry out these tasks.

The other machines, that are located in the NT4 domain, with users that are
also in the NT4 domain (same PC image). We have configured the local policy
as stated in http://support.microsoft.com/default.aspx?kbid=301527 (and
direct through custom adm and registry editting). The same group i.e.
'AD\helpdesk group' is listed as those that are allowed to offer remote
assistance (have also tried local admins of which 'ad\helpdesk group' is a
member. However in this scenario after you click the 'Start Remote
Assistance' button the usual logon screen appears, instead of automatically
logging on with the 'Helpassistant' account. If i enter my details it
tellsme that userx is currently logged on and will be logged off. I end up
with the same as using normal remote control (mstsc).


just to summise: we can offer remote assistance to workstations that are in
the same domain as the helpdesk staff, but can't offer remote assistance to
those machines that are in a different domain. Is this a limitation of the
offer remote assistance scenario.

Hope that someone can clarify this is as designed, should it work, what may
i be doing wrong or any other such pointers

Thanks

Mark

http://support.microsoft.com/default...;EN-US;Q306045

there was an old nt4 policy sitting around set to 'do not display last
logged on user' turned this off and now appears ok

"mark" wrote:

Hi,

Windows XP Pro SP1a

We have a situation whereby we wish to offer remote assistance to machines
in two different domains, one NT4 type domain and the other Active Directory
(AD).

The helpdesk staff are located in the AD domain as are their machines. When
we use 'offer remote assistance' to other machines that reside in the AD
domain (logged on users also in AD domain) we are able to without any
problems. The GPO is used to configure the permissions allowing certain
users i.e. 'AD\helpdesk group' the rights to carry out these tasks.

The other machines, that are located in the NT4 domain, with users that are
also in the NT4 domain (same PC image). We have configured the local policy
as stated in http://support.microsoft.com/default.aspx?kbid=301527 (and
direct through custom adm and registry editting). The same group i.e.
'AD\helpdesk group' is listed as those that are allowed to offer remote
assistance (have also tried local admins of which 'ad\helpdesk group' is a
member. However in this scenario after you click the 'Start Remote
Assistance' button the usual logon screen appears, instead of automatically
logging on with the 'Helpassistant' account. If i enter my details it
tellsme that userx is currently logged on and will be logged off. I end up
with the same as using normal remote control (mstsc).


just to summise: we can offer remote assistance to workstations that are in
the same domain as the helpdesk staff, but can't offer remote assistance to
those machines that are in a different domain. Is this a limitation of the
offer remote assistance scenario.

Hope that someone can clarify this is as designed, should it work, what may
i be doing wrong or any other such pointers

Thanks

Mark