To uninstall Remote Desktop Client completely from your system follow this path: System/Library/CoreServices/RemoteManagement, select this folder, right click and select 'Move to Trash', you will then be asked for your Password.
Agent.exe is a file that is associated with one or all of three programs: Forte Agent Newsgroup Reader, InstallShield and Avira Internet Security. InstallShield is the most popular program that runs this file. InstallShield uses agent.exe to check for software updates through the Internet. If this file is causing problems for your computer, you can remove it. However, keep in mind that removal of this file could cause the program using the file to stop working. It is safe to have a system restore disk available before you delete any important file on your system in case something goes wrong.
Step 1
Open the Task Manager and terminate the process. Hold down CTRL, ALT and DEL. Click the 'Image Name' tab and find agent.exe. Click on it. Click 'End Process' to terminate it. If there are more than one, terminate them all.
Step 2
Use the Windows search tool to locate the file. Click 'Start' and 'Search' then 'All files or folders.' Select the option 'Look in: My Computer' from the drop down menu, or 'Folder: My Computer'. Type 'agent.exe' into the search box and click 'Search.' When the search finishes, hover your mouse over the agent.exe file. Right click the file name and select 'Delete.'
Restart your computer by clicking 'Start' and selecting 'Shut down.' In the menu that appears, select 'Restart' and click 'Okay.' Your computer will restart and agent.exe will be gone.
Warning
- InstallShield is an important program that comes built-in to most operating systems. By removing agent.exe you may stop this program from working correctly.
- Sean Gallup/Getty Images News/Getty Images
More Articles
Completely uninstall Apple Remote Desktop Admin | 15 comments | Create New Account
Click here to return to the 'Completely uninstall Apple Remote Desktop Admin' hint |
The following comments are owned by whoever posted them. This site is not responsible for what they say.
When I've encountered issues like this with ARD I've also had to remove:
or, in the worst case replace the entire SharingPref.prefPane
/System/Library/PreferencePanes/SharingPref.prefPane/Contents/Resources/RemoteDesktop.bundle
or, in the worst case replace the entire SharingPref.prefPane
I am seeing this more and more as our deployment goes on longer in time. We have several Mac Minis set up that do ARD display and observe scans to monitor students, these things go haywire the quickest. My iMac at work goes haywire every 6 months so far with ARD admin.
It is hard to say exactly where the problem lies as well. Is it not playing nice with the switches, routers, and controllers, or is it software related? Before at my last job we only had about 250 macs, so I never saw these problems. With over 6,400 macs I see problems like this on a constant basis.
It is hard to say exactly where the problem lies as well. Is it not playing nice with the switches, routers, and controllers, or is it software related? Before at my last job we only had about 250 macs, so I never saw these problems. With over 6,400 macs I see problems like this on a constant basis.
i thik you'll have to escape the spaces or put in quotes
rm -r /Library/Application Support/Apple/Remote Desktop/
rm -r ~/Library/Application Support/Remote Desktop/
might work better as
rm -r /Library/Application Support/Apple/Remote Desktop/
rm -r ~/Library/Application Support/Remote Desktop/
rm -r /Library/Application Support/Apple/Remote Desktop/
rm -r ~/Library/Application Support/Remote Desktop/
might work better as
rm -r /Library/Application Support/Apple/Remote Desktop/
rm -r ~/Library/Application Support/Remote Desktop/
and the others too: Remote Desktop ...
or just quote the path
or just quote the path
crap I totally forgot to put that in quotes...my bad
Upon reading further into it, you can actually go as far to do this
Thanks for the more efficient scripting method. I sometimes do things the hard way, and I think I like your method better.
I'm not sure what shell you were using when this worked, but this didn't work at all for me in Lion, using its default shell, bash. I simplified the script a bit and trimmed some paths that didn't seem to be used any more with ARD 3 & Lion.
all those saved tasks and saved unix command templates - this would be a more complete hint if it included what to backup and later restore to retain those. That's what has kept me from doing this sort of thing sooner/more often.
wow, self-spank (see below for that)- Following this didn't quite go right on computer - I ended up doing a script as follows: then reinstalled from CD and updated - And it worked WONDERS on the functioning of ARD - AND, my lists and saved unix scripts are still there. Not sure where they are stored, but it seems everything works better now and I might just do this on a regular basis. Thanks
Use with care!!!
Instead of creating a script, I ran the commands one at time in the Terminal window and the last command permanently deleted everything on my desktop. The quotes really should be around the whole path.
Instead of creating a script, I ran the commands one at time in the Terminal window and the last command permanently deleted everything on my desktop. The quotes really should be around the whole path.
It has been my experience that you can preserve your scanners and lists by backing up
~/Library/Preferences/com.apple.RemoteDesktop.plist
then removing, reinstalling, and testing ARD before restoring the plist. My theory is that it's the postgre db that gets messed up most of the time not the plist, but I haven't thoroughly investigated that.
I make regular backups of the plist so I can restore a recent good one when ARD has issues.
~/Library/Preferences/com.apple.RemoteDesktop.plist
then removing, reinstalling, and testing ARD before restoring the plist. My theory is that it's the postgre db that gets messed up most of the time not the plist, but I haven't thoroughly investigated that.
I make regular backups of the plist so I can restore a recent good one when ARD has issues.
I just deleted my entire desktop. THANKS!!
me too how do you get the bastard back
If it can be of some help, here is my experience about Apple Remote Desktop (3.5) problems, and the workaround I have found to solve them.
I have four Macs at home (3 iMacs + a MacBook). I have now installed Apple Remote Desktop on the “main” machine, the others acting as satellite machines, which I can observe and control in distant mode (which is why I bought this application).
I never experienced crash problems, but before and after installing Lion (on the four machines), I experienced somewhat random problems with Apple Remote Desktop being unable to access to the satellite machines, whereas these where recognized as present in my private network (= visible by Bonjour Browser, as well as accessible through standard Finder system ( Go -; Network)).
I have resolved this as follows : on each satellite machine, in System - Preferences - Sharing options, activate “screen sharing” (instead of “remote control”, which is the option you normally activate if you are Remote Desktop User, otherwise you do not get anything more with Apple Remote Desktop than what you already have in standard system functionality). NB : For some strange reason I cannot understand, these two options (“Screen sharing” versus “Remote Control” are exclusive).
Then, on the “main” computer, (outside Apple Remote Desktop), access to the Screen sharing functionality through the standard system Finder functionality (go -; Network -; machine selection + Screen Sharing click).
This normally works (possibly after you enter the username & password through which you want to access to the distant machine, username which of course has to match what you have specified within the preferences system; share options of the distant machine). Then, coming back to the sharing options on the satellite machine, and reversing from “Screen sharing” to “Remote Control”, Apple Remote Desktop miraculously works again on the main machine.
It is also important to note that in case each machine of your network uses a different user name and an associated password, you have to be aware of indicating the specific user name & password applicable to the satellite machine you want to access to. I had problem with AppleTV which I could resolve this way : the AppleTV password is unique, therefore if you have different password on your machines, it cannot work for all. I have suspected for a long time Firewall problems (either the standard Apple one, or the Intego one I have also installed), but I finally concluded that my AppleTV problems were not related to a Firewall problem, but to this password issue.
I have four Macs at home (3 iMacs + a MacBook). I have now installed Apple Remote Desktop on the “main” machine, the others acting as satellite machines, which I can observe and control in distant mode (which is why I bought this application).
I never experienced crash problems, but before and after installing Lion (on the four machines), I experienced somewhat random problems with Apple Remote Desktop being unable to access to the satellite machines, whereas these where recognized as present in my private network (= visible by Bonjour Browser, as well as accessible through standard Finder system ( Go -; Network)).
I have resolved this as follows : on each satellite machine, in System - Preferences - Sharing options, activate “screen sharing” (instead of “remote control”, which is the option you normally activate if you are Remote Desktop User, otherwise you do not get anything more with Apple Remote Desktop than what you already have in standard system functionality). NB : For some strange reason I cannot understand, these two options (“Screen sharing” versus “Remote Control” are exclusive).
Then, on the “main” computer, (outside Apple Remote Desktop), access to the Screen sharing functionality through the standard system Finder functionality (go -; Network -; machine selection + Screen Sharing click).
This normally works (possibly after you enter the username & password through which you want to access to the distant machine, username which of course has to match what you have specified within the preferences system; share options of the distant machine). Then, coming back to the sharing options on the satellite machine, and reversing from “Screen sharing” to “Remote Control”, Apple Remote Desktop miraculously works again on the main machine.
It is also important to note that in case each machine of your network uses a different user name and an associated password, you have to be aware of indicating the specific user name & password applicable to the satellite machine you want to access to. I had problem with AppleTV which I could resolve this way : the AppleTV password is unique, therefore if you have different password on your machines, it cannot work for all. I have suspected for a long time Firewall problems (either the standard Apple one, or the Intego one I have also installed), but I finally concluded that my AppleTV problems were not related to a Firewall problem, but to this password issue.