DS 6.9 SP3 not showing Logged in user
Updated: 18 Sep 2010 | 10 comments
We have recently upgraded our Deployment Solution to 6.9 SP3 from 6.8 SP2. Since the upgrade we have lost the visibility of the logged on user from within the console. All PCs just show as turned on or off and not showing the little head image if someone is logged in.
Is there an agent setting that has changed? I have found on another forum somewhere that it will only work if the Terminal Services service is started, however we cannot have this service enabled on the desktops. Is there another workaround for this?
Many Thanks
discussion Filed Under:
Group Ownership:
Comments
6.9 build635 SP1-Sporatic machines-not showing logged in user
Some computers at a site are not showing that a user is logged on or they are showing an active computer that is not active if DS Remote is attempted.
The computers have been rebooted but still do not show that a user is logged on.
All services are running. running the KB 4214 vbs does not show any problems. The deployment server had this problem yesterday, was rebooted last night, but is still having the problem. What is the next thing to check?
6.9 (365) SP1, AClient 6.00.2399
A couple of items
1. The DS and AClient/DAgent need to be the same version to prevent problems.
2. Are you using AClient exclusively? If so, you will want to make sure that AClntUsr.exe is running and an exception in the firewall. This is what is used to pass the logged in user information and computer state back to the DS console.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Thank you for update. Yes we
Thank you for update. Yes we use Aclient exclusively. I will ask the firewall tech to verify that AClntUse.exe is an exception in the firewall, but we have 5000 machines and this problem has just surfaced. Other computers at the same location are reporting properly about logged on users and about active computers.
I reported our version of
I reported our version of AClient incorrectly. The client version is 6.9.366 (x86)
Firewall
Generally, the firewall exception I was referring to has to do with the Windows Firewall and not so much to do with the corporate firewall.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Yes, firewall has AclntUser in exceptions
Thank you for the clarification. Yes, there is an exception for AclntUser
AClntUsr
Can you verify that this is a running process on the afflicted machine?
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Aclients
Are all of your Aclients up to date I had this problem when we upgraded because some of the clients did not get upgraded.They were off when we pushed the job and then the job was deleted before all clients had updated.
I've got the same problem. I
I've got the same problem. I just posted my events from the server because just last week i was able to see the computers and control them. Now i can see them but can't control them. I've heard on the forum that this is a known issue and everyone is waiting for the next release. I did the upgrade in january same aclient version and deployment version.
Had the same problem....
We had the same problem once we started to REALLY lock down our network. Make sure that Terminal Services are running on the clients. This was our problem.
Would you like to reply?
Login or Register to post your comment.