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

Honest, there's nothing you can do beyond what I said earlier. Look at the data, it's nonsense data in the plst

True, but the good thing is that if you put the files aside, remove the ARD Admin along with the ARD Client (core services), install the 3.6.2 Admin and 3.6.2 Client and have it read preferences that 3.7 has touched and also clean it.

I've not found any compatibility problems with the 3.7 enabled clients either so you don't have to bother downgrading them.

Remote Desktop has never worked well. But now it is almost worthless.

When scanning the network from my Mavericks computer I see 20% of the computers on the Network.

I guess if you use bleeding edge .0-products like OSX10.9 where you really need your tools you should start thinking about your strategy. That is what you should refer to as you test computer. ARD is a faboulus tool, nothing like it and has worked extremely well since what System 7.6? Sure some very small issues but no real problems. It's a setback at the moment but going back to 3.6 is a easy five minute job and since you don't loose any settings or templates and have full admin capability of 3.7 clients there's really nothing to think about.

Have you tried taking a 10.9 machine and using ARD Admin 3.6 on it? I was pretty sure i had to update to 3.7 because 3.6 would no longer work.I too enjoy ARD, and have been a daily user of it for over 10 years. Does anyone know if Admin 3.6 will work on a machine running 10.9?

Thanks.

No I haven't but the latest OS would never get near my admin-computer I depend on for living. The 3.6 admin is fully compatible with the 3.7 clients so it doesn't matter what clients do themself in terms of updates. Therefore it would just be a case for the test bed, but I can try later when I get home to them if you want to know.

all is working well after doing this:

- delete all entries in "all computers" in RemoteDesktop3 Software

in Terminal:

- chmod -R 777 ~/Library/Application\ Support/Remote\ Desktop/

- chmod 777 ~/Library/Preferences/com.apple.RemoteDesktop.plist.*

Works like a charm - UNTIL NOW...

The chmod commands are pointless.. ARD 3.7 is sandboxed, thus its Library is containerized. Those files you changed aren't used anymore

Deleting all entries in All Computers works for a while, bu eventually the host names will get messed up again. It's also not practical with 3200 computers

RobmanI just tested to remove ARD 3.7 on a 10.9 computer in my test bed and install 3.6.0 (ARD admin) and upgrade that to 3.6.1 and then install the 3.6.2 ARD client. It was all done via VPN [and ssh/ard]. Keyboard did not work at all under remote connection into the 10.9/ARD3.6-mac so I had to open the keyboard viewer. Mouse was fine but GUI was sweeping slow, exactly like an old 9600 baud terminal. I don't know if this just relate to my ARD session tapping into the 10.9/ARD3.6-mac or if that applies also to the computer at location. Most likely it affect just my remote session and it might even be fine after a restart of the computer. I just restarted the ARD client. I also successfully transfered all unix commands and all history into the old ARD admin and that came up as it should.

Using 10.8/ARD3.6 is beautiful even though the client is on ARD 3.7 but if you have 10.9 on your admin-mac and don't ever remote into that you might want to try a downgrade. Just make copies of your config files in the container folder and move them into the old positions. The ARD client folder in /System/Library/CoreServices along with the Remote Desktop.app is all I removed.

I installed this on OS X Server 10.8.5 which runs better than on my Mac 10.9... Nothing has changed for my system, still flashy, problems connecting, etc.. Maybe this patch just fixes 10.8.5 even though it says fixes 10.9 issues...

I installed it on my 10.8.5 Mac Pro AND my 10.9 Macbook Pro.

Previously I had to turn off the firewall on my Macbook Pro to allow my Mac Pro to see the screen.

Now I don't have to turn the Firewall off so that problem is fixed for me. I use ARD at home to save me walking up and down three or four floors and to connect from a work location to home so I haven't had the issues that many other far more professional users have experienced, so can't comment on the DNS issues.

But a cautious thumbs up (so far) from me.

Rob

I got the new 3.7.1 and i'm still seeing multiple machines have the same DNS entry when if i SSH onto the machine i can tell they do not. They are on different subnets, and nothing has changed with our DNS server..

If I look on a machine I set up running 10.8.5 and ARD 3.6.1 it looks fine, so it might just be a holdover form the All Computers list..

I just removed all my machines from All Computers and will re-populate it. Hopefully the DNS-entries sorts itself out..

my 2 cents so far...

No worries, just installed it in a test computer I had ready waiting for such upgrade. That computer was terrible on 3.7.0 so it's a great candidate. I'll report back in 10 h when the fleet is started [or later if seams fine at first]. All I can say so far is both admin and agent is now 3.7.1.