Quicklaunch Administrative Updates

Administrators now have the ability to update Quicklaunch Settings or Templates via a directory on the local computer. Place a QLS file in the import directory and the next time Quicklaunch is restarted the settings will be applied.


Ability to apply individual setting section updates

Quicklaunch Administrative Updates provide the ability to update specific sections of the QLS settings file. The sections to be imported are described in a simple csv format descriptor file. This feature allows administrators to update passwords, licenses, or themes remotely – without modifying distinct installation settings like room name.


Administrative Update Options

  1. Apply a template.

  2. Apply an entire Quicklaunch Settings file.

  3. Apply a partial Quicklaunch Settings file using a section descriptor file.


How To: Apply a template using the Administrative Update

  1. Create a template using Quicklaunch.

  2. Copy the template to C:\ProgramData\Quicklaunch\Import on each machine that you would like to apply the template.

  3. The template must have an extension of .qlt but you may choose any file name that you like.

  4. Restart Quicklaunch.

  5. The template is applied on start-up and the template that was imported is renamed to filename-date-qlt.bak

  6. Quicklaunch checks the import folder on every start-up. If it finds a file with a .qlt extension that template will be applied. It is therefore not advised to store historical copies in this folder unless they have been renamed.


How To: Apply an entire Settings file using the Administrative Update

  1. Create a QLS settings file using Quicklaunch.

  2. Copy the settings file to C:\ProgramData\Quicklaunch\Import on each machine that you would like to apply the settings.

  3. The settings file must have an extension of .qls but you may choose any file name that you like.

  4. Restart Quicklaunch.

  5. The settings are applied on start-up and the settings file that was imported is renamed to filename-date-qls.bak

  6. Quicklaunch checks the import folder on every start-up. If it finds a file with a .qls extension that settings file will be applied. It is therefore not advised to store historical copies in this folder unless they have been renamed.


How To: Apply specific Settings sections using a descriptor file

  1. Backup all your room settings 

    1. Go to settings,

    2. Click export

    3. select backup all settings

    4. this will create a .qls file

  2. In notepad, create an import descriptor file.

    1. the file can have any filename, but it must have a file type of ".csv"

    2. inside the file it will contain a list of settings "sections", and a yes or a no if you want to import that section

    3. the following example will import only the Display and Actions sections

License,No

Account,No

Display,Yes

Actions,Yes

Theme,No

Calendar,No

System,No

  1. Place the ".qls" settings backup and the "import descriptor" (csv) file into the Quicklaunch import directory (usueally this is C:\ProgramData\UC Workspace\Quicklaunch\Import

  2. Restart Quicklaunch.

  3. The setting section(s) that you selected in the descriptor are applied on start-up. The settings and descriptor files are renamed to filename-date-qls.bak and filename-date-csv.bak

  4. Quicklaunch checks the import folder on every start-up. If it finds a file with a .qls extension that settings file will be applied as well as any .csv file (descriptor). It is therefore not advised to store historical copies in this folder unless they have been renamed.


Why are there warning files in my Import directory?


If Quicklaunch detects multiple valid import files in the import directory it will process the most recent valid file and rename the remaining files. When this occurs Quicklaunch will leave a text file in the import directory. These are for support purposes.

If you have single valid template (.qlt) and a single valid setting file (.qls) in the import folder Quicklaunch will apply the settings file and rename the template. The QLS setting file will always take precedence over a template.