Current NCDesk Icon NCDesk

Autoupdate

NCDesk contains a feature that checks to see if it has the latest version of each component. Each time NCDesk is launched it attempts to communicate with a server that knows the latest versions of all of the components of NCDesk.

  1. If NCDesk cannot connect to the server the user is notified and can continue using NCDesk without knowing if there are updates. This situation means that it is very likely that the computer cannot connect to the servers hosting the updates and the test.
  2. If NCDesk does connect and the local components are up-to-date, then NCDesk will continue to launch without any additional messages. This will mean that anyone in this situation should be able to take the test as long as other network and workstation requirements are met.
  3. If NCDesk does connect and finds that there are updates available, then the user is presented with the option of getting the updates.
    1. If the user chooses NOT to get the updates, then they can continue to use NCDesk without the updates, but will not be allowed to begin a test session.
    2. If the user gets the updates, NCDesk stops and will have to be started again. After NCDesk is launched again following updates, there should not be another update notice and you should be able to administer the test as long as other network and workstation requirements are met.

NCDesk component sizes currently range from 2 Kb to 333 Kb with most being less than 80 Kb. Speed of downloading new versions using the Autoupdate feature varies depending on the quality of Internet connectivity and the number and size of newer version components being downloaded.

It is possible that more than one NCDesk restart and downloading of updates can happen. Updating would be complete when the autoupdate dialog no longer appears.

If system administrators or lab managers (whoever is managing lab workstations) allows updates to be applied to NCDesk as they become available, then there may not be a need to apply updates right before testing. It may be as up-to-date as possible. However, if NCDesk is NOT allowed to be updated as updates are made available, then the computers will have to be updated before testing can begin.

Forced Update
To force an update of all NCDesk components, delete the NCVersion.properties file located in the NCDesk directory.

This file was modified on Wednesday, August 29, 2007; at 1:36:38 PM