WARNING: the following method is unsupported and should only be used by experienced staff who understand and can program in XML and XPath. Use at your own risk. Make sure to test your changes thoroughly before deploying to production.
As enterprise administrators it is sometimes required to push out new settings to hundreds of conference room computers. For this purpose, Quicklaunch supports importing QLT (room template files), QLS (settings files) and QLS/CSV files for this purpose. However, if only one or two settings values need to be changed, then Quicklaunch can read a QLX file and process XPath statements to update settings files.
- Create a QLX file of XPath statements and values (see below for details)
- Push the file to the conference room computer and place in the C:\ProgramData\QuickLaunch\Import folder
- Issue a restart
- When Quicklaunch starts, it will read the QLX file and apply the individual settings ONCE. Then it will rename the QLX file to .bak
- If there are any errors, Quicklaunch will pop up a red error message. The error details will be in the event log.
The QLX File
The QLX file contains XPath statements followed by a comma, then followed by settings value. One Xpath statement per line in the file. The Xpath statements are constructed based on the Quicklaunch settings Xml file.
Here are a couple of examples:
//Settings/Account/AllowChangeUser,false //Settings/Actions/ActionGroups/ActionGroup[Key="Group_3"]/Name,Start Applications
The first statement will set the AllowChangeUser to false.
The second statement will set the name of the "Launcher" action group to "Start Applications"
These must all be put into one file (QL will only update from one QLX file each time it starts).
The file type *must* be ".qlx"
The qlx file is used only for simple changes to single values. Any more complex XML editing will have to be done through a scripting language, such as powershell.
- test your changes thoroughly before deploying to production
- test quicklaunch with the new settings changes thoroughly before deploying to production