After you have published AND enabled an Upgrade package to one or multiple end users with MarvelClient Essentials, Basic or Upgrade installed on their Notes client(s), the following happens on each respective client:

  1. For licensed customers:
    Every hour, up and running clients check for new or changed Actions. For testing purposes you may not want to wait as long.
    In production, however, the respective clients will start to download the packages within the next hour, depending on the randomization settings of your published Smart File Downloader Action(s).

  2. For all customers (Essentials and licensed):
    Simply (re)start a respective client to see your downloads appear start in your Upgrade Directory (%PUBLIC%\MCUpgrade) 5 minutes after starting a client.
    Clients will also immediately deploy the MCUpgrade executable and your Upgrade configuration (MCUpgrade.ini, keyfile if applicable, splash screen etc.) into your Upgrade Directory.

    Why do we suggest using %PUBLIC%? Because for Multiuser setups, you don't want multiple users downloading the same installer multiple times into different directories.
    %PUBLIC% has the huge benefit that you have one download per computer, even if a machine is used by multiple users on any given day.
    Some of our customers have up to 60 different users per day use one computer.

  3. Clients with MarvelClient Essentials will check whether all Upgrade requirements are met after login.
    MarvelClient Essentials customers can optionally enable the same check for client shutdown by enabling the readily prepared Action #2.
    Clients with MarvelClient Basic or Upgrade will check whether all Upgrade requirements are met on first server access after start (waiting a minimum of 60 seconds after starting a Notes client), as well as during client shutdown.

  4. Upon every licensed and selected RunType according to 3.), if all requirements are met (Conditions according to your Upgrade configuration, plus, if set, the When and Who tab configuration, and finished downloading of all packages), MarvelClient Upgrade will launch.
    In other words: If all requirements are met during a Notes client (re)start, Upgrade will launch.
    If you see MCUpgrade.log in your Upgrade Directory (%PUBLIC%\MCUpgrade), but nothing happens, go take a peek. It should tell you, what is missing.
    If you don't see MCUpgrade.log yet, take a look at %localappdata%\panagenda\pmc (Essentials) or %localappdata%\panagenda\marvel (licensed) and check log.xml for details.

  5. Further execution of your upgrade and the corresponding user experience depends on your Upgrade configuration.