When launching the Enterprise Reporter Configuration Manager on a system where User Account Control (UAC) is enabled, the application does not open unless it is started with Run as administrator (elevated privileges).
Customers may also ask whether this requirement can be avoided by granting permissions through a custom security group, delegated permissions, or another local Windows group instead of using administrator-level elevation.
This is a known product issue tracked under:
Bug 486747 – Elevated privileges are required to open the Configuration Manager and Report Manager
When UAC is enabled, the Configuration Manager currently requires elevated privileges to launch. This behavior is under investigation by the Product team.
Additionally, according to the Enterprise Reporter documentation:
This behavior is currently by design due to a known product issue, and there is no supported workaround to eliminate the UAC elevation requirement.
Current requirements are:
At this time, there is no supported method to satisfy this requirement by using a custom local group, delegated permissions, or minimum-permission configuration without UAC elevation.
- Enterprise Reporter Configuration Manager User Guide (UAC elevation requirement):
https://support.quest.com/technical-documents/enterprise-reporter/3.6/configuration-manager-user-guide/5#TOPIC-2044106
- Enterprise Reporter Installation and Deployment Guide (Reporter_Discovery_Admins requirement):
https://support.quest.com/technical-documents/enterprise-reporter/3.6/installation-and-deployment-guide/7#TOPIC-2044361
- Internal reference: Bug 486747 – Elevated privileges are required to open the Configuration Manager and Report Manager
