ILLiad Client Automatic Updater

The client contacts the Atlas update server and checks for updates each time staff log into the client. If an update is available, a popup message will appear to notify you that an update has been found. Major version updates (going from 8.2 to 8.3, for example) require you to update the client because the existing client may not be compatible with the ILLiad server database. Click Yes to download and run the client update.

You are not required to run minor version updates (going from 8.3.0.0 to 8.3.1.0, for example) and can select No to dismiss the update and open the client. You can also dismiss further notification of that available update when logging into the client by clicking the Do not ask this again checkbox. Note that the update notification will still display for that version on the status bar.

In addition to the update checks at login, the client checks the update server every 12 hours to see if a new version is available. If an update is found, a notification will display on the status bar. Clicking the notification will close the client and download and install the update.

Server Version Matching

Beginning in ILLiad 10.0, the update the client offers is matched to the version your ILLiad server is ready for. Each ILLiad Client build declares the minimum server version it requires, and the client only offers an update your server can support.

If a newer client requires a server upgrade you have not performed yet, that build is simply not offered — the client keeps running normally and staff see nothing. Once your server is updated, the newer client becomes available automatically at the next check. This prevents a client from getting ahead of the server it connects to.

Nothing needs to be configured for this to work. Two settings support the behavior:

• VersionClient — the client version your server expects. The server updater sets this value when the server is updated, and it is what update matching compares against. You do not normally edit it by hand.
• ClientUpdateLocation — an optional override for where the client looks for updates. This is blank at most sites, which is correct. If you have set it, point it at a location containing the current update information; if the client cannot read what it finds there, it falls back to the standard Atlas update source.

Timed Out Connections

If the client cannot connect to the update server and the connection times out (after 15 seconds), the client will cease the attempt to connect and open to the Main form.

Once you have logged in, the client will continue to check for updates every hour until a version check has been completed. If an update is found, a notification will display on the status bar. Clicking the notification will close the client and download and install the update.