Endpoint Management
| Configuration Name | Description | Default Value | Tag |
|---|---|---|---|
| Controller Discovery | If the value is set as true, then HyDesk can discover the HyWorks Controller in the network. This is also controlled from System > Service config > Discovery Settings. Broadcast port is used as configured in Advance config > Controller Discovery Port (default: 39003) |
False | - |
| In session, HyDesk heartbeat timeout multiplier | HyDesk Heartbeat interval increases with this set multiplier. | 3 | Heartbeat |
| Deliver Applications to Client Version Onwards | Client with version and above supports Application delivery | 300000 | - |
| Define/Specify the device time zone | Specify the timezone to be enforced on HyDesk. | IST | - |
| Enforce time zone | Enforce the time zone for HyDesk. Expected values: True or False, Default value: False | False | - |
| Stop Controller-HyDesk Date Sync | If this is set to true, HyWorks Controller will stop sending the Date to HyDesk during the registration call, and HyDesk will stop syncing the date with the controller. | False | HyDesk |
| Heartbeat Interval | All endpoints use this interval to communicate with the HyWorks Controller; any relevant endpoint configurations can be set using this heartbeat interval. In large deployments with too many desktop clients, the heartbeat interval can be increased to improve the performance overhead of processing heartbeats from too many endpoints. Note: Increasing the heartbeat interval causes longer gaps in communication with endpoints, so any settings changed on the controller will take effect according to the configured interval. |
40 | Heartbeat, Interval |
| In Session HyDesk Heartbeat Timeout Multiplier | With user-logged-in, heartbeats are also used in this configuration to increase the default heartbeat time, which means if a device with no user logged-on sends a heartbeat in 40 seconds, the same device with a user logged-on will send a heartbeat in 40 * 3 (Consider the multiplier is set as 3) = 120 seconds. | 3 | Heartbeat |
| Heartbeats Allowed to be missed | This value configures the number of missed heartbeats allowed; beyond that, HyDesk is marked as disconnected. | 3 | Heartbeat |
| TCP user timeout | The TCP user timeout controls how long transmitted data may remain unacknowledged before a connection is forcefully closed. Value in Second, Default value is 9. | 9 | RDP |
| KeepAlive interval | Keepalive interval is the duration between two successive keepalive retransmissions if acknowledgment of the previous keepalive transmission is not received. Value in Second, Default value is 2. | 2 | RDP |
| KeepAlive count | Keepalive count is the number of retransmissions to be performed before declaring that a remote connection is unavailable. Value in Second, the default value is 3. | 3 | - |
| KeepAlive idle | Keepalive Idle is the duration between two keepalive transmissions in an idle condition. Value is in Seconds, Default value is 5 seconds. | 5 | RDP |
| Disable HyDesk Activity Monitoring | By default, endpoints send timer details whether any user activities are present, but in cases where the user has logged in, is active on the desktop, but not accessing any desktops/ applications. In such cases, HyWorks uses this flag to determine whether to consider information sent by endpoints indicating that the user is active. It should be kept as true as HyWorks will then ignore user activeness details from clients with no desktops or apps accessed. | True | - |