Question

* How does GUI upgrade work for network installations and profiles?

Examples
1. change of html print template
2. change of print.ini files

Answer

* Print templates are always transferred/updated (to the profiles) when there was a change on the server and the package was re-created by util i/6 Create Print Templates Package for the PC Client
Please do not change any print templates on the PC. This is only a local - and temporary - change.

* A change to ./alephcom/tab/print.ini in the version check directory on the server will be downloaded with the next version check - which is - depending on the configuration either at startup or upon request.

Example:
* If you change $aleph_root/pc_exe/version/circ/tab/print.ini on the server and the client is setup to check this directory on the server, the file will be automatically downloaded to the profiles, if the file on the server is newer than the local file.

Additional Information

How to create the profiles
1. Create a directory for each of the profiles on a network drive
2. Start the AlephADM module of the network client with profile 'default'
3. Add all profiles via menu 'Configuration / Profiles manager' and choose the correct profile directory. Changes specific to the profile will be automatically stored there.
Take a note, that not the complete *ini files are stored here, but only those which differ from the default.
4. Connect to the client with the relevant profile name.

Read more in KCS article "The Aleph Version Check" (KB 16384-21362)

• Article last edited: 10/8/2013