Notes:

This page is outdated: See current setup scripts

For ConSys install on a new computer: See ISA OneNote, Controls|ConSys|Installation|ConSys PowerShell installation instructions

Most computers include a copy script to copy new ConSys code to all instances on the computer and is found in the "ConSys Setup" folder on the desktop. The script name typically starts "GenericCopy..." or "Copy..." and ends with ".cmd-Shortcut". On these computers, to update all instances follow the instructions below. On computers without this script - or if a single instance update is wanted, follow the Consys alternative update method

Updating all ConSys instances to the newest available ConSys version:

• Open 'ConSys Setup' folder found on the desktop
  
• Stop all ConSys programs - including programs using CsAPI
• Stop 'ConSys Kernel' service(s) (or the ConSysloader program if run as application)
  • Start Service manager, 'Services' ('Run as administrator' if not logged in with local administrative permissions)
    • Open 'Services' found in the 'ConSys Setup' folder
  • Stop 'ConSys Kernel' service(s) for all instances:
    
  • Wait until the service(s) is stopped. If a service is not stopped within 2 minutes: Kill it from the task manager or reboot computer and start from the top again
• Copy the new version of the ConSys executables:
  • Run the Copy script found in the 'ConSys Setup' folder. The name of shortcut to the script depends on the script needed for the specific computer, but typically starts "GenericCopy..." or "Copy..." and ends with ".cmd-Shortcut"..
    • The install script may call other installers to update the Miscrosodt Visual C++ redistributables. In this case, install these as well (there will typical be two installers, one for x32 and one for x64). If restart is required install both and wait with the restart until the ConSys setup script has finished.
  • When the copying is finished two status reports are opened in notepad
    • Check the log files to ensure that all files are copied - if not so it is probably due to a running ConSys application. Close the application and try to run the script again.
• Start 'ConSys Kernel' service(s) again
• Remark: As part of the update, the previous executables and persistent files has been copied to the folder(s) '.\ConSys\old\Previous'. If wanted these files can be preserved by renaming the 'Previous' folder, typical to
  <year><month><day><note>, ex.
  20201224_BeforeXXX
  Remember to clean up/delete older outdated backup folders in the '.\Old' directory.

Last Modified 03 October 2025