Differences between Offline and Online
Upgrades 
The Offline Upgrade is executed as a command in the parent upgrade. Such nesting implies that Offline Upgrades behave differently than the parent upgrade, as described below:
· The Offline Upgrade does not display another window during execution. The parent upgrade window appears.
· The Offline Upgrade creates another log file "ClientUpgradeSlave.log" containing log statements. These statements are not visible in the main console log window.
· The Offline Upgrade does not try to shut down all other applications unlike the parent upgrade.
· The Offline Upgrade does not register for an automatic restart. The parent upgrade already does this. Furthermore, only the parent upgrade can start this Offline Upgrade.
· The Offline Upgrade does not try to extract packages from the application database (IDES), instead it first searches for the packages and if not found then prompts the user to select a directory where the package is present and continues the process.
· After completion, the Offline Upgrade does not acknowledge success/failure to the CRM Server (since it was not sent via the CRM Server).
· The Offline Upgrade has a special version number that ends with a dollar sign ($), indicating that this is an offline upgrade.
· After a successful completion, its registry entries are removed immediately by the parent upgrade.
· Upgrade packages created marked as offline can be started only by another upgrade containing the Offline Upgrade Command. Such packages cannot be started manually like a normal .mup file.
Although an offline upgrade also results in the creation of a Mobile Upgrade Package, in a folder, this package is not the same type as the Mobile Upgrade Package created using the online method.
See also: