Can you update Ent Guide without elevated rights

[CanteenCook]

Hi

It's common knowledge now that SAS Eg and Office Add-ins are update-able directly by the client through the interface. My question is:

Is there a way for the updates to execute without the clients having elevated rights on the machine?

[JuanS_OCS]

Hello @CanteenCook,

so far, not, because the updates come through msi installers, hence the elevated rights. However, you could always ask this question to SAS Technical Support, perhaps they can offer you an alternative. If any, please let us know.

[andreas_lds]

I really hope that such a feature - updating EG without elevated rights - is not implemented in the near future, lets say the next 20 year. Maintaining a site where everyone uses a different version will be a nightmare.

[Kurt_Bremser]

---

@andreas_lds wrote:

I really hope that such a feature - updating EG without elevated rights - is not implemented in the near future, lets say the next 20 year. Maintaining a site where everyone uses a different version will be a nightmare.

---

Especially in light of the still prevailing problem that every new EG version writes project files only in a format that previous versions can't read.

[CanteenCook]

Hi Guys

After some digging around, I came across this article:

Using Windows Installer with UAC from the MS support site.

Windows Installer complies with User Account Control (UAC) in Windows Vista. With authorization from an administrator, the Windows Installer can install applications or patches on behalf of a user that may not be a member of the Administrators group. This is referred to as an elevated installation because the Windows Installer makes changes to the system on behalf of the user that would not normally be allowed if the user were making the changes directly.

• When using Windows Vista in a corporate environment, applications can be designated as managed applications. Using application deployment and Group Policy, administrators can lockdown directories and then assign or publish the managed applications in those directories to standard users for install, repair, or removal. Managed applications are registered in the HKEY_LOCAL_MACHINE registry hive. Once an application has been registered as a managed application, subsequent installation operations always run with elevated privileges. If the user is running as an administrator, no prompting is required to continue the installation. If the user is running as a standard user, and the application has already been assigned or published, the installation of the managed application can continue without prompting.

I am hoping that if we package E Guide as a "Managed Application" as stated above. if I understand the above correctly, any subsequent updates will not require elevated rights because they are "managed".