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

@bobgeo,

I just re-imaged my iMac lab today- 35 Macs. Brought ARD 3.7.1 back in from a back up and all machines came back in Bonjour except one, but brought it back with IP. I will give it a few days and post back.

Jesus, updated image and deployed...zero screen interaction now. Everything else works. Fan-tastic!

No, 10.9.2 did not fix it.

Apple will need to release an ARD Admin 3.7.2 to fix this. Hopefully that'll be soon.

Would you be willing to share your Automator app with those of us who are barely even understanding what is being said here, but need / would like a fix to be able to run their classroom more effieciently?

bash script works for me, just download it from github and decompress it and you will have a ARDFixer.command, you'll need to make it an executable (check link) and double click it

http://apple.stackexchange.com/questions/80704/how-to-run-a-bash-script-from-the -desktop

http://www.hackmac.org/articles/bash/bash-101-hello-world-and-a-little-further/

Amen, ZakAttack is perfectly correct!

Please stop saying everything works because it will break sooner than later and you will not be here to correct yourself.

The only thing which works is to keep admin at 3.6.x which require 10.8 (or older) and naturally that old compatible computer.

The ARD Administration application is still not working well, but that Script does help me immensly. I run it 1 or 2 times a week, takes only 15 seconds or less, and at least gives me workable Administration. I should figure out how to turn it into a nightly script.

But again, thanks for the script, it's really helping..

Same here. Until Apple fixes ARD, I'm getting great mileage out of the script provided here. Big thanks for that.

Keep in mind that the ARDFixer script I posted must be run at least as often as your DHCP lease time. If you are unlucky enough to have a 24 hour DHCP lease time you're going to need to run ARD Fixer daily.

We have a 14 day DHCP lease time, so I run it every weekend and it gets me through the next week.

ARD 3.7 doesn't even work in a static network so DHCP and lease time has little to do with it unless you have one really simple network you might be successful running it over and over. ARD becomes really confused if you have different networks and totally mayhem if you have two sets of clients and they have the same subnet. Consultants who help different companies usually have those lists. The only way to SOLVE IT until Apple get a grip is to keep that old computer which is compatible with OSX 10.8 and ARD 3.6.

irob, that's basically the same problem as a short DHCP lease time.

When you have clients with the same subnet you're going to get different computers with identical IP addresses that - that's no different that two computers getting each others DHCP address a week later because of short lease times.

Because ARD is caching ALL this historical IP/dns info, it gets badly confused in these situations.

The only "solution" I've found is the ARD Fixer script I posted, since it clears out all the cached DNS/IP info, it forces ARD to refresh its info when scanning the current network

It's by no means perfect, but it does allow ARD to work for me in our environment

Yes, that's perfectly true and it's great you have shared the script, but it's not a solution that sticks like one can believe when reading this thread. The only solution which is a permanent cure is to stay with ARD 3.6 (and OSX 10.8).

Apple has to address the broken software which is essential for every IT rep'. It's terrible it's been unattended for such a long time and the whole situation sais quite a lot about their attitude to administrators.

Never said it "sticks" - you could move to Mavericks and ARD Admin 3.7 and simply use the script every day, but you certainly don't have to, you can stay on Mountain Lion and ARD Admin 3.6, that's a perfectly reasonable choice.

For me it the inconvenience of running the script regularly was a reasonable price-to-pay to be able to move to Mavericks. Everyone needs to make their own decision regarding that.

I agree, that the state of ARD in general is unfortunate, but I'm not sure it really says anything new - Apple has never really put that much focus on IT needs. 😟

On the other hand, I'm not sure I'd want them to put too much attention on ARD and change it too much! I could easily see them "improving" things so that it's be much less useful for us. One example: our organization has very well developed set of unix, copy and install tasks that are posted to central server and rsynced regularly to techs, so we can do things like this:

I actually fear the day that we can't easily externally edit the unix/copy/install task plist files. So beyond just not breaking ARD, I'm not sure I want them to try and change it too much 🙂

I do pretty much the same things w/o Munki so you could say I've got everything you have along with the Munki part in the templates, so it's easily the most precious data in my computer. I totally understand you are worried the distribution breaks because It's a hazzle to recover if the preference file gets broken. Having to address that must be a pain.

I'm self employed so I can rely on the old history of the time machine and don't care much if they change it as long as I can manage my templates in ARD ;-)

Though, it would be nice with a more sofisticated "edit template window". A plain "Save" to update a template is a real blunder as is the lack of managing subfolders. The tiny window which doesn't scale is also really annoying. My list of templates is so long but I don't have the energy to manage them in subfolders as I constantly improve them. I'd do it if I could update them easily. Nice to see you did that. When I work with teams I often put the scripts I use on a wiki.