You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Since updating, my Apple Remote Desktop 3.7 is not working properly.

Since updating to 3.7, my Apple Remote Desktop Admin is not working properly.

Prior to the update, everthing was working correctly.

Since the update, workstations are not showing up in the Scanner, some workstations are flickering between Available & Offline, others are showing as Access Denied. I have updated all of the clients to the appropriate ARD clients.


What is going on with this version?


Running OS X Server 10.7.5 on Mac Mini

Mac mini, OS X Server

Posted on Nov 3, 2013 5:22 AM

Reply
211 replies

Nov 10, 2013 9:18 AM in response to ZakAttack451

Zak, I have similar issues; status offline or --, yet I can still control them. With so many Macs in three locations, I'll take it. Hopefully, someone can build on this and add to it. Apple will eventually fix it, but folks like us on the front lines can't wait for them. I noticed that some of my Macs are showing up as .local and others as .domain.com which led me to try what I did. Hopefully, some of the other admins out there can take this and build on it and we can get through this.


I also noticed that two of my newly configured Macs didn't show up in Windows Active Directory and I had to unbind and rejoin the domain to make them work??? Can someone else check this on your domain?


Russ

Nov 12, 2013 7:35 AM in response to ZakAttack451

I, and all of my colleagues have the exact same issue. I think it's because when adding a client computer, ARD caches it's IP adress somewhere. Then, when it changes due to DHCP, the fun starts.


This used to happen in previous versions as well, but in a lesser form. You used to be able to just select the offending computer in the 'All computers' list, remove it, and you'd be able to control the client you wanted again.

Now when you remove the computer, it seems like the IP adress is still cached somewhere and solves nothing.


Other side effects are: Trying to observe one computer, and end up getting a completely different one in view;

Doing a search for an exact IP adress ***.***.*.10 and getting two results ending with .9 and .11, both of which aren't the ones you're looking for.

Computers viewed as offline, even though they're actually online as others have mentioned before...



As of right now, I'm mostly instructing users to go to system prefs and look up the actual IP adress for me so I can manually start a VNC connection..

Nov 12, 2013 9:24 AM in response to Tegenwind

Tegenwind wrote:


Other side effects are: Trying to observe one computer, and end up getting a completely different one in view;

Doing a search for an exact IP adress ***.***.*.10 and getting two results ending with .9 and .11, both of which aren't the ones you're looking for.

Computers viewed as offline, even though they're actually online as others have mentioned before...



I've seen all of these as well. I actually went in to control one machine yesterday, started quitting apps and realized it was not the machine I had selected. Very embarrassing. I've also seen multiple machines all listed with the same IP address (even though they are assigned static IP's), machines showing up in smart lists that don't match the smart list attributes and machines constantly showing offline or authenticating.

Nov 12, 2013 12:14 PM in response to ZakAttack451

I will chime in here. I have a classroom full of Imacs and had the same problem since upgrading. I called Apple support and here is what we did.


Opened user account ~Library~Containers~


Found the com.apple.RemoteDesktop folder and dragged it to the desktop.


Restarted Apple Remote, filled out the necessary "I agrees" and regular start up menus. Went into the scan mode and all of my Imacs showed up and it appears to be working.


He was perplexed with the flickering. I had five computers showing the same IP address. I would do a IP address search for a computer and it would bring up another computer.


Anyway, it appears to be working, but he told me to give it a few days to see if it continues to work. He told me NOT to delete the com.apple.RemoteDesktop folder that I dragged to the desktop. BTW- they are getting other cases of this being reported.


Good luck- Dude from Apple was very good. He stayed with me for about an hour as we troubled shooted.

Nov 13, 2013 4:14 AM in response to ZakAttack451

As above. ARD 3.7 on 10.8.5. Running on a MacBook Pro

Mix of 10.6 and 10.8 clients


ARD is exhibiting the same issues, flickering status, inconsistent IP addresses, unable to stay on the selected computer in the list.

Again, like everyone else, I depend on this to manage approx 55 Macs across two sites.


Can I ask, does removing the ARD preference folder mentioned above also remove all my saved actions and scripts?


Thx

S

Nov 13, 2013 7:02 AM in response to gamova

Nope. Same issue as everyone describes here with only 10.8.5 machines.


Edit: I should note that I can still manage the majority of my machines manually (some show up as offline or with self-assigned IPs at times) but any scheduled tasks I have set to run during downtime/over weekend always fail with authentication errors or communication timeouts. None of the machines are powered off at these times either. I also don't only use ARD on a server but my own client, which is now completely unavailable to the server ARD instance.

Since updating, my Apple Remote Desktop 3.7 is not working properly.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.