Offering Remote Desktop Assitance

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am currently working on setting up the ability to offer Remote Desktop Assistance to PC's within our domain. I currently dictate through Group Policy Disable solicitation of Remote Assitance and Enabled Offering Remote Assistance for a specified Domain Security Group. The issue I am currently having is that I can resolve the host name and am able to pick which user to help, but after I click on Start Remote Assistance I get the following error message: A Program could not start. Please Try again. I have verified that the group policy is up to date. The only thing I can think of right now is that I have NetMeeting Desktop Sharing set to disabled. Does Remote Assistance rely on this netmeeting service? What services does Remote Assitance depend on? I have also strengthened the OS's security settings. Our Domain is currently running a mix of Windows 200 Servers and Windows 2003 servers as Domain Controllers. Any ideas?
 
My recollection is that you need to enable a remote-assistance related
property that you might think shouldn't be enabled, to be locked down the
way you wish.
Maybe it is the solicitation object, but that isn't ringing a bell.
Take a look at what you have disabled with regard to Remote Asstance.
 
Bill

Thanks for the reply. I enabled the ability to solicit a RDC. That seemed to do the trick. My question now is why does the offering of Remote Assistance depend on the ability to solicit Remote Assistance? Anyone from MS care to answer this? I think that it would be more secure to make these independent of each other. Is this behavior going to be changed in Windows XP SP 2? Is there a registry hack to get around this? Any detailed information on this would be greatly appreciated

Thanks for the help.
 
In XPSP1 and XP, offer remote assistance depends on solicted remote
assistance, there is no way to get around this and this will change in
XPSP2.

--
This posting is provided "AS IS" with no warranties, and confers no rights.



Ken Gosnell said:
Bill,

Thanks for the reply. I enabled the ability to solicit a RDC. That
Click to expand...
seemed to do the trick. My question now is why does the offering of Remote
Assistance depend on the ability to solicit Remote Assistance? Anyone from
MS care to answer this? I think that it would be more secure to make these
independent of each other. Is this behavior going to be changed in Windows
XP SP 2? Is there a registry hack to get around this? Any detailed
information on this would be greatly appreciated.
 
Excellent news--any guideance as to a testing script that might let someone
with SP2 see what is different?

Email welcome--just remove .plugh.org
 
I would also be interested in any more information on the
remote assistance change in SP2 - this could be crucial
to the XP SOE we are currently devloping for a large
client base.

regards,

Nick
 
Try taking a look at
http://www.microsoft.com/downloads/...c0-19b9-4acc-b5be-9b7dab13108e&displaylang=en
for more information (this is an Excel Worksheet of the new GP changes
in XP SP2).

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top