This is a list of recommended activities for deploying and configuring Quicklaunch for Enterprises. A number of the activities are general in nature, as each site has their own tools, policies and procedures.
Note: this information only applies to version 4 or greater of Quicklaunch using the MSI installer.
Preparation
Licenses
It is recommended that you have a single license key with multiple activations. This will eliminate the need to configure a license for each room.
Room Accounts
Each room typically uses its' own room AD account that has its' own Exchange or Google calendar. These room accounts need to be set up prior to deploying Quicklaunch. Accounts do not need to be local admin.
Creating Settings for Each Room
Quicklaunch keeps all its' settings in a settings file in the ProgramData folder of conference room computer. Each room will have many common settings (license, domains, calendaring, action tiles, room reset, theming, logos, etc), as well as room specific settings (room name, room account, etc.).
Quicklaunch has three methods that can be used to create the settings file for each room:
(1) Bulk Creation of Quicklaunch Settings Files with the Quicklaunch Settings File Generator
It is recommended you install Quicklaunch on a test computer and set up a master settings file of all the required Quicklaunch settings (license, domains, calendaring, action tiles, room reset, theming, logos, etc).
Then, with the Quicklaunch Settings File Generator it will create each room settings file based on this master settings file (see above) and a CSV file containing the room specific information. See Quicklaunch Settings File Generator for more information.
(2) Import a template section
You can create a Quicklaunch template section for each room that contains just the specific room information. See How do I create, export and import a room template? for more information on creating room templates and see Quicklaunch Administrative Updates for information on how to import sections into Quicklaunch.
(3) Use Xpath to edit the settings file
It is recommended you install Quicklaunch on a test computer and set up a master settings file of all the required Quicklaunch settings (license, accounts, domains, room name, calendaring, action tiles, room reset, theming, logos, etc). See How do I create, export and import a room template? for more information on creating room templates.
If you are well versed in XML and Xpath, you can create an Xpath edit file to custom edit the Quicklaunch Settings file. See Offline Editing of Settings for more information.
Installation
Upgrade from Quicklaunch V3 to Quicklaunch V4
Quicklaunch V3 uses Microsoft's ClickOnce deployment technology. Quicklaunch V4 uses MSI. To upgrade from V3 to V4 without user interaction (e.g. upgrade via SCCM or InTune) requires specific steps. Please see Silent Upgrade from Quicklaunch V3 to Quicklaunch V4
Installation
The Quicklaunch MSI can be pushed from SCCM, Intune or from a central management tool that supports MSI. See MSI Installer for options on using silent install.
Elevated Privilege During Install
Elevated privileges are required during installation for the program files, setting up registry entries, setting up scheduled services (for update and lockdown) and for setting up event logs. The Quicklaunch Room Account does not require admin privileges.
Pushing the Settings to Each Room Computer
Depending on the option selected above for creating your settings file, there are different options for pushing the changes to your room computer:
Method used to create settings file | Options to push settings to each room computer |
| Quicklaunch Settings Generator | (1) copy each generated room setting file to the C:\ProgramData\UC Workspace\Quicklaunch folder as "QuickLaunchSettings_V2_0.xml" (no conversion of xml required, just rename the extension). Then restart Quicklaunch. (2) copy each generated room setting file to the C:\ProgramData\UC Workspace\Quicklaunch\Import folder as a QLS file. Then restart Quicklaunch. NOTE: for import t o work you must have settings->System->General->"Use Import File for Silent Install" enabled. |
| Import a Template Section | Copy the template section to the C:\ProgramData\UC Workspace\Quicklaunch\Import folder and restart Quicklaunch. See Silent Install for more information. |
| Use Xpath | Copy the QLX file to the C:\ProgramData\UC Workspace\Quicklaunch\Import folder and restart Quicklaunch. See Offline Editing of Settings for more information. |
Application Updates
Quicklaunch has an automatic update that can be enabled through the Quicklaunch settings. If you choose not to use the built-in automatic update, you can update Quicklaunch by installing a newer version of the Quicklaunch MSI. All settings files will be preserved.
Machine Replacement
If a computer needs to be replaced or re-imaged, Quicklaunch can be installed remotely with the above procedures. If the computer is restored from a master image, the account and room name (as well as other room specific settings) may need to be updated. This can be done through the custom settings for each room (see above) or by manually altering the settings.