How to update omaha client itself?

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Install product with omaha client.
2. Need to bring to users new version of omaha client.
3. How to do this?

What is the expected output? What do you see instead?
I need to know - what i must put into omaha server and register a package for 
update with omaha client ID (default app id is 
{430FD4D0-B729-4F61-AA34-91526481799D}) for correct updating omaha client on 
user's PC? Which file from build?

What version of the product are you using? On what operating system?
Omaha client version: 1.3.23.0

Original issue reported on code.google.com by Komarnit...@gmail.com on 24 Sep 2012 at 12:41

GoogleCodeExporter commented 9 years ago

Your update server should supply the untagged metainstaller for your new 
version of Omaha (GoogleUpdateSetup.exe is the name in the default sources) 
with the command line argument /update.

FYI, we try to reserve the bugtracker for software bugs in the Omaha source 
code -- if you've just got a question about how to customize and/or deploy 
Omaha, try emailing the omaha-dev or omaha-discuss mailinglists instead.  
Thanks! :)

Original comment by ryanmyers@google.com on 24 Sep 2012 at 7:27

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

Many thanks, Ryan.

Sorry for this question here, really don't know where i can ask it. Now i know 
where to ask. Thanks.

Original comment by Komarnit...@gmail.com on 25 Sep 2012 at 2:31

jatpat / omaha

How to update omaha client itself? #45