Run UpdateManager "silently"

Last change: Jan 24, 2018

Article refers to SYMplus plusCare only, not valid for SYMplus 6.0 oder older versions

1. Silent Mode expects the latest updates to be available for offline update on your server. How to do that is described here, (Chapter Offline-Update, German only).
2. For an update in silent mode the update manager needs a special config file. This file determines where the update files are located, where the program and user data of the KELLER software are installed and where a corresponding log file should be stored at the end of the update process. For example, such a config file might look like this (q: is the "network drive" where the offline update is located, de in kellerplusde stands for Turning (Drehen) English in this example):
   
   update-url=q:\updates\355
   system-dir=c:\program files (x86)\keller\kellerplusde
   user-data=%appdata%\keller\kellerplusde\datasd
   log-file=q:\updates\silent-update.log
   
   
3. Then call up the Update Manager via "UpdateManager silent=silent.cfg", whereby you naturally specify the name of the corresponding config file in "silent.cfg". You can create different config files for turning and milling or, if there are several users on the same PC, also vary the user data. The start of the update manager must of course be done with admin rights, the update manager itself calls no admin rights in silent mode (otherwise you would have to go back to the affected PC and confirm the appropriate dialog).
4. The actual update then runs without further user intervention. However, it is not really "silent", which means a few dialogues will appear on the affected PC, informing about the progress. A completely invisible update would have been too laborious to develop.
5. After the update, you can check in the log file what the update manager did and if everything worked. If more than one log file is created, it is automatically "numbered". There is (consciously) no feedback about the exit code, since under certain circumstances the update manager will be restarted during the update (if there is an update for this tool itself, for example).