What is the OS on the client machines?  Also, are you using the aclient or dagent?

Good questions Stu. 

Jane,
If using XP or less, you need to use the ACLIENT agent.  If using Vista or above, you need to use the Dagent.  This is configured under the Remote Agent Installer.  There is a check box "Use AClient instead of DAgent on older OS computers (XP and 2003)".  If the DAgent is used on XP or 2003, there are several features that do not work, such as Remote Control.

Hope this helps.

Marco

Windows XP, sp.3
I am using aclient

Do the clients you can't remote control have anything in common? location? software? hardware? computer model?

Just curious, but do these computers have the xp firewall enabled?  If so, have you made exceptions for the AClient connection ports?

No....

I will check to see what is common among the ones that I am having trouble with.

Thanks/

Jane

Jane,
Sorry for the dumb question. 

Have you looked at this thread:
http://www.altirigos.com/vbulletin/ds-console-web-console/6817-problems-ahoy.html

They talk about the issue you are having

<QUOTE>
In the DS Console, click Tools -> Options. Select the Agent Settings tab and click the Change Default Settings button. Any changes here will apply to all new AClient installs.

As for the remote control waiting for client to accept connection problem, ensure that you don't have Prompt the user before performing actions Remote Control checked in the agent settings (on the Access tab).
</QUOTE>
.
.
.
<QUOTE>
Verify this in your aclient.inp

Code:

;---------------------------------------------------------------------
; UseRCDrivers - Specifies whether or not keyboard and mouse filter
; drivers are installed for remote control. If the
; drivers are not installed, you will not be able to
; use the Remote Control feature to log in to Windows
; NT and 2000 machines.
; optional ( Yes / No ) - Default - No
;---------------------------------------------------------------------
UseRCDrivers=No

;---------------------------------------------------------------------
; AllowRemoteControl - Specifies whether or not this computer can be
; remote controlled
;---------------------------------------------------------------------
AllowRemoteControl=Yes  <-----Verify Setting

;BlockedDaysSun=FALSE
;BlockedDaysMon=FALSE
;BlockedDaysTue=FALSE
;BlockedDaysWed=FALSE
;BlockedDaysThu=FALSE
;BlockedDaysFri=FALSE
;BlockedDaysSat=FALSE
;ScheduledBlockStart=8:00
;ScheduledBlockEnd=18:00

I am assuming the client is XP not 2k.
</QUOTE>

Hope This Helps.

Marco

I don't have 'prompt the user' checked.

I reviewed that article but don't think it pertains that much to this version of DS.

When I went back to try again, just like with the car mechanic, the one I was having trouble with is working fine. I did try another one that we have had trouble with and i still couldn't remote control, but I did discover that it has 6.1 version of aclient. I uninstalled it from the console but when I tried to install the newer one from the console I got some kind of a network error.

: (

Jane

Try running through article 4214 on kb.altiris.com. Alot of the times that when the client request the remote control session from the engine, the engine is busy processing some other jobs/requests/sql data and doesnt have the resources to do the remote control. So when you went back to it the engine was in a state where it could. Running 4214 will help fine tune the engine and client performance.

Jane, has the problem been solved? Let us know if you've gotten it to work for you.

1. Sometimes the Deployment Console doesn't have the correct status of a computer so you can't remote. right click computer click advanced and click reset connection. When it turns blue again try it.

2. Sometimes I have to go to Tools, Options Global and change the remote primary port to another number like 5001,5002, 5003 etc. Apply and OK.   Not sure why this works.

3. Found a couple no matter what you did they wouldn't remote. Their database was bad. I had to delete them and rename them. Weird but true.

4. If alot or all cannot be remoted then reboot the server cause microsoft updates messes up servers something fearse.

Hope one of these helps.............

i have the same Problem with the Remote Controll, change the remote primary Port und now it works again.

Thank you. :))

It's probably your network firewall in some of these cases. Most have an idle timeout feature to clean up what it believes to be "stale" connections. This can make aclients look inactive or make them stop working. You can increase this timeout on the firewall or look into using keep alive packets.

http://www.symantec.com/business/support/index?page=content&id=HOWTO10570

I read that article and it sounds like a great idea. It mentions pushing the .reg file to clients. I can't figure out how to do that. I just have Deployment Solution and tried running a script without success.

Thanks. 

Jane