Adobe Remote Update Manager

Follow

John Sullivan

• November 29, 2018 17:43

When I run RUM I always get the error: RemoteUpdateManager not launched with Admin privileges. RemoteUpdateManager exiting with Return Code (1)

RUM works if I run it manually on the target machine.

0

• 

  Brigg Angus

  • November 29, 2018 18:27

  Hi John,

  If you download the RUM from the admin console in Adobe CC, extract the executable, create a package and then deploy that package, what results do you get?

  Here is the package I created:

  0

  Comment actions Permalink
• 

  John Sullivan

  • November 29, 2018 18:53

  Hi Brigg. Thanks for your reply. Unfortuantely, I get the same result.

  0

  Comment actions Permalink
• 

  Brigg Angus

  • November 29, 2018 20:01

  Okay. Would you post a screenshot of the install step from your RUM deployment package, like the one above? Also, a screenshot of the Options tab for the step. It might also have to do with the origin of the RUM. Did you download that from the Adobe admin console for CC or from a machine with Adobe CC products installed?

  0

  Comment actions Permalink
• 

  John Sullivan

  • November 29, 2018 20:19

  I tried it both ways. These screenshots were from a fresh download from Adobe. My initial attempts were on a machine with Audition CC installed. The Deploy User is an account with Domain Admin permissions.

  Here's the install step:

  And here's the options:

  

  0

  Comment actions Permalink
• 

  Brigg Angus

  • November 29, 2018 20:32

  Perfect. I'm assuming the Deploy User is also a local admin on the machine (otherwise, terrors). I was able to get some to "fail" (the machine needed a reboot) and have Output Logs for those failures. Do you also get those? If so, is the same elevation error presented as the disposition of the attempted update?

  

  If it is the same elevation issue, can you deploy some other package that requires elevation to the machine? Since I'll assume that would be successful (but we do want to rule that out), change the credentials (Options > Credentials) in PDQ Deploy to some other account that has local admin privileges on the failed target, set those credentials as default (set them back afterwards, however), then attempt to deploy. Do you get the exact same error?

  0

  Comment actions Permalink
• 

  John Sullivan

  • November 29, 2018 22:43

  Well, I did what I should have done a long time ago, and tried it on another target, and it seems to be going. (25 minutes so far!) My failing target has a device license, the working one has a user license, so I'm wondering if that's the difference.

  0

  Comment actions Permalink
• 

  John Sullivan

  • November 29, 2018 22:49

  Though after thinking about it, running RUM locally did work, and said that no updates were needed, so that theory might be wrong. I'll still try your admin tests when I get a chance. Really appreciate your help with this. You people rule.

  0

  Comment actions Permalink
• 

  Brigg Angus

  • November 30, 2018 03:16

  No worries, John. If the issue persists, shoot an email to support@pdq.com and we can go into full-on troubleshooting mode.

  0

  Comment actions Permalink
• 

  John Sullivan

  • November 30, 2018 17:31

  Thanks. So far it's working on everything BUT my test machine. Figures.

  0

  Comment actions Permalink

Please sign in to leave a comment.