Quickbooks says user doesn't have proper permissions

Follow

Miguel De Santiago

• May 10, 2022 19:54

So I was told AutoElevate could let endusers update Quickbooks on their own but a user is always getting this error saying they don't have proper permissions to update.  I have to log in and run as an admin to do so.

How can I make it so that when they launch it they can update it too?  Do I have to set the app to run as an administrator?

0

• 

  Andrew Brockhaus

  • June 28, 2022 18:20

  Miguel, Did anyone respond to you?  We set quickbooks as a rule but the end user doesn't get an error message when the update.  It looks like it applies but then it breaks quickbooks and we have to login as an Admin on the computer and apply it there to get them working again.  

  0

  Comment actions Permalink
• 

  Miguel De Santiago

  • June 28, 2022 20:19

  No, no one responded.  I thought about this, and the only thing I can think of to make it work is to set all the desktop shortcuts for all versions to "Run As Administrator" and then approve the application using User mode and put it Company-wide.

  0

  Comment actions Permalink
• 

  Todd H

  • July 08, 2022 16:34
  • Edited

  Setting 'Run as Administrator' was one of the first things we tried.  But setting Shortcuts to 'Run as administrator' created various issues and even if it worked you wouldn't want QB running with Admin privileges 100% of the time.

  So what ended working better was just end user training.    We added the following instructions for installing 'QB Updates' .

  1. If QB is already open, then Exit / Close the program.
  2. To Install Updates: Right click on the QB program icon on your desktop
  3. Select 'Run as administrator' from the Context menu popup
  4. That step both gets around QB not realizing it will be able to run as admin to install the updates, and it triggers the AutoElevate rule.
  5. Install the updates
  6. **Important**  After the updates are installed, Exit QB and relaunch it normally.   This last step is important if you're using a Company File on a Shared network folder with locked down security permissions (instead of QB's insane default public access permission that it keeps trying to overwrite with...)

   

  0

  Comment actions Permalink

Please sign in to leave a comment.