Auto Updates, Permissions, and the Registry - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

pyro9219
Posts: 4
Joined: Thu Jan 14, 2010 10:35 pm

Auto Updates, Permissions, and the Registry

Hello,

I've been trying to get the auto update feature working with a limited users account and have hit some hurdles. I have my projects set to not require admin rights, and this is in a multi-user enviroment, so that adds to the game :)

1) The program is first installed using an administrator account to get everything in place and set full control permissions on my folders/files and to place a few registry keys onto the system. To get the key onto each users machine, I've created a key under HKLM\Software\Microsoft\Windows\CurrentControlSet\Run that calls a silent .reg file to install the version number for the auto update to the current users profile. I'm doing it this way so that it doesn't matter who logs into the system, the version number is written so the auto-updater can be called. My problem is that if I manually click on the .reg file it will install the key as expected into the current users machine, but for some reason the HKLM loader key doesn't seem to function. HKLM/Run should come after the user logs in according to MS, so that should not cause the problem.

2) I can't run the updater.exe from my programs folder with a limited account. However, if I move the .exe and the .ini to the desktop and create a shortcut with /checknow it will start the check no problem. I've given my applications folder full rights for all users, so I'm not sure what is causing this.

3) The update will fail after attempting to load from the auto updated on a limited user account. This is both with the auto-update tool and running the temp folder with the downloaded update. I will get a message to the extent of "some or all of this setup requires administrative rights. please contact your administrator if you require assistance". I've not been able to track down anything that would lead me to believe it's anything I'm doing, and nothing I've found with Windows Installer makes me think the user shouldn't be able to update. However, I do know my limited user does not have permissions to even uninstall the application.

Does anyone have answers, solutions, or tips? In a power user or admin account I've never had any trouble with all the different methods for updates I've done. I've also got an enterprise level license so I should have all the required bells and whistles to figure something out.

Help is appreciated in advance!

Thanks,
Chris
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Auto Updates, Permissions, and the Registry

Hello,
1) The program is first installed using an administrator account to get everything in place and set full control permissions on my folders/files and to place a few registry keys onto the system. To get the key onto each users machine, I've created a key under HKLM\Software\Microsoft\Windows\CurrentControlSet\Run that calls a silent .reg file to install the version number for the auto update to the current users profile. I'm doing it this way so that it doesn't matter who logs into the system, the version number is written so the auto-updater can be called. My problem is that if I manually click on the .reg file it will install the key as expected into the current users machine, but for some reason the HKLM loader key doesn't seem to function. HKLM/Run should come after the user logs in according to MS, so that should not cause the problem.
I am afraid I do not understand what you are trying to do here, or what the issue is. Could you describe this more clearly, perhaps give an example?
2) I can't run the updater.exe from my programs folder with a limited account. However, if I move the .exe and the .ini to the desktop and create a shortcut with /checknow it will start the check no problem. I've given my applications folder full rights for all users, so I'm not sure what is causing this.
What exactly happens when you try to run updater.exe? Does it give off an error? What error?
3) The update will fail after attempting to load from the auto updated on a limited user account. This is both with the auto-update tool and running the temp folder with the downloaded update. I will get a message to the extent of "some or all of this setup requires administrative rights. please contact your administrator if you require assistance". I've not been able to track down anything that would lead me to believe it's anything I'm doing, and nothing I've found with Windows Installer makes me think the user shouldn't be able to update. However, I do know my limited user does not have permissions to even uninstall the application.
Please note that an update will remove the existing installation and install a new one in its place. That means all privileges will be removed along with the removed folder. The new update would have to again be installed using admin privileges. You should make sure the folder that was created by the previous install is not removed, so that the privileges remain in place.

Please send your .aip project file to support at advancedinstaller dot com so we can further investigate the issue.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
pyro9219
Posts: 4
Joined: Thu Jan 14, 2010 10:35 pm

Re: Auto Updates, Permissions, and the Registry

GabrielBarbu wrote:Hello,
1) The program is first installed using an administrator account to get everything in place and set full control permissions on my folders/files and to place a few registry keys onto the system. To get the key onto each users machine, I've created a key under HKLM\Software\Microsoft\Windows\CurrentControlSet\Run that calls a silent .reg file to install the version number for the auto update to the current users profile. I'm doing it this way so that it doesn't matter who logs into the system, the version number is written so the auto-updater can be called. My problem is that if I manually click on the .reg file it will install the key as expected into the current users machine, but for some reason the HKLM loader key doesn't seem to function. HKLM/Run should come after the user logs in according to MS, so that should not cause the problem.
I am afraid I do not understand what you are trying to do here, or what the issue is. Could you describe this more clearly, perhaps give an example?
2) I can't run the updater.exe from my programs folder with a limited account. However, if I move the .exe and the .ini to the desktop and create a shortcut with /checknow it will start the check no problem. I've given my applications folder full rights for all users, so I'm not sure what is causing this.
What exactly happens when you try to run updater.exe? Does it give off an error? What error?
3) The update will fail after attempting to load from the auto updated on a limited user account. This is both with the auto-update tool and running the temp folder with the downloaded update. I will get a message to the extent of "some or all of this setup requires administrative rights. please contact your administrator if you require assistance". I've not been able to track down anything that would lead me to believe it's anything I'm doing, and nothing I've found with Windows Installer makes me think the user shouldn't be able to update. However, I do know my limited user does not have permissions to even uninstall the application.
Please note that an update will remove the existing installation and install a new one in its place. That means all privileges will be removed along with the removed folder. The new update would have to again be installed using admin privileges. You should make sure the folder that was created by the previous install is not removed, so that the privileges remain in place.

Please send your .aip project file to support at advancedinstaller dot com so we can further investigate the issue.

Best regards,
Gabriel
Alright, let me back up...

What I need is a solution that will let me run the update application on a system with restricted rights. Assuming I already have the application installed from an admin account so everything is in place - how can I make it so the user can receive updates?

From my email to support:

My company produces a product called Revenue360 which is a client / server based integrating solution to help medical facilities verify patient insurance. We have found with our nation wide customer base is that just about all have their users setup with User Level Access, not Super User or Admin. Due to this, our application has been deployed via GPO as an administrator. What I need is to then be able to push our product updates, or allow the user to click the update shortcuts I’m providing from their accounts and receive the latest versions.

If you have a solution, or have a set of mocked up project files that I can follow I would appreciate it!
pyro9219
Posts: 4
Joined: Thu Jan 14, 2010 10:35 pm

Re: Auto Updates, Permissions, and the Registry

I've not received anything from the support email I sent in - atleast a confirmation would be nice...

Anyone else have any thoughts?
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Auto Updates, Permissions, and the Registry

Hello,

Your product has the Installation Type set to "Per-machine only (fails if user is administrator)" on the Install Parameters page. This means your product will fail to install if the user is not an administrator.

Please try setting both installers to "per-machine if user is administrator, per-user otherwise" and see if that works.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
pyro9219
Posts: 4
Joined: Thu Jan 14, 2010 10:35 pm

Re: Auto Updates, Permissions, and the Registry

No luck,

What I've decided to do is have our customers release either a GP or Scheduled Task to run the update at each login while using Administrator credentials - this has worked flawlessly in a number of our tests so it should work.

Return to “Common Problems”