Remote Updates

Updating your players on remote may be necessary, especially when you have more than a couple of players, or if you have no way of administering them on remote.

To help you with remote updates we have created a update script that can be compiled using NSIS (Nullsoft Scriptable Install System).

Script

The script is to be downloaded at the end of this article, and can be customized to make other changes to the registry, replace files or some other maintenance on the player.

When run, the script will stop, update and restart your current Dise software on the player. Refer to the NSIS User Manual and contact support for more information on how to customize this update script.

Compiling the script

When compiled the script will produce a file called for example 'diseupdate2006Feb28.exe', the date is added so that you will not mix up the versions. This file can then be run on any player/manager/monitor with a complete Dise installation, be default the script will show an user interface and let you manage any running applications and so on. If executed with the parameter /S the script will run silent and close down any running Dise applications automatically.

Distribution

Note: Before distribution, make sure that Dise Probe is setup to execute remote system updates.

Rename the output exe file to 'diseupdate.exe'. Next, either:

• Use Dise Bridge to distribute the file to the destination - add the file using the Additional Files dialog
• Manually put it somewhere on your file server.

Probe will download the file and execute it with the parameter /S. It is recommended to keep the update file in the destination directory since this will enable any new players or not-updated players to run the update at a later stage. When you then create yet another update you replace the old one and Probe will recognize this as a new file and then download the file and execute the new update.

Probe will also execute files called 'diseupdate.bat' or 'diseupdate.vbs', both with the flag /S.

Note: It is very important to test the update before sending it to the actual players, since a small error in the script can cause problems in your system and stop players. While testing an update it is recommended to do that from clean ghosted player machine, so that any special behavior can be detected. At first you can run the update manually to check that it works, but later on you can test is through a test setup in Probe to make sure that the file is downloaded and executed as expected.

Download

Contact support to get access to the update script.