How does the Uniprint Package Automatic Update Module work?

The following article explains the Automated Package Update Module and its operation.

Operation

1. When  a new package is created, the Uniprint Web Site manifest.xml file is updated to reflect an update or change .

2. If the automatic updater is installed with the original package, it runs as the ‘system’ user and upon first print checks the manifest.xml file for the update frequency.

3. If more than the specified amount of time has passed since it last checked, then it will check the Uniprint Web Site. The updater reviews the manifest.xml to determine if anything has changed (version number or checksum, depending on the type of module).

4. If an update has occurred, the updater downloads the smaller package installer that is created during the package creation process.

5. The package updater then runs the small package installer, which draws the larger update file to the PC from the server.

6. When the file is completely downloaded the full package is run and the local computer updated.

Items that are Updated

• package contents, hot fixes, updated popup and notify components

• drivers 

• configuration settings (dependant on driver)

• custom packages

Pre-requisites

The site must have originally deployed the updater with the first package for the PC to be updated.

Known Issues/Limitations

• If the update interval was originally set to a very high value (when it was first installed on the client), then the updater won't run until that period has passed (even if you change the settings in Pharos Administrator). You can force it to recheck if you need to by editing the registry (Updater > Update Interval) - this value is in seconds.

• The updater will not update driver settings changes on some drivers.