How could I test some official test?

[quyen194]

In page:
https://code.google.com/p/omaha/wiki/UsingOmaha
there is a test with command line:
GoogleUpdate.exe /install "appguid={8A69D345-D564-463C-AFF1-A69D9E530F96}&appname=Google%20Chrome&needsadmin=False&lang=en"
That is the only test can use after compile omaha without any modification. So how could i test it with this project? (your omaha server)
and must i change all to start test omaha client? follow this:
https://github.com/Crystalnix/omaha/wiki/Customizing-Omaha

I just don't know how to start step by step :(
follow above, i have to change so much (many step and long time) then test, so too hard to debug what wrong if i made :(

[shashkin]

If you're using unmodified Omaha from master branch, you can only test it against Google servers as described here and here. However, since unmodified Omaha differs from official Google Update, you can expect the process to fail shortly after install with the error code 0x80040905. This is due to these products writing their registration information to the Google Update area of the registry, instead of your Omaha's location.

You can also build "semi-official" Google Update (it's not really official because our fork contains some modifications to the original Google's project) which will not fail after install. As said here, "the main difference between code compiled from this site and Google Update is the Authenticode signature and version number, and the CLSIDs of the COM objects. (To restore the original CLSIDs and build a complete Google Update clone, see the files in the official/ folder of the source.)". The only problem here is that shortly after successful installation your Google Update will also update itself because Google has newer version of Google Update.

The Customizing Omaha page describes all required steps you need to perform to have your own branded Omaha. It is not necessary to customize Omaha if you want just to test it.

If you want to test your Omaha build with your own server (assuming it's already set up and working), you need to change URLs located in omaha\base\const_addresses.h to point to your server. You also need to be sure that your app installers will write into the correct registry location. In case of unmodified Omaha the registry locations are HKEY_LOCAL_MACHINE/Software/OmahaCompanyName/Update and HKEY_CURRENT_USER/Software/OmahaCompanyName/Update.