Permissions Repair Error: ARDAgent.app

As I indicated in previous posts, I repaired permissions many times in Terminal. I didn't perform the ls -al on the file itself, and I thank you for the heads-up.

I had serious slow down troubles, in MacOSX and in Ubuntu 7.10 that I was running under Parallels 3.0/build 5160 (I am now responding to your post from Firefox in Ubuntu).

Since I "regressed" to ARDAgent.app 2.1, the computer, both in OSX and in Windows XP Pro, or Ubuntu 7.10 under Parallels works fine (let's not jinx it...).

I suppose Apple-tech people are getting their....wits together, and working on a solution. I'm not concerned with Remote Desktop per se, because I don't use it, but it's unacceptable and risky to run the Mac with a file that has been deprecated by Apple.

Thanks for your feedback.

The permissions of the file should be -rwsr-xr-x, which in most cases they still are.
Check in terminal :-
cd /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS
ls -altr

It should return the below:-

-rwsr-xr-x 1 root wheel 1463076 17 Oct 18:50 ARDAgent
drwxr-xr-x 9 root wheel 306 5 Nov 10:52 ..
drwxr-xr-x 3 root wheel 102 5 Nov 10:52 .

If not:-

sudo chmod 4755 ARDAgent

Hope I don't get to many "I already knew that" comments, I am just trying to help 🙂

Hi loose_cannon26, that's what I get on the Powerbook PPC where ARDAgent.app version 3.2.1 is installed (allowing for time zone differences).

On the Macbook Intel Core 2 Duo, where I have "regressed" to version 3.2 (the one originally installed by Leopard's install DVD), I get exactly the same permissions, allowing for different dates of course.

I didn't know that, and I thank you for your help.

If the permissions are the same for both files, why does Disk Utility (or diskutil in Terminal) balks at the updated file (version 3.2.1)?

The 3.2.1 update is still available by Software Update, Apple has not changed it. The link in the update's blurb <http://docs.info.apple.com/article.html?artnum=306490> indicate that "...provides two update packages: Apple Remote Desktop 3.2.1 Client. and Apple Remote Desktop 3.2 Admin. These updates can be downloaded from Apple downloads" .
At Apple Downloads, Remote Desktop 3 is offer at prices between $ 499.00 (Unlimited Managed Systems Edition Administrator) and $ 299.00 (10 Managed Systems Edition Administrator).

So what's this? I haven't bought any of the above. What do I need the whole RemoteManagement folder in CoreServices for?

Or does the basic MacOS X installs a "free copy" of the software?

Someone mentioned a Remote Desktop Preference Panel in System Preferences. I have no such thing.

Why doesn't Apple come with a clear statement about Remote Desktop?

It would seem that, after all, this is really a non-issue, and that the best thing would be to delete the whole RemoteManagement folder, unless you have bought and install the original software?

hi Charly,

remote management check box in system preferences > sharing is what turns it on/off.

Correct me if I'm wrong but:
I guess if you don't have the $299/$499 Apple Remote Desktop 3.2 host software then remote desktop is not much use.

It does seem like RM is tied into some other functions as well though.

If you are still having complications, you might try a reinstall.

Hi KJK555,
Remote Management in System Preferences>Sharing. Box is not checked.
I don't have the $299/$499 Apple Remote Desktop 3.2 host software, never bought it.
For the time being, I have removed the whole RemoteManagement folder from CoreServices, restarted, run Software Update. No update available, so no Remote Management update is required, makes sense?
Ran Repair Permissions in Disk Utility, and in Terminal. No warnings, but it still takes a lot of time. Well that's a subjective statement.
Maybe I should have dumped the 'Receipt' for the update, from '/Library/Receipts' too?
So far so good.

..." If the permissions are the same for both files, why does Disk Utility (or diskutil in Terminal) balks at the updated file (version 3.2.1)?"...

There's a very good reason why permissions on SUID files shouldn't be "fixed" if a file has apparently been tampered with. Everyone has heard of MOAB #15, surely.

Recall that "repair permissions" uses information in "/Library/Receipts". The .bom files (and their newer equivalents) have always contained checksum information for the installed files, and really, Apple should have been making use of that information from the beginning.

So Apple is trying to make OS X more secure, but there are still some kinks in the system. ARDAgent has been updated (the "Remote Desktop Client" update), but "repair permissions" doesn't know to use the new checksum so the new file and old checksum don't match. It doesn't matter if the permissions are correct - the checksums don't match, and "repair permissions" is flagging that. If everything was working correctly and you got that message, it would be a warning that the file has become corrupted, or worse, that someone or something is trying to hack your system.

I can't believe some of the comments around here -- Delete ARDAgent.app... where's that bottle of clue musk?

Hi Charly:

My copy of leopard is running okay now. Disk utility is still a little slower than Tiger's. permission repair/check takes about 5 min. Disk check takes about 4 min. I Haven't seen any errors in disk utility for a few days now. Leopard runs 10-15 hours per day. I've had a few progams I had to force quit or back out of. They just simply are not compatible with Leopard.

Most of the programs I need to do work are okay or have been fixed with an update.

It'll probably be a couple of months before the majority of programs get their code working right.

There are a couple of things I find annoying in Leopard and they are the ugly folders and the firewall settings need to be a lot more customizable.

Hi KJK555,
Thanks for the feedback.
I agree on the issue of programs that still need to be updated to be compatible with Leopard, the only ones I'm stil missing are SuperDuper! and DiskWarrior.

About Repair Permissions requiring about 4 minutes, are you running Leopard with the much discussed ARDAagent.app 3.2.1?

HI Charly

No I am running RMC 3.2 that comes with Leopard. I removed RMC 3.2.1 because of ACL problems and other strange stuff that kept popping up.

At first I just uninstalled the entire RMC 3.2.1 app altogether. The strange stuff stopped and everything stabilized. I was still having problems getting Parallels (build 4128 v3.0) to start. After I got it started though (about 3-5 tries) it ran okay and didn't crash anymore like it it did with RMC 3.2.1 installed. ACL problems disappeared and other random miscellaneous permission problems. Most of the other apps began to behave as well.

I reinstalled RMC 3.2 off the Leopard DVD and Parallels began operating flawlessly as did some the other apps that were a bit choppy. The only apps that are misbehaving now are those that are known to be incompatible with Leopard.

Disk Warrior will repair a leopard partition, but must be run under tiger or booted from the Disk Warrior CD. *DO NOT* use it to repair permissions on a leopard partition.

I don't use Super Duper! I use Carbon Copy Cloner instead. It also appears to be partially broken under Leopard (won't do image backup). It does work under Tiger to backup the Leopard partition to images. I haven't used time machine yet. I need some additional hardware first. I am going to use an external SATA drive. The Mac Pro will support two additional SATA external drives with a $24. internal to external adapter. I have 5 PATA drives I need to unload on ebay first though.

Hi KJK555 (I feel somewhat silly to call you KJK555, but I respect your privacy)

I had also replaced ARDAagent.app 3.2.1 with 3.2 that I had "Pacified" from Leopard's installation DVD, but every time I ran Software Update, I was presented with the update to 3.2.1, which I declined. To end the routine, I decide to take out the whole RemoteManagement folder from /System/Libray/CoreServices. I don't use Remote Desktop, I haven't purchased it, therefore I don't see the need to have my system include a Remote Desktop client-software. Although I feel a bit uneasy to have removed something from CoreServices.
While I was running the updated version 3.2.1, the laptop went to heck, and barely made it back. It seemed to operate in a bathtub full of molasses.

Parallels, where I had installed a legit copy of Windows XQ Pro (with SP2), and Linux Ubuntu 7.20, was almost inaccessible. I don't try to run, at the same, MacOSX and Windows and Ubuntu which I could do if I had a much larger HD and double the RAM. In retrospect, I regret I didn't purchase the Macbook with a larger HD

The moment I went back to version 3.2, everything went back to a very fine performance.

By the way, I am not using any more Parallels Build 4128, but 5160 which is stable, and totally compatible with Leopard. You can download it, if you are interested, from <http://www.parallels.com/en/download/desktop/> scroll down to the 5160 link.

I am well aware of the limitations of the current DW version, and know I should run it from an external HD running Tiger. But I prefer to wait for Alsoft's update, that will enable registered users to burn an updated CD. My experience with running DW from an external HD, and not from the CD itself, has taught me that the results could be unexpected and sometimes very risky.

I know about CCC, but I'll wait for an updated release of SuperDuper! that has never disappointed me.

I have a Leopard-updated working copy of Déja Vu, which comes as a part of Roxio's Toast Titanium. I made a test to back up the contents of the Powerbook PPC where Leopard is also running (with ARDAgent.app 3.2.1), it took hours to complete, but the resulting backup was not bootable, in spite of the fact that I had followed all the instructions to create a bootable back. So much for Déjà Vu.

Thanks for your feedback.
Charly

Hi Charly

You can call me Ray if you like.

Thanks for the parallels link, but I am running 4128 because I am running two commercial programs I use for business that have sensitive anti-piracy solutions on them that cripple the software with the slightest change of hardware or OS software. Two previous parallels upgrades have already disabled it twice and it takes 2-3 days to get the new codes to re-enable it again.

Anyway 4128 is running flawlessly so far so "if it ain't broke, don't fix it!"

For my disk warrior and other utilities, I created a small 17 Gb Tiger partition using ipartition 3.0. on a second internal drive. I stripped it to a bare bones install. It took only about 2.5GB. Then I adjusted the partition back to 8GB again with ipartition. The new ipartition 3.0 rocks! Now I run my Carbon Copy Cloner from Tiger again.

Of course you can produce a working backup image from Apple's disk utility as well. Just use your install disk to boot and run disk utility and save the image to the internal or external drive of choice. That's what I used for quite some time. I just recently started using CCC.

Here's a little tip: If you are not booting from startup disks to do a backup, always start in safe mode before backing up to an image file.

Ok Ray,

Definitely, if your current Parallels build satisfies you, no need to change, on the contrary.
Good idea of creating a small Tiger HD where from DW can be run. I have an external FW HD that I bought some time ago. It has become too small for backups, but it would suit perfectly for running DW and, in my case, SuperDuper! under Tiger.
Thanks for the tip about starting in safe mode.
Charly

I don't know if this is related to my issue with Leopard and permissions but here goes anyway....

Does anyone know why my MacPro has suddenly locked me out of certain Apple applications?
When I try and launch iMovie I get the following:

"The project could not be opened, because the disk is full, the folder is locked, or the folder permission are incorrect."

My disk isn't full, nor does it say my folder is locked.

Leopard also won't let me edit my Address Book and stops me moving certain files into folders as well as failing to complete Quicktime Sharing commands.
I've tried repairing permissions using Disk Utility but it's having none of it. Even Disk Warrior 4 (running from start-up disk) doesn't seem to correct things.
My Accounts/Admin permsions seem to be really buggered.

Any help or advice would be greatly appreciated. Ta.

Hi Uncle,
I have checked permissions for iMovie, Address Book, they both show 'System Read&Write', 'Administrator Read&Write', 'Everybody Else ReadOnly'. I'm not having the problems you indicate. Repair permissions is still in the same sorry state as previously reported with the 'SUID...blah-blah...'. a hundred of so items that will not be repaired, and still takes 10 minutes or so to complete, and I still don't know whether Disk Utility has repaired anything.
About iMovie HD, specifically, do you know whether it is trying, upon launch, to open some project you started, or a video clip or video file that you have previously viewed with iMovie HD? That file, if there is such a file, might be locked, or its permissions incorrect?
I guess it's useless to keep on commenting why Apple hasn't done anything, yet, to remedy the Repair Permissions issue, if Apple considers it an issue? All this is confusing and frustrating, I have the impression to be a Windows user.

Hi Charly, the warning from iMovie pops up when I try to open a new project as well as on existing movie files.

Address Book says that I've ('Me') got Read & Write privileges and lists 'system' and 'admin' as also having Read & Write privileges. I was under the impression that I was the administrator???

Thanks anyway.