Q-SYS Connect
Q-SYS Connect is a Windows-based software application that enables multiple use cases for the integration of Q-SYS systems with third-party products and notably Windows-based UC room systems.
Security Considerations for Q-SYS Connect
Use Q-SYS Connect with Secure Communication enabled. Q-SYS Connect is designed to support Secure Communication to maintain end-to-end encrypted and trusted communication paths across the Q-SYS system. Q-SYS recommends enabling Secure Communication on supported components so that the introduction of Q-SYS Connect does not require customers to reduce their existing security posture.
When integrating Q-SYS Connect with Windows-based UC meeting platforms such as Zoom Rooms or Microsoft Teams Rooms (MTR), Q-SYS strongly recommends following each vendor's published best-practice guidance for securing meeting environments, system access, and room compute devices.
Recommended Best Practices
Secure the Windows Room Compute Environment
The Windows device hosting the UC platform and the Q-SYS Connect Taskbar application must be secured according to your IT policies. This includes:
-
Keeping the OS updated with current security patches.
-
Enforcing strong authentication and access policies.
-
Limiting local administrator access.
-
Ensuring antivirus / endpoint protection is active.
Follow Zoom Rooms Security Guidance
For Zoom Rooms-based deployments, Zoom provides detailed guidance for protecting meeting environments, managing authentication, reducing disruption risks, and maintaining a secure room experience. Please follow Zoom's recommended practices for securing meetings and device configurations.
Follow Microsoft Teams Rooms (MTR) Security Guidance
For Microsoft Teams Rooms deployments, Microsoft provides comprehensive security guidance to help ensure that Teams Rooms on Windows and Teams Rooms on Android devices operate within a protected and well-managed environment. Be sure to review Microsoft's recommended practices for securing room compute devices, managing authentication, applying the appropriate security baselines, and controlling device-level access and meeting behavior.
These recommendations cover how Teams Rooms devices are secured by default, how to maintain compliance with organizational policies, and how to harden the environment against unauthorized access or misuse. For the most current information, refer to Microsoft's official security guidance.
Microsoft Teams Rooms on Windows and Teams Android Device Security
About Zoom Rooms Integration
For Windows-based Zoom Room systems, Q-SYS Connect enables the Q-SYS TSC-101-G3 touch screen controller to operate as a native, certified Zoom Room controller.
Q-SYS Connect is included in the Inventory, in version 10.2 to help you plan your system design today. Full download availability and support will roll out in an upcoming 10.2 hotfix, unlocking the complete Q-SYS Connect experience.
About Microsoft Teams Rooms (MTR) Integration
For Windows-based Microsoft Teams Rooms, Q-SYS Connect allows system designers and AV / IT administrators to enable Q-SYS Control integration. This replaces the legacy Q-SYS Control for MTR application and introduces new features such as built-in device discovery for more seamless integration into Q-SYS designs.
Note: As of Q-SYS Designer 10.2, Q-SYS Control for Microsoft Teams Rooms has been moved to Discontinued status. System designs should transition to using Q-SYS Connect and its Microsoft Teams Rooms control integration features beginning in Q-SYS Designer version 10.2.1.
The legacy application, Q-SYS Control for Microsoft Teams Rooms remains available for use, but is planned for full deprecation in future Q-SYS Designer versions.
Q-SYS Connect TSC Integration Behavior When the Virtual Display is Not Active
Device ID Toggle
The Device ID toggle for Q-SYS Connect only has an effect when a virtual display session is active on the supported Q-SYS TSC‑101‑G3 for Windows‑based Zoom Rooms systems. If the virtual display is not available, the toggle remains visible in Q‑SYS Designer, but has no visible effect until the virtual display is active on the supported TSC.
The full setup workflow—including enabling the TSC, configuring the Windows room compute, and presenting the Zoom Rooms interface is documented in the Q‑SYS Connect Setup Guide, in the Q‑SYS Knowledge Base.
Q-SYS Connect Task Bar Application
The Q-SYS Connect Task Bar application runs on the Windows room compute. It enables Q-SYS device discovery and provides basic configuration to system administrators and designers to integrate Q-SYS Connect within a Q-SYS system design.
Key Settings:
Network Name
Text identifier used by Q-SYS Designer to associate a Virtual UC Controller subcomponent with the Q-SYS Connect instance running on the room compute.
Network Adapter
Network interface used for Q-SYS device discovery and communications with a Q-SYS design.
For installation steps and Zoom Rooms configuration, see the Q-SYS Connect Setup Guide in the Q-SYS Knowledge Base.
Q-SYS Designer Properties for the Q-SYS Connect Component
The Q-SYS Connect component in Q-SYS Designer is organized into three subcomponents:
-
Properties - configuration settings, graphic properties, room system information, and script access.
-
Status - real-time operational state of the component.
-
Control Pins - input and output pins for scripting, automation, and UCI logic.
Note: Before adjusting these properties, be sure to walk through the end-to-end setup in the Q-SYS Connect Setup Guide, in the Q-SYS Knowledge Base.
Properties
Name
The Name may contain ASCII letters 'a' through 'z' (case-insensitive), the digits '0' through '9', and the hyphen. Names cannot begin or end with a hyphen. No other symbols, punctuation characters, or blank spaces are permitted.
Location
User-defined name that groups the component with other components in the same physical location, or in the same organizational scheme.
Is Network Redundant
Select whether the device is connected to redundant networks.
Is Required
When enabled, and the device is not found on the network, the device is reported as 'Missing', which is an error condition. This is the default behavior. When disabled, and the device is not found on the network, the device is reported as 'Not Present', which is not an error condition.
Verbose
Enables additional diagnostic information in its Status component.
Room Type
Identifies the unified communications platform and room profile running on the Windows compute device that hosts Q-SYS Connect.
Enable UCI Control
Turns on or off the “Second Page Experience” / UCI integration for the selected Room Type.
UCI Assignment
Defines how a UCI is associated with the UC app, when Enable UCI Control is set to Yes.
UCI
Specifies which UCI from the design is presented on the UC platform’s controller interface when UCI integration is enabled.
Graphic Properties
Label
User-defined text that appears next to the component on the Schematic. Changing the label does not affect the component name or system behavior.
Position
Specifies the X and Y coordinates of the component on the Schematic. The values update automatically when you move the component, and can be edited to place the component at an exact location.
Fill
Sets the background color of the component block on the Schematic. This is for visual organization only and does not affect system operation.
Script Access
Code Name
Displays the currently assign name for control access. You can use the auto-assigned name or customize it. Q-SYS will automatically check all Code Names in the design to ensure name is unique.
Script Access
Defines whether the component will be accessible by script and/or externally, or not at all. Choices include All, External, None (default), and Script.
- None (default) - Not accessible by any script, plugin, or by Q-SYS Remote Control Protocol (QRC).
- Script - Can be accessed by scripts, such as Text Controller, Block Controllers, and plugins only.
- External - Can only be accessed by 3rd party controls systems using component commands from the Q-SYS Remote Control Protocol (QRC).
- All - No restrictions, can be accessed by 3rd party control systems via Q-SYS Remote Control Protocol (QRC), or script objects or plugin objects.
Tip: Use Script Programmer Mode to quickly view the Script Access setting directly on the component in the design schematic without the need to disconnect from the Q-SYS Core processor.
Room System Info
Discovery Name
Read-only field that displays the discovery name advertised by the Q-SYS Connect TaskBar App on the Windows compute device, for Room Manager use. This value matches the component’s Name property in the design.
Room Type
Read-only field that displays the detected room system type for this device, for example, Zoom Room. Intended for Room Manager use. This value matches the Room Type property configured for the device.
Monitors Active (LED)
LED indicator that is lit when the Windows compute device is awake and its monitors are active. The LED is unlit when the compute is asleep or its monitors are inactive.Use this to confirm that the room system UI should be visible on the virtual display.
Identify Device Behavior
In Q‑SYS Designer / Q‑SYS Core Manager, the Identify Device toggle for a Q‑SYS Connect room compute remains visible even when no virtual display session is active on a supported Q-SYS TSC‑101‑G3 touch screen. In this state, turning the toggle on has no visible effect; on‑screen identification only occurs when a virtual display is running on the supported TSC.
Wake-up
LED indicator that indicates the state of the wake-up input pin on the Status component. When the pin is asserted, the LED lights show that an external control signal is requesting the compute to wake up.
Status
Component status is conveyed with the Status LED and Status box, which uses both color and text to indicate the current condition:
- OK: The device is functioning normally.
- Initializing: The device is in the process of a firmware, patch, or configuration update, or the design is starting.
- Compromised: The device is functioning, but a non-fatal problem exists. Refer to the Status box for details.
- Missing: The device cannot be discovered.
- Fault: The device is malfunctioning or is not properly configured. Refer to the Status box for details.
- Unknown: This status appears during a Core reboot (for example, during a firmware update), or when a design is being uploaded to the Core and before it has started running.
- Not Present: If applicable to the device, this status appears when the device is not connected to the network and its Is Required component property is set to 'No'. This status also appears if the device component's Dynamically Paired property is set to 'Yes', pairing has not been assigned in Core Manager, and the device component's Is Required property is set to 'Yes'. See Dynamic Pairing.
Control Pins
| Pin Name | Value | String | Position | Pins Available |
| Wake-up |
0 1 |
false true |
0 1 |
Input |
| Current Discovery Name | N/A | Current discovery name shown by the Q-SYS Connect TaskBar app. |
0
|
Input / Output |
| Current Page | 0 | Name of the currently selected page of the assigned UCI. |
0
|
Output |
| Current Room Type | N/A | Current room type reported by the compute. |
0
|
Output |
| Current UCI |
0
|
Name of the UCI currently assigned to the room system control app. |
0
|
Output |
| Display Active |
0 1 |
false true |
0 1 |
Output |
| Display Off |
0 1 |
false true |
0 1 |
Output |
| Display On |
0 1 |
false true |
0 1 |
Output |
| Hide UCI |
0 1 |
false true |
0 1 |
Input / Output |
| IP Address | Read-only | IP address or host of the Zoom Room compute discovered by Q-SYS Connect. | 0 | Output |
| Q-SYS Connect Status |
0 1 |
0 1 |
0 1 |
Output |
| Remote Status |
0 1 |
false true |
0 1 |
Output |
| Show UCI |
0 1 |
false true |
0 1 |
Input / Output |
| UCI Visible |
0 1 |
false true |
0 1 |
Output |
