Features & Enhancements
This section in release notes, provides the details of new features and enhancements in HyWorks v3.3-R2 release.
Enhancements in HyWorks Controller
Built-in Automatic Power Management for dynamically deployed Session Host Servers (Teams)
Power management finctionality for dynamically deployed session host servers on Microsoft Azure was introduced in previous version and required Azure based configurations. From this version, support of two more provides - Nutanix AHV and VMware vCenter Server is added.
The automatic power management capabilities are brought to HyWorks Controllers by implementing following two services:
- Accops Scheduler
- Accops Action Processor
The modules will help in achieving:
- Automatic deployment or deletion of session host servers as per schedules
- Automatic power management of sessions host servers as per schedules
Refer for details.
Network Preserve option for Course Reservations in HyLabs
From this version, Network Preserve functionality is supported even in HyLabs. This will allow to preserve the network configuration in HyLabs even when Course reservations are destroyed or redeployed. Till previous version, it was required to reconfigure the network as HyLabs deployments required network configuration - MAC Addresses in case of Nutanix/ VMware and network object for Microsoft Azure. Only course reservations with option Reuse VMs for each run of reservation enabled, will be able to use network preserve feature on re-deployments of reservations. Currently this feature is not supported for:
- Self-study reservations
- Course self-study reservations
- Course reservations which deploys VMs for all schedules (Reuse VMs for each run of reservation option is disabled)
Support of high heartbeat interval for Session monitoring
HyWorks session monitoring process now supports higher heartbeat intervals of HyWorks endpoints. This will reduce dependency on heartbeats for user sessions and overhead of processing too many heartbeats.
Following settings in HyWorks Controller Management Console will define session monitoring mechanism
System > Advanced Configurations > HyDesk User Session Idle Monitoring
- HyDesk User Session Idle Monitoring = 1: HyWorks will consider HyWorks client heartbeats for user session monitoring. The behavior will be same as previous versions.
-
HyDesk User Session Idle Monitoring = 2: HyWorks controller will start idle session monitoring, when no desktop or app sessions running. Endpoint heartbeats will not be needed and can be increased as required.
- This will help in reducing load due to too many heartbeats from endpoints.
UI Changes
Controller to display Release Tag
From this version onwards, HyWorks Controller release tag will be displayed at:
- Management Console > Server > HyWorks Controller Page > Version Column
- At the bottom strip, beside HyWorks Controller Date/Time
Add Application Wizard - Label change
Label for the button to navigate to application binary location is changed from Get details automatically to Browse Application Details.
Column Value of Pool Type, Assigned Client and Client Type in Desktop VMs Page
For provisioned session host server, visible in Desktop VMs page, following column values are changed for better understanding:
- Pool Type: Shared Hosted Desktop - Dynamic
- Assigned Client: NA
- Client Type: Multi-User
New Columns - Session Teams
New columns are added to provide details of a managed session team:
VM Status: Suggesting the status of session host server VM:
| SHD VM Status | Status on Desktop VM Page |
|---|---|
| Unknown | - |
| Provisioning_Failed | Sysprep failed / Encryption Failed |
| Not_Provisioned | Un-provisioned / Missing |
| Provisioning | VM creating / Recomposing / Sysprep not completed / Encryption Not complete |
| Powering On | (Sysprep completed OR not required) && (Encryption complete OR not required) |
| Powered On | Powered_On |
| Shutting Down | Shutting_Down |
| Powered Off | Powered_Off |
| Rebooting | Rebooting |
| Suspend | Suspend |
Server Status:
| SHD VM Status | Condition |
|---|---|
| Unknown | - |
| Ready | Provisioned + SHD Agent Responding + Powered On [Un-cordoned] + Active+ Connectivity |
| Draining | Provisioned + SHD Agent Responding + Powered On [Cordoned] + Active+ Connectivity |
| Not Ready | - |
Removed dropdown for Log Type from Logs Page
Link from Desktop Pools page to Session Teams Page
Name of desktop pool (Dynamically provisioned shared hosted) in Desktop Pools page will function as a link and will navigate the user to Session Teams page directly.
Session Host Changes
All the latest supporting modules are integrated
- Accops User Experience Manager (AUEM): Version 3.0.0.124
- Accops Session Server Extensions (HyPrint, Light Speed Printer, File Transfer): Version 3.3.1.12
- Accops Session Recording: Version 1.0.2.45
Manage session disconnection through Registry basec control
Till previous releases, session host server used to keep the session running for which it failed to communicate with HyWorks Controller and the sessions were getting disconnected without any notifications, when controller was performing cleanup of such sessions. To handle this situation registry based control is provided that will let you configure force logout time for such unmanaged sessions.
- Location: HKEY_LOCAL_MACHINE\SOFTWARE\Accops\Controller\EDC\SESSIONHOST
- Registry Name: ForceLogoutUnmanagedSession
- Registry Type: String
- Registry Value:
- True: Logout the user as per timeout set for registry ForceLogoutUnmanagedSessionInMin. Also prompt user for session logout
- False: Keep the session and do not prompt any message
- Registry Name: ForceLogoutUnmanagedSessionInMin
- Registry Type: String
- Registry Value: Valid positive number. User sessions to be logged out as per provided value when ForceLogoutUnmanagedSession is set as true.
!!! important Keeping **ForceLogoutUnmanagedSessionInMin** value too high does not mean that sessions will be kept for longer duration. The sessions may still be cleaned up as per HyWorks Controller configuration to cleanup failed sessions.
Option to suspend processes on session disconnections
New session host server is having feature integration to suspend user processes in disconnected sessions.
How will it work:
- On session disconnection, session host server will suspend processes
- On session reconnection, suspended processes will be resumed
How to enable:
To enable process suspending, following registry has to be enabled:
- Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Accops\DVMAgent\SUSPEND PROCESS
- Registry Name/ Type: Enable (String)
- Registry Value: Set as True to enable process suspending/ Set as False to disable process suspending
HyshellServerPreScript and HyShellServerPostScript will now run in User context instead of System context
DVM Tools Changes
Following integrations are there in DVM Tools being released as part of v3.3-R2:
All latest supporting modules integrated
- Accops User Experience Manager (AUEM): Version 3.0.0.124
- Accops Session Server Extensions (HyPrint, Light Speed Printer, File Transfer): Version 3.3.1.12
- Accops Session Recording: Version 1.0.2.45
Option to suspend processes on session disconnections
New desktop agent is having feature integration to suspend user processes in disconnected sessions.
How will it work:
- On session disconnection, session host server will suspend processes
- On session reconnection, suspended processes will be resumed
How to enable:
To enable process suspending, following registry has to be enabled:
- Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Accops\DVMAgent\SUSPEND PROCESS
- Registry Name/ Type: Enable (String)
- Registry Value: Set as True to enable process suspending/ Set as False to disable process suspending