Status Not Working in 3.3

Question

Level 1

10 points

Status Not Working in 3.3

I am having a major issue after the update. The computers in the ARD lists show no current status, user or application, and have a dark gray screen icon instead of blue. I am an Administrator user. I still had the same symptom with the security setting on "Full Access To All Features" which I tried despite being an Administrator user. I cannot do anything but screen share, as the other functions require checking the status.

Anyone solve this issue?

Mac Book Pro (Early 2008), Mac OS X (10.5.8), 4GB RAM

Posted on Aug 24, 2009 9:44 AM

Reply

Answer 1

rauschelbach Author

Level 1

10 points

Aug 24, 2009 12:02 PM in response to rauschelbach

Additionally, I can telnet to port 3283 to all computers that should be showing a status.

Reply

Answer 2

zair

Level 1

0 points

Aug 24, 2009 12:56 PM in response to rauschelbach

I had the same issue. Installed last Friday had the same issues as you. This morning as I was going through my Monday morning routines everything came back. It seems like it took a really long time to authenticate again after the update. Everything is back to normal now. I would just give it some time or if you really need it re-install.

Reply

Answer 3

rauschelbach Author

Level 1

10 points

Aug 24, 2009 5:24 PM in response to zair

Thanks, but I did the update on Friday as well. Still no change. I have updated other admin machines without problem now, but none with as large/various a list as my main computer. Since there isn't a way to backup tasks or multiple lists in one go, I'm going to try re-installing. I'll update shortly.

Reply

Answer 4

rauschelbach Author

Level 1

10 points

Aug 24, 2009 6:03 PM in response to rauschelbach

OK. A straight reinstall didn't work. Still no status. Also, I can't quit ARDAgent in order to backup my settings. The copy of /var/db/Remote Management hangs (and locks up the Finder). Apparently it can't get access to the RMDB.sqlite3 file.

Reply

Answer 5

rauschelbach Author

Level 1

10 points

Aug 25, 2009 11:39 AM in response to rauschelbach

Well, this morning it is working. Literally nothing was done between it not working yesterday evening, and it suddenly showing the status this morning. I guess with large lists (>850 computers in my "All Computers" list), there is some process for upgrading the database. I'm not sure why this could possibly need to be as long as four days, but I'm very glad it's working now.

Reply

Answer 6

QACI

Level 1

0 points

Aug 31, 2009 7:17 PM in response to rauschelbach

I am having the same issue. I have updates to 3.3 and if i ditch the plist file in my library it will work once. Then if i clae it down and re-open it only shows status but they all say either screen sharing available or authenticating.

Any help would be great

Reply

Answer 7

edb007

Level 1

4 points

Sep 3, 2009 8:10 AM in response to rauschelbach

Same issue. Even when connected it shows "offline" in status and shows old version Remote Desktop and system. Anyone have a solution or even a cause.

Reply

Answer 8

Sep 15, 2009 12:32 PM in response to edb007

same issue here, would love an answer!!

Reply

Answer 9

rauschelbach Author

Level 1

10 points

Sep 15, 2009 12:52 PM in response to nickatbarbarian

- How many computers are in your "All Computers" list?
- How many days has it been since you upgraded to ARD 3.3?
For me, with over 800 computers in my All Computers list, it took nearly four days for whatever is happening to work itself out, then everything was fine. I recommend just leaving ARD open, and waiting. Hopefully Apple will correct this frustrating problem soon.

Reply

Answer 10

Sep 15, 2009 12:57 PM in response to rauschelbach

80 computers, had the update since the day it came out, all clients are still grey, can't send files, get reports, but i can control/observe clients fine. so weird!

Reply

Answer 11

rauschelbach Author

Level 1

10 points

Sep 15, 2009 12:59 PM in response to nickatbarbarian

Has ARD been running the whole time? I had to leave it open.

Reply

Answer 12

Sep 15, 2009 12:59 PM in response to rauschelbach

nah, but i will try that now, thanks for the tip!

Reply

Answer 13

Sep 21, 2009 10:42 AM in response to rauschelbach

still nothing. this is crazy annoying.

Reply

Answer 14

Sep 21, 2009 12:40 PM in response to nickatbarbarian

Ok so I was having this issue with my some of my servers. One in particular was throwing an authentication error even though I had reset my passwd. This is a G5 cluster node box, so I had no graphics card to revert to, so it was either ARD or CLI.

What I ended up doing was going to /var/db/RemoteManagement inside of which was a directory called caches. The contents of caches included:

drwxr-xr-x 9 daemon daemon 306 Sep 21 00:08 .
drwxr-xr-x 3 root wheel 102 Dec 29 2004 ..
-rw------- 1 root daemon 30751 Sep 21 10:47 AppUsage.plist
-rw------- 1 root daemon 30751 Sep 21 00:00 AppUsage.tmp
-rw------- 1 root daemon 1617 Aug 23 07:04 UserAcct.plist
-rw------- 1 root daemon 1918 Sep 21 00:00 UserAcct.tmp
-rw------- 1 root daemon 409 Sep 21 00:00 asp.cache
-rw------- 1 root wheel 19196576 Sep 21 00:08 filesystem.cache
-rw------- 1 root daemon 2250 Sep 21 00:00 sysinfo.cache

So just to see these would re-spawn if I moved them, I moved the caches directory to root's home directory.

First I stopped the ARD agent:

sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -agent -stop

sudo mv caches /var/root/

Then restarted ARD:

sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -agent -restart

For good measure, I made sure that all the local accounts had access privs:

sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -configure -allowAccessFor -allUsers -privs -all

Then I tried to open and ARD session and all was good.

Interestingly enough, at this point the /var/db/RemoteManagement/ directory is still empty. The caches sub and its contents have not regenerated.

Message was edited by: rsnyderpsu

Message was edited by: rsnyderpsu

Reply

Answer 15

5thwall

Level 1

20 points

Sep 22, 2009 10:11 AM in response to rauschelbach

I'm in the same boat. I have 5 computers in my setup. 1, a Mac Pro 8-core, has never been able to achieve "current status" in ARD. I tried the method above and nothing worked.

Then, while working remotely last night, another Mac Pro 4-core lost it's current status.

Another on the Mac Pro 8-core is that sometimes I completely lose the ability to log in remotely, so to circumvent, I'll log in to another computer, run ARD and then log out the user on the Mac Pro 8-core. Only then can I log in with ARD.

Also, I am unable to remotely manage either of these computers. The other three, knock on wood, are still working.

The interesting thing is that, within the network, through bonjour I suppose, I can manage and see the status for all the computers. Everything works in the office.

Reply