So no one knows? And no one from Adobe can say? Really?!
You can contact Adobe. This is a user to user forum.
And where might I find their enterprise support contact information?
I don't know.
Outstanding. So, my original request for information remains open.
I think an ARM is the processor used in most mobile phones (iphone and G1) - so this is probably something to do with enhancing the experience on mobiles.
If you are using AutoStarts you could always disable it and then reenable it if you have any problems with adobe products.
ARM is a processor, yes - but why would Adobe need to start this process on x86 processors, at startup, for every user? That doesn't seem to make sense to me.
I stumbled my way through their support area and submitted a question, which will hopefully get to someone who knows on the Adobe-side.
The only reason I can think of is if you are developing websites/flash animations which you wish to distribute to a mobile device.
OK - but if you're developing ... you aren't using Reader. And every user on the planet wouldn't require this feature, so starting this process at startup for every user just doesn't make sense.
Any other guesses?
Well am sure mobile devices are capable of reading .pdf files, so am sure it still to do with publishing adobe files.
And who to say that AdobeARM doesnt get installed with the latest installations of dreamweaver, flash etc anyway. its only cause you have downloaded a later version of this you actually noticed it.
My original question is still unanswered.
I just called. They do not support Reader, as Reader is a free product. They pointed me to the knowledge base, which has NO information about AdobeARM; or these forums, where no one seems to know what this process is for, either.
I'm at the point where I feel disabling this from executing on startup is the most viable option, as I don't want some rogue process phoning home and causing pain for my user base.
AdobeARM.exe is a part of new Adobe Acrobat\Reader updater.
If you manage updates yourself, it is absolutely safe to remove it from Run registry.
I don't know why Adobe, in their right minds, thinks the corporate/enterprise customer could/would possibly want their software updating itself. Sounds like a help desk nightmare.
I've axed this from the registry - along with the other tweaks I implement via the Adobe transformer.
1 person found this helpful
I forgot to mention that the right way to disable automatic updates in enterprise environment is to set bUpdater DWORD value to 0 in Registry
for Reader 9x
for Acrobat 9x
Thank you for the explanation; I also needed to know this.
Question: What is AdobeARM.exe
Answer: Adobe Reader Manager
It appears to be a update/download manager for adobe reader 9.2 and launches at windows startup via the following registry entry:
"Adobe ARM"="\"C:\\Program Files\\Common Files\\Adobe\\ARM\\1.0\\AdobeARM.exe\""
To prevent it from starting at windows startup you can safely delete this entry from the registry. If you change your mind and want it to startup again at windows startup just add the entry back to the registry. To easily add it back you can copy the registry entry above and paste it into notepad then save it as whatever.reg, next double click whatever.reg and you will get asked if you want to add this entry to the registry, click yes obviously.
"I just called. They do not support Reader, as Reader is a free product"(what MORONS you are Adobe)
that is such a pathetic answer.Excuse me adobe it is YOU who put the software out.That bloody adobearm disabled my network connection.I am wondering why no one else has said anything about it.My first thought was to see what was running in the task manager and sure enough,there it was so i disabled it then deleted the file and also disabled it in msconfig
FYI - In addition to removing this from the registry, I found that you also need to do the following:
End Task on AdobeArm.
Delete the three programs in C:\Program Files\Common Files\Adobe\ARM\1.0\ directory - AcrobatUpdater, AdobeARM & ReaderUpdater (I am now deleting the entire Adobe\Arm\1.0 directory instead of just the three files) .
Last - Delete the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run “Adobe ARM” entry.
I got some email from this bloody forum.I hope i have blocked it now.And for peoples info either deleting the info from the registry OR deleting the files is ok.Why Adobe can't reply is so pathetic.!!
STOP SPAMMING ME.!!
I DIDN'T post this
STOP SPAMMING ME.!!
I DIDN'T post this
Nobody is spamming you - you posted in this topic, and because your Preferences are set to notify you, you get notified. You have to change your Preferences and unsubscribe from this and all other subscribed topics, or post at http://forums.adobe.com/community/general/forum_comments if you are unwilling to do that.
i have blocked the emails from adobe anyway.
This thread is a bit long in the tooth now we are up to 9.3.4 really, but here's my tuppence worth.
Anywayz, after installing 9.3.3 then being nagged to update to 9.3.4. I did so.
Then, thanks to my Guardian Angel, WinPatrol on lookout, I was requested to let reader start with the system FIFTEEN TIMES IN ONE HOUR!! That was with only two start-ups of reader! So I initially did what a man's gotta do.
I un-installed Reader.
Then I thought "This ain't gonna beat me", so I did some trawling round T'Interweb.
I eventually came across this thread. Some numbers may have changed from the original Tut, but by following the Tut, I now have, and this is the first time I've ever attemped anything like this, (although I have been known to make my own msstyles/themes) a very light Reader, no nags, no let me auto-start, no ARM and no harm.
Not quite sure if I'm more impressed at the speed reader now opens or in my ability to have made it like this!!
BTW Running Windows 7 64 bitHome Prem.
Elmer (not very, now) BeFuddled
Message was edited by: Elmer B. Fuddled
If anyone is still wondering what it is, look here:
It's used for the Updater.
ARM stands for Adobe Reader & Acrobat Manager.
ARM is the new updater that came to replace AUM. There are only several keys in registry to control it and this keys can be found in AIM: Administrator's Information Manager. http://kb2.adobe.com/cps/837/cpsid_83709.html here you can find it.
I've made group policy templates in admx format based on AIM and they include managing ARM. They can be found here https://sourceforge.net/projects/customadmx/
Yes, it does stand for Adobe Reader Manager and I don't understand how and Acrobat Manager gets added in when ARM exists even if only reader and no Acrobat is installed, plus it would and should be ARAM if it truly stood for Adobe Reader & Acrobat Manager and I am well aware the question has already
been answered and yes it can be removed without causing trouble. The user that posted group policys to make changes and propagate sytem wide in an Active Directory enviornment has a head on his shoulders. Those that went about it via the registry need to rethink strategy.
In workgroup enviornments or in the absence of Active Directory in some enviornments, there is a far more efficient way to do it then the registry.
I think it bizaar and over the top to always jump to the conclusion you need to go under HKEY_LOCAL to add or remove things from startup. It is easy to botch things in the registry, far more time consuming to add and remove entries and simply not neccesary. Reality is even after removing the registry entries or changing a DWORD value, ARM still resides on the machine, but just doesn't start up when Windows starts. However, by approaching it this way if you decide you need it later it is just more of hassle to add and remove from registry and is just plain uneccessary even if it makes you feel geeky cool that you did it by the registry. In many corporate enviornments, i.e. large ones like Boeing, where I have worked a registry change especially propagating it company wide can create headaches and even on a single computer this other method is far more efficient.
Simply go to "RUN" and type "msconfig" then go to startup tab and deselect AdobeARM and apply, it accomplishes the exact same thing without delving into the registry uneccesarily and is VERY SIMPLE. Furthermore, you can propagate the change to other machines more easily and if you change your mind its as easy as going back and rechecking the box. Furthermore, in the absence of a group policy you could simply make the change on the master image using msconfig and next time you image, it would propagate, even in a non AD enviorment.
Why most parties in this thread think going to the registry under HKEY_LOCAL>blah blah blah>Run and deleting or adding values is the best way to go to accomplish this I will never know.
Someone with a B.Sc. in Computer Network and Communications Management, A+, CCNP and X....system admin, lead tech and help desk manager
>>I think it bizaar and over the top to always jump to the conclusion you need to go under HKEY_LOCAL to add or remove things from startup.
Yes!!! Me too!!!
I think Adobe should not "go undel HKEY_LOCAL and add things to startup":
If they do not want os removing it... they can simply not add it in the first place!
I HATE automatic update programs
I just updated Adobe Reader and my machine told me it wanted to run ARM at startup, was that alright with me?
That's what brought me here.
So I read this and told the updater I didn't want ARM. It finished the update without the ARM thing. Wouldn't that be the simple way to go?
I also installed it without the infuriating and redundant McAfee scanner - another option provided for me.
Lastly I find it bizarre that man so educated and obviously intelligent should spell it the way he does.
That's the kind of nasty, snide, nitpicking, carping little nuisance I am....
I just have this thing about spelling......
p.s. the thing I found most interesting was the bit about foxit. I'm downloading it, will give it a try. Lovely if I can get rid of Adobe entirely....
Why create two update mechanisms and programs, one for reader and one for acrobat? Why not just create one! Maybe Microsoft should create Word updater, telnet updater, notepad updater, etc....