To continue, you need to be on a Windows computer with administrator privileges. You will create a very basic application, upload it to an update server, then use Omaha to release a new version. The rest of the tutorial will now give you first-hand experience with using Omaha. This for instance allows a non-privileged user to 'check for updates' in a system-wide installation.

Omaha performs all update and installation tasks with the same privileges as the original installation. For example, Chrome may be installed with an administrator account, but then run under a normal user account without permissions to perform updates. The only thing the two components need are executables which perform the application-specific update/installation steps.Īnother important feature of Omaha is that it handles permission issues. exe file which can be used to update the respective application.Ī nice feature of this binary-based approach is that Omaha and the update server are completely agnostic of the applications they manage. If a new version is available, the server responds with the URL of an. It sends this information to the update server. When the update tasks run, Omaha looks at the registry keys shown above to see which applications need to be updated, and what versions they are at.

Google chrome administrator privileges