In this article
As of version 4.7 of the console, it is possible to provide updates for client software, AnyFind definitions, and license files directly from the console without the need to create a custom Check for Updates server. It is recommended that the console be used for updates and Check for Updates servers be phased out.
It is possible to control how existing Identity Finder clients are updated to new versions. By default, Identity Finder clients are not configured to check for software updates. It is possible to modify your settings and enable your clients to check your own Identity Finder Console server (or other web server) for updates. It is also possible to disable the pull method and use any existing software distribution method used within your organization to push out client updates.
By following the steps in this article, you can configure Identity Finder clients to automatically check for and download updates from your own server. There are two types of updates: application updates and AnyFind definitions updates. Using the pull method, it is not possible to check one server for application updates and a different server for AnyFind definitions updates; however, it is possible to check one server for updates and download those updates from a different server.
To configure your deployment to have your clients pull updates, you must configure your update server to publish the updates and configure your client settings to check that server for updates.
You must have an Identity Finder Console server (or other web server) that can be browsed to from the client machines that will be configured to check it for updates. Once the machine has been identified, the following steps must occur:
- Create a valid version information file
- Place the version information text file in a browseable path. Ensure that you can view the version information file from a web browser on a machine whose client will check that file for updates.
- Place the installation packages in the browseable path specified in the version information file. For example, copy IdentityFinderSetup.exe, and/or IdentityFinderMacSetup.dmg to a location that, when accessed via a web browser, prompts the browser to save the file to the local machine.
Once the server has been configured to publish updates and make the installation packages available, the clients must be configured to check that server. To do so, configure the following settings (more information on each of these settings is available in the Windows Configuration Guide):
- Set Settings\Updates\UpdateHost to the base URL for the update server. This should be of the format http://internal.myupdateserver.com or https://internal.myupdateserver.com, as appropriate.
- Set Settings\Updates\VersionInfoPath to the path from the root of the website to the version information file. For example, if the file is http://internal.myupdateserver.com/version7.info, set VersionInfoPath to /version7.info.
- Ensure that Settings\Updates\EnableCheckForUpdates is set to 1 (Enable).
- You may also set any of the following settings, as desired:
The actual check for updates is triggered only when the client software is launched interactively. For example, when the client is launched in Explorer or Finder with a double-click, the check will occur, however when it is launched via a scheduled task, the check will not occur. If using a script or a command prompt to launch the client, it must not include the jobmode or taskmode switches - those switches will prevent the check from executing.