Recommended Changes

We strongly recommend making these changes before you release:

• Change the names of core executables -- GoogleUpdate.exe, goopdate.dll, GoogleCrashHandler.exe, and so on. (This will require changes to the SCons build scripts, to the names of EXEs in omaha\base\constants.h, to WiX MSI fragments, and to several unit tests.)

• Duplicate the contents of common\omaha_customization_unittest.cc into a new file, replace EXPECT_GU_STREQ() with EXPECT_STREQ(), and update the string literals for your fork of Omaha. Do the same with EXPECT_GU_ID_EQ() in a copy of goopdate\omaha_customization_goopdate_apis_unittest.cc. (These macros change their behavior based on the value of is_google_update_build in main.scons. When set to True, this test checks for equality - i.e. that the values haven't changed between builds. When set to False, it checks for inequality - i.e. it ensures that these values do not collide with the official Google Update releases. By adding additional tests with the first behavior, you can provide the same safety measures for your own fork.)

• Define a new CUP public key if you plan to use the CUP protocol on your update server.

• If your product exposes any settings that are controlled via Group Policy, you may want to move the Omaha GPO settings to the same location as your product. This is set in omaha\common\const_group_policy.h.

• Change the value of the reference GUID used to identify your fork of Omaha when self-updating. This is defined in kGoopdateGuid and GOOPDATE_APP_ID in omaha\base\constants.h and verified in several unit tests.

• Do a general search for strings that reference Google or Google Update, and revise them. This should include debug logging statements.