Are administrator rights required to install QAP?
If the Quick Access Popup setup program asks for an administrator password, you have two options: ask your system administrator to install it for you (using the setup program). Or, if you have some basic technical knowledge and prefer to get it done yourself, install Quick Access Popup in portable mode since this type of installation does not require administrative rights.
Now, for your sysadmin...
The QAP setup program requires elevated rights (via a User Account Control dialog) when the installation is started. If the setup program was started by an unprivileged user, Windows will ask for the password of an account that has administrative privileges, and the setup will then run under that account.
In order to allow installation by the admin and to set configuration files specific to end users, the setup program is executing the following steps.
- It creates a group Quick Access Popup in the All Users Start Menu with the Start In parameter set to the common appdata folder (for example: C:\ProgramData\Quick Access Popup).
- In the common appdata folder, the setup program creates file named quickaccesspopup-setup.ini where QAP stores the language selected by user during setup. This folder can also include customized templates of the files QuickAccessPopup.ini and QAPconnect.ini. This would allow the sysadmin to create a default menu and default configuration for the needs of his organization's end users.
- When Quick Access Popup is launched for the first time by an end user, it creates in user's appdata folder (for example: C:\Users\Username\AppData\Roaming\Quick Access Popup) the files QuickAccessPopup.ini and QAPconnect.ini from an internal template, unless templates of these files are found in the common appdata folder. In this case, these files are copied to user's appdata folder. Original files in the common appdata folder are never changed by end users.
- If the end user selects the Run at Startup option, the shortcut created in his/her personal Startup folder will make sure the users's config is saved in his/her personal appdata folder.
If, during setup, the option Import Folders Popup settings and favorites is selected, the imported settings are saved in the file quickaccesspopup.ini in the common appdata folder. This file would also be used as a template for end users configuration.
There is no obligation but... if Quick Access Popup is making your company save money, maybe should you consider a donation to QAP developer... 🙂
As seen at step #2 above, sysadmins could create or edit the quickaccesspopup.ini file in the common appdata folder to give their users a template with favorites of interest for all users: network folders, path to shared applications or documents, intranet URLs, etc. Administrator could also edit this file to enable the Shared Menus Catalogue to facilitate the addition of shared menus by end users (see Can I create a catalogue of shared menus for my team or workgroup?).
To facilitate the creation of a new quickaccesspopup.ini file, admin can run QAP in portable mode, configure options and favorites and copy to fresh ini file the common appdata folder.
About Explorer Context Menus
When installed with in setup mode, QAP always enable its Explorer Context Menus. There are two exceptions: context menus will *not* be enabled if "ExplorerContextMenus=0" in either of the quickaccesspopup.ini file in current user's appdata folder or common appdata folder. More about Explorer context menus: Explorer Context Menus Help.