Deploying Quality Window in a Terminal Server environment

The following is a list of recommendations on how one might deploy Quality Window for use in a Microsoft Terminal Server environment. Some of it may also apply to other systems such as Citrix.

Quality Window would be installed on the Terminal Server using the built-in Add Program functionality. When asked to insert a CD, just browse to the downloaded Quality Window Install program. Once installed, shortcuts on the desktop wil have been created (for all users). The administrator would then remove the shortcuts for any user that access to Quality Window would not be required, or would be restricted from using it.

Typically, all QW data files are stored on one or more external dedicated file servers. Folders on these servers  would then be shared and mapped drives created on the Terminal Server side, based on the user logon. Administrative rights could also be set on these shares based on the user.

Note that in Terminal Server, all users share the same registry hive. Settings made by one user will affect all other users. We would suggest administrators make global changes, and then lock down the registry so individual users do not affect other user’s settings.

Licensing can be either single standalone license or use QWLicenseServer:
– If using a standalone license, then a methodology must be in place to restrict the number of QW accesses to the number of standalone licenses in ownership. Failure to do this would be in violation of our licensing agreement.

– If using QWLicenseServer, the license server can either be installed on the terminal server itself, or on an external server. QWLicenseServer uses the client’s computer name and logon name as a key to its licenses, meaning that if you allow the same user to log into Terminal Server at the same time, QWLicenseServer will treat this as a single license, which is in violation of our licensing agreement. The administrator must disable multiple logons in Terminal Server in order to comply with our licensing. One way to get around this would be to turn off the flag ‘Allow Duplicates’ in QWLicenseServer, which would treat every QW access as a license. Note that in this mode, if a user opens Quality Window twice on the same workstation/session, they will be using up 2 licenses.

If users on the terminal server will be in different time zones, then the policy needs to be changed for each user as to their specific time zone settings.
http://technet.microsoft.com/en-us/library/cc783386(WS.10).aspx

Making use of Quality Window Directory Files could greatly improve the user experience, since users would then be restricted to a predefined number of Quality Window applications (on a per user basis). QW Directory Files can be created and managed using the QWAdmin application.






Try Quality Window 5 (QW5)

Collect, visualize, analyze and react to your process data so you can increase efficiencies across the manufacturing floor.