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.
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.
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.
It is recommended you install Quicklaunch on a test computer and set up a master room template of all the required Quicklaunch settings (license, accounts, 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.
Custom Settings for Each Room
Each room will likely have room specific settings. Typically the room account and the room name, but there may be others. Quicklaunch has two methods that can be used to created customer settings for each room:
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.
Use Xpath to edit the settings file
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.
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.
Installation with Lockdown Manager
If you are planning to use Lockdown Quicklaunch (AKA Kiosk mode), Quicklaunch must be installed under the Quicklaunch room account. This is to ensure Quicklaunch and the shell are automatically restarted from the proper interactive room account if the computer is shutdown, updated or Quicklaunch process is stopped.
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 File to Each Computer
Using the room template file created above, push the Quicklaunch template file to each computer. See Silent Install for information for details.
Pushing Custom Settings for each Room
Depending upon the technique selected above. Custom room settings are pushed after the template settings file is applied.
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.
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.