Managing Personal Desktops
The VDI > Desktops > Personal section lists all the personal desktops configured in the desktop pools.
The page enables administrators to perform various administrative tasks, such as power operations and assignment modifications.
The VDI > Desktops > Personal section provides the following information and actions to the administrator:
-
Viewing Desktops and Details
-
Desktop Related Operations
-
Desktop Pool-Related Operations
-
Client Assignment Operations
Each of these operations is explained in detail in this document.
View, Filter, and Export Desktop List
Personal Desktops List
The VDI > Desktops > Personal section lists all the personal desktops with the following details shown in tabular format:
| Column Name | Description |
|---|---|
| Alert | Green indicates no action required. Red alert indicates upgrade pending. |
| OS | The desktop VM's operating system is displayed as a Windows or Linux icon. The information is fetched from the session provider. |
| Desktop and DVMTools Version [VM Version] | Name of the DVM on the session provider and the installed HyWorks DVM agent version on the Desktop VM. In the bracket, the VM version is shown, indicating the current provisioned version. Details of the VM version are available here. |
| IP Address and FQDN | IP Address and FQDN of the personal desktops as provided by the service provider. FQDN information is not available for VMs from Microsoft Azure, Amazon Web Services (AWS), Oracle Cloud Infrastructure (OCI), Nutanix, and Hyper-V. For VMware/vCenter Server: Desktops must have VMware Tools installed to obtain this information. For powered-off or Desktops whose IP and DNS information cannot be retrieved, the display will be ‘NA’ (not available). |
| Pool Name and Display Name | Desktop Pool Name and its display name information in which this Desktop is configured. |
| Pool Type and Entitlement Type | Pool Type: The pool type that indicates the disk type of Desktop VMs, which can be either Persistent or Non-persistent. Entitlement Type: Desktop can be assigned to registered endpoints or users. The field will display possible values, either Device-based or User-based. |
| Assigned Client and Type | Assigned Client: A desktop can be assigned to a user or client, and it displays the assigned client information accordingly, which can be the username or the device name. Assignment Type: A desktop can be assigned permanently or as a floating assignment to a client. The field displays the possible values: Permanent, Floating, On Demand, or Floating-On-Connect. |
| Connection Status | Indicates whether the session is connected or disconnected; possible values are Connected and Disconnected, and the status is displayed using icons. |
| State | DVM's current Power State: powered off, powered on, suspended, not synced, syncing, creating, etc. |
| Network Ready | Checking whether the desktop is configured for a network-ready status check, and, if so, the current connection readiness status. Possible values could be 'Ready' or 'Not Ready'. |
| Agent Status | Displays the HyWorks Desktop Agents status as responding, not responding, or not available. Responding: This indicates that the HyWorks Desktop Agent is running and the HyWorks Controller can communicate with the HyWorks Desktop Agent’s mouse. Not Responding: Either the HyWorks Desktop Agent is not running, or issues are preventing a connection from being established with the HyWorks Desktop Agent. When Agent status is in Not Responding state, then mouse hovering on Agent Status will also display the detailed status with the possible cause of the status. Not available: DVMs in powered-off or suspended state. |
The desktop section provides valuable information on Desktop Virtual machines (VMs). Administrators can also click Desktop Name (which functions as a link) to open the Desktop Details dialog, which displays additional information about the selected desktop.
Filtering Desktop List
HyWorks v3.4-SP2 or later allows administrators to filter the desktop list. The following filtering options are available:
-
Pool Name: Filter by the name of the desktop pool.
-
Pool Display Name: Filter by the display name of the desktop pool.
-
Version: Filter by the desktop version.
-
VM Name: Filter by the virtual machine’s name (VM).
-
IP Address: Filter by the desktop's IP address.
-
DNS Name: Filter by the Fully Qualified Domain Name of the desktop.
-
Pool Type: Dedicated Desktop or Shared Desktop.
-
Entitlement Type: Device-Based or User-Based.
-
State: The states can be - Not Synced, Powered Off, Powered On, Suspended, Powering On, Powering Off, Missing, Syncing, Restarting, Suspending, Resuming, Shutting Down, Creating Desktop, Pending Desktop Creation, Deleting, Recomposing, Saved, Un-provisioned, Not Available.
Viewing Desktop Details
To open the Desktop Details dialog, click on Desktop Name in Desktops > Personal section.
The desktop Details dialog provides the following details of the selected Desktop:
| Section Name | Configuration | Description |
|---|---|---|
| Basic Info | Desktop Name | Name of the Desktop on the Provider. |
| DNS Name | DNS Name as gathered from the Dedicated Session Provider | |
| OS Name | Operating system on desktop VM. | |
| OS Version | Version of the operating system on the desktop VM. | |
| Assigned Client | Name: Device Name or Username assigned to this desktop. | |
| Desktop Status | Current Power State of the desktop. | |
| Connection Status | If connected or not. | |
| Pool Name | The name of the Desktop Pool to which this desktop belongs | |
| Networks | Network configuration of the desktop as collected from the Session Provider. Displaying Adapter Name, MAC ID, and IP Address. | |
| Enable DVM Reset | If reset is enabled on DVM during deployment or not | |
| Restore Point Statue | Name of the restore point if DVM Reset is enabled; otherwise, values may be required or not required. | |
| VM Path | Full path of VM location | |
| Agent Info | Status | Responding or Not Responding |
| Message | Detailed status of desktop, e.g., if Desktop Agent Status is responding, then the message will be Desktop is Ready. If it's not responding, then a relevant message suggesting why the agent is not responding |
|
| Version | HyWorks DVM Tools version | |
| Installed On | Date on which HyWorks DVM Tools was installed | |
| Info Last Updated On | Date and time of the last Desktop Information update. | |
| Desktop Agent Info Version | Version of HyWorks Desktop Agent. | |
| Built-in Driver Inf - | Version number of the Built-in USB redirection driver software installed on a desktop, or displayed as ‘not installed’ if not installed. | |
| Enhanced Driver Info - | Version number of the Enhanced USB Redirection driver software on the Desktop, or 'Not Installed' if not installed. | |
| Customization Inf - | Type of customization, i.e., HyPrep or Sysprep. Status flag of Sysprep, possible values can be: Required: Suggesting customization was performed on the Desktop during provisioning and is needed, but has not yet been run. Running: Customization is in progress. Completed: Customization is completed Not Required: Customization was not enabled while provisioning and thus customization won't be run, when Desktop will be powered on. Unknown: When a Desktop is selected that is not provisioned and is an existing VM from a dedicated session provider. Failed: When provisioning fails on the chosen desktop VM. Completed: If customization is completed. |
|
| Hypervisor Tool Info | Version | Some numbers, such as 9354. |
| Status | As shared by the Dedicated Session Provider, E.g., Running (Current). |
Administrators can use the details above to verify whether the Desktop is ready for user access.
Exporting Desktops List
Administrators can click the Export button to download details of all registered VMs as a CSV file. This feature allows you to choose different encoding types (UTF-8, ANSI, Unicode, Shift_JIS) and select which fields are included in the exported file.
Steps to Export VM Details:
-
Click the Export button shown on VDI > Desktops > Personal page:
-
A dialog will appear, prompting the administrator to select the encoding type and the fields to include in the CSV file.
-
Select Encoding Type: Choose from the following encoding options: UTF-8, ANSI, Unicode, or Shift_JIS.
-
Select fields to export: The following fields can be selected for inclusion in the CSV: OS Name, OS Version, Assigned Client Name, Desktop Status, Connection Status, Pool Name, MAC ID, IP Address, Enable DVM Reset, Snapshot Status, Snapshot Name, Agent Status, Agent Message, Agent Version, Agent Installed On, Agent Last Updated On, Hypervisor Tool Version, Hypervisor Tool Status, Organization Name, Customization Type, Customization Status, Pool Type, Pool Entitlement Type, Eltima Version, Sep Version.
-
-
Confirm Export:
-
Once the desired encoding and fields are selected, click the Export button to initiate the process.
-
Export Completion:
-
A CSV file containing the selected information for all desktops will be downloaded upon successful export.
This functionality provides a comprehensive overview of the desktop environment, enabling easy data manipulation and reporting.
Power Operations
The administrator can perform the following power operations on selected desktops. The power operations will be enabled or disabled as per the current power state of the chosen desktops:
-
The desktop is powered off. Power operations will be enabled in the Power On or Saved state (on Hyper-V only).
-
The desktop is already powered on. Power Off, Shutdown, Restart, and Suspend operations will be enabled.
-
The Desktop is in a suspended state. Resume power operation will be enabled.
Performing Power Operation
To perform any power operation on the desktop(s):
-
Select one or more desktops from the list.
-
Click on the Power Operations dropdown button.
-
Appropriate power operations will be displayed for selected desktops based on their current power state. E.g.,
-
When a single desktop is selected, the available option will be displayed based on the current power state.
-
All power operations will be shown as available if multiple desktops are selected.
-
-
Click the button for the necessary power operations. A mismatch may occur between the desktop VM's power state in the HyWorks Controller and the Desktop's actual power state in the Dedicated Session Provider, such as when suspending.
-
In the Confirm Action dialog box:
-
Provide an appropriate reason for the power operation.
-
Type the power operation as part of the challenge to avoid unintentional power operation.
-
The HyWorks Controller initiates power operation and forwards it to the session provider.
-
Once the initiated operation is successfully executed, the desktop status will be updated on the Desktops > Personal page.
The example above assumes the Desktop's power state is Powered On. The same steps can be used to perform other operations, such as Resume, Restart, Shutdown, and Power Off.
Important
The HyWorks Controller periodically communicates with the Session Provider to obtain updated Desktop status. Sometimes, there may be a mismatch between the desktop VM's power state on the HyWorks Controller and the Desktop's actual power state on the Session Provider. In such cases, power operations may fail because the connector/provider indicates the VM is not in the correct power state.
Hibernate with Azure (termed as Suspend in HyWorks)
HyWorks v3.6-SP1 includes an implementation (further enhanced in v3.6-SP1-HF1.3 and integrated in v3.6-SP2) to initiate Hibernate operations on desktop VMs from Azure.
The action is called Suspend in HyWorks.
Key Benefits:
-
Reducing resource consumption
-
Preserving the machine's in-memory state for faster resume times
Support and Compatibility:
- The VM is hosted on Azure, and Hibernation is enabled.
How to hibernate from HyWorks:
-
From the HyWorks Controller Management Console > Desktops page, select one or multiple DVMs.
-
Go to Power > Suspend.
Similarly, suspended VMs can be resumed using the same steps.
Limitations:
-
HyWorks does not know a VM's hibernate support in advance; thus, if suspend (hibernate) fails, the VM will remain in the same state.
- Hence, the administrator must not perform a hibernation assuming all VMs will be hibernated. This will be improved in future releases.
Pool Related Operations
Remove from Pool
Desktops can be removed from the HyWorks configuration and their respective desktop pool from the Desktop section by following the steps below:
-
Go to from VDI > Desktops > Personal page and select the desktop(s) to be removed from the pool.
-
Click on Remove from Pool.
-
Confirm action dialog will be displayed. Provide the reason for the action and click Continue.
-
Delete the desktop from the session provider, also? Select this checkbox if the DVM is no longer required and should be deleted from the respective provider. Keep this unchecked if you need to remove it from the HyWorks configurations.
Warning
The action is irreversible, and the deleted VM cannot be restored. Administrators should use this option only when they are sure they want to delete the DVM from the provider.
-
To proceed with the removal, the administrator must type Delete.
-
Click on OK to proceed. The dialog will be dismissed, and HyWorks will begin the desktop removal process based on the selected options.
-
-
Desktops will be removed from the Desktops section and the respective desktop pool.
Client Assignment Operations
Like Power Options, appropriate Assignment options will be enabled or disabled, e.g.:
-
The desktop is in an assigned state. The following options should be enabled.
-
Assign: Reassign the Desktop to another client.
-
Unassign: To remove the current client assignment from the Desktop
-
-
The desktop is unassigned. The following options will be available.
- Assign: To assign a client to this Desktop
Unassign Client from a Desktop
Unassigning a client from a selected desktop removes the association between the client and the desktop, making the desktop available for assignment to any other client.
The Unassign option will be available when the administrator selects any desktop assigned to a client.
-
Unassign in Manual Assignment Pool: In a Desktop Pool, where auto Assignment is not selected, and manual assignment is done, then Unassigning will:
-
Remove the association of the desktop and the client.
-
The desktop will not be automatically assigned to another client because this is a manually assigned pool; therefore, the administrator must make the assignment manually again.
-
When logging in from a client that is not assigned to a desktop, the error message No Desktop is assigned to this client appears.
-
-
Unassign in Auto Assignment Pool: In a Desktop Pool, where Auto Assignment was checked, and- Remove the association of the Desktop and the client(user or device)
- The desktop will be automatically assigned to another client or to this one on the next login.
Important
-
As explained above, unassigning a desktop from the Auto Assignment pool makes it available to all the clients in the Desktop Pool.
-
If a Desktop is unassigned while a session is in progress, it will be made available for another client. The session will not be affected.
-
The current user session might be disconnected if another client logs on.
Bulk Un-assignment
-
Supported Versions: v3.6 or later.
-
Steps to make bulk Un-assignment:
-
Navigate to VDI > Desktops > Personal page on HyWorks Controller Management Console.
-
Filter desktops as per requirements.
-
Select one or more desktops, then select Actions > Unassign.
-
A prompt will be displayed, listing the desktops eligible for assignment removal.
-
Select the option Remove assignment from pool also?: If it requires removing the assigned user entry from the desktop pool as well.
Note
Group-based assignments will continue to assign desktops to users who are members of the group added to the desktop pool.
-
Type the text unassign and click on OK to continue un-assignment.
-
Current assignment will be removed, and if the option Remove assignment from pool also? is checked, the user (if it exists in the desktop pool) will be removed.
-
Assign Client to a Desktop
The administrator can assign a Desktop from the Desktops > Personal section to either an already-assigned Desktop or an unassigned Desktop.
Assigning a client to a desktop not only assigns the client to a desktop but also adds the client to the pool configuration.
The client can be a user or device, and as per the pool type, an appropriate dialog will be displayed, i.e.
-
Device-Based Pool: Select a desktop from a Device-Based pool, then click the Assign button to display a desktop Assignment dialog listing the devices to be assigned.
-
User-Based Pool: Select a desktop in a User-based pool, then click the Assign button to display a desktop assignment dialog listing users to assign to.
Assignment Process
Follow the steps below to perform the assignment on Desktops > Personal section:
-
Select a Desktop from the Desktops > Personal section.
-
Click on the Assign button.
-
Select the desired client (Device or User, depending on the Pool Type) from the list of clients displayed in the Desktop Assignment dialog.
-
Click the Assign button.
-
If the selected client is already assigned to another desktop in the pool, the Confirm Action dialog will be displayed. Click OK to continue.
-
Suppose the selected client has not yet been assigned a desktop in the pool. In that case, no such dialog will be presented; the Desktop Assignment dialog will be dismissed, and the selected desktop will now be shown as assigned to the selected client (Device or User, depending on the Pool Type).
-
Impact of assignment on several types of pools
-
Case 1: Unassigned client to unassigned desktop:
-
Floating pool: Though temporary assignment pools require auto-assignment to be enabled, administrators can also do one-time desktop assignments for any device. This assignment will be active only for the client's next login and will be removed upon session disconnect. As the client was not assigned to any Desktop, they will be connected to the assigned Desktop on the next login.
-
Permanent pool: In a permanent pool, if a client was not previously assigned to a desktop and is then assigned to a free desktop, the assignment becomes permanent. At the next logon, the client will be assigned a session on the newly assigned desktop.
-
-
Case 2: Unassigned client to already-assigned desktop:
-
If the Desktop is currently assigned to a client, assigning it to a new client will remove the current assignment and assign it to the new client.
-
If a session is in progress with an old client, it will not be disconnected. However, when a new client logs on, the session will either be notified and disconnected, or disconnected directly.
-
Case 3: An assigned client to an unassigned desktop:
- Suppose the selected client (say Client-1) is already assigned to another desktop (Say Desktop-1) and is now being chosen to be assigned to a new, unassigned desktop (Say Desktop-2). In that case, the existing assignment of Desktop-1 to Client-1 will be removed, and only one assignment, Client-1 to Desktop-2, will be made. Thus, on the next login from Client-1, the Desktop-2 session will be granted.
-
Case 4: An assigned client to an already-assigned desktop:
-
Suppose the selected client (say Client-1) is already assigned to another desktop (Say Desktop-1) and is now being chosen to be assigned to a new desktop (Say Desktop-2, assigned to Client-2). In that case, the existing assignments of Desktop-1 to Client-1 and Desktop-2 to Client-2 will be removed, leaving only one assignment: Client-1 to Desktop-2.
-
On the next login from Client-1, a Desktop-2 session will be assigned, whereas the next login from Client-2 will display the error 'No Desktop is assigned to this client.'
More Desktop Management Operations
Reset Desktop
Desktop VMs from a Non-persistent desktop pool or a deployed desktop pool with the Enable DVM Reset option enabled can be restored to a fresh state.
To reset a desktop, follow the steps below:
-
Search and select a desktop from the list of DVMs.
-
The Observe button is Reset.
-
Click Reset.
-
On the prompt Confirm Action dialog.
-
Provide the reset reason and click Continue.
-
Type ResetDVM and click OK to proceed.
-
-
The Desktop will be reset to its fresh state.
Refresh Desktop
If a desktop VM's power state, IP address, or other attributes are not synced or do not show the latest information at any time, the administrator can initiate a refresh.
The Refresh operation performs the following tasks:
-
Obtain the latest details of the desktop VM’s power state, IP address, or fully qualified domain name (FQDN) from the provider.
-
Initiate agent communication to check agent status.
-
Update desktop VM information based on the refresh operation result.
Follow the steps below to refresh a desktop:
-
Search and select a Desktop from the list of DVMs.
-
Click Refresh.
-
Desktop status will be refreshed.
Fix Desktop/ Recreate Desktop
If a provisioned desktop has any issues that prevent the user from accessing it, the administrator can resolve them. This option will be enabled only on the provisioned desktop. Issues on the desktop can be:
-
The desktop is not powered on.
-
The IP address is not available.
-
The agent is not responding.
-
Internal OS issue.
To fix the desktop, the following steps can be followed:
-
Search and select a Desktop from the list of DVMs.
-
Ensure the Fix Desktop button is displayed, then click Fix Desktop.
-
On the Fix Desktop prompt, the following options will be shown:
-
Desktop Name.
-
The controller identifies the error.
-
Desktop Version: The current version of the desktop virtual machine.
-
Pool Version: Current version of the desktop pool.
-
Fix options:
-
Fix soft errors: The system can try to resolve soft errors by refreshing the desktop status (power state, IP address, agent communication) or rebooting the DVM.
-
Fix all errors: The controller will first attempt to resolve soft errors, and if that does not improve the desktop's status, it will recreate it. It may take several minutes for the desktop to become ready.
-
Recreate Desktop (Only for Persistent type pool): The Data and configuration stored in the desktop VM will be lost. The desktop will be deleted, and a new desktop will be created. This process requires time to clone and customize the OS.
-
Reset Desktop (only for non-Persistent type pools): The desktop VM's Data and configuration will be lost. The desktop will be reverted to a snapshot taken by HyWorks.
-
Update Domain Credentials (Optional): This option is only supported for HyWorks v3.4-SP2 or later. It is not a desktop-fixing option. It is an optional mechanism for updating the credentials used by machines in the desktop pool to join the domain when Active Directory changes affect the configured user (e.g., the user's password has changed or the user has been deleted). This option will be covered in detail later.
-
-
To proceed, click on the appropriate option (Fix soft errors, Fix all errors, Recreate Desktop, or Reset).
-
Check the logs for the actions required to fix the errors, based on the selected options.
-
In HyWorks v4.0 onwards, the administrator can select one or multiple desktops and initiate the fix desktop action.
Flow:
-
The administrator selects two or more desktops.
-
The fix type selection dialog is shown.
-
Desktops are filtered based on eligibility.
-
Summary confirmation displays eligible and skipped desktops.
Troubleshoot
The Troubleshoot button is used to diagnose issues with the DVM Agent (if any). The latest DVM Tools include an integrated troubleshooter. When clicked, the Troubleshoot option sends a message to the Desktop Agent, initiating the troubleshooting process. This tool can retrieve the machine's blueprint and gather general parameters to identify underlying issues.
Options Available: When clicking the Troubleshoot button, the following options will be displayed:
-
Download: If troubleshooting has been performed previously, the most recent report (including date and time) will be available for download.
-
Run the Troubleshooter: If no report is available or the administrator wants to generate a new report, this option initiates troubleshooting on the controller machine and automatically downloads the report once troubleshooting is complete.
- The report can help identify possible causes, and if further analysis is required, it can be shared with the Accops Support Team.
Upon completion of the troubleshooting process, a zip file named TroubleshootLog will be automatically downloaded. This zip file contains various folders, including:
-
DVMExtracted Log Folder
-
EventViewerLogs Folder
-
Report Folder
-
TroubleshootLog.txt document
-
VMBlueprint.json file
Important
This option is not available for Linux-based desktops.
Upgrade DVM Agent
The administrator can upgrade the DVM agent for specific desktops from the Desktops > Personal section.
File Location for Upgrading DVM Agent
For pushing the upgrade, HyWorks must have the appropriate version file placed in the appropriate directory; below are the details of placing Windows and Linux DVM Tools:
-
-
Place the latest HyWorks DVM Tools for Windows in the following directory:
C:\Program Files (x86)\Accops\HyWorks\HyWorksUpgradeService\Updates\Windows
-
HyWorks will automatically pick the version from the setup and will update the details. The upgrade process is defined below.
-
-
-
Place the latest HyWorks DVM Tools for Linux in the following directory:
C:\Program Files (x86)\Accops\HyWorks\HyWorksUpgradeService\Updates\Firmware
-
Update information on DVM Tools in the following file:
C:\Program Files (x86)\Accops\HyWorks\HyWorksUpgradeService\Updates\Linux\info.inf
The following information must be passed:
-
FileName=\<Name of file placed in step#1> e.g. FileName=HyWorksDvmTools_Linux_merged_3.3.2.24.tgz
-
Version=\<Version of placed DVM tools> e.g., Version=3.3.2.24
-
-
Save the file.
-
HyWorks will read the latest DVM Tools version information, and desktops running lower versions can be upgraded accordingly.
-
To upgrade the DVM agent, follow the steps below:
-
Search for and select a desktop from the list of desktop VMs. Desktops running a lower version of DVM Tools are shown with a red alert.
-
Click on the button Upgrade Agent. Based on the current running tool version, the following options will be displayed:
-
DVMs running a lower version:
-
Option to upgrade components:
-
HyWorks Desktop Agent
-
HyWorks Built-in USB Redirection Driver
-
HyWorks Printing Module (Session Server Extensions)
-
HyWorks USB Cleaner.
-
-
Option to reboot DVM.
-
Select the appropriate options, then click the Upgrade button.
-
-
-
The upgrade will be initiated, and the respective DVM will get upgraded to the latest version.
-
DVMs running a greater version
-
An upgrade is not possible.
-
An appropriate message should be displayed, stating that the version running on DVM is already higher and cannot be upgraded.
-
-
DVMs running the same version: This can be treated as
-
Option to upgrade components:
-
HyWorks Desktop Agent
-
HyWorks Built-in USB Redirection Driver
-
HyWorks Printing Module (Session Server Extensions)
-
HyWorks USB Cleaner.
- Option to reboot DVM.
-
-
-
Select the appropriate options, then click the Upgrade button.
- The upgrade will be initiated, and respective desktops will be upgraded to the latest version.
-
Controller logs can be checked for detailed information on the upgrade.
Multi VM Upgrade with HyWorks v4.0
With HyWorks v4.0 onwards, administrators can upgrade DVM Agent on multiple desktops in a single action from the tab.
Bulk upgrade will be initiated only when the following conditions are met:
-
All selected VDIs must belong to the same Pool.
- Ensures the same OS type, base image, and DVM Tools compatibility.
-
VDIs must be in allowed Agent states such as
RespondingorIdle.- Prevents upgrade on powered-off, deprovisioned, or unreachable desktops.
-
Only VDIs running a lower version of DVM Tools / Agent are considered.
- Desktops already running the latest version are skipped.
-
Ineligible VDIs are automatically excluded.
-
Administrators will be notified with an appropriate message. Example: "3 desktops skipped - already upgraded or not responding."
Nutanix Flow Categories
If the desktop is from the Nutanix (Prism Central) desktop provider and Micro-segmentation is enabled, this option will be visible when configuring categories on the desktop.
This option is primarily used to configure categories that do not apply to desktops. The categories configured on the Pool will be applied to the desktop by default.
Refer to the following link for Categories on the Pool under deployment settings.
The following options will be displayed when clicking on the Nutanix Flow Categories button:
-
Nutanix Flow categories: Option to choose pool setting or specify different settings for DVMs.
-
Use Pool Settings: This option is selected by default, and the categories configured on the Pool will be displayed in the Pool categories dropdown. The categories will be displayed read-only; no changes are allowed.
-
Specify categories to apply to DVM: The Selected Categories dropdown will populate with all the categories available on Nutanix (Prism Central). Multiple categories can be selected and configured on the desktop.
-
-
Applied Categories on DVM: The categories currently applied on the desktop will be displayed.
Move to Version
The Move to Version feature allows administrators to revert desktops in a desktop pool to an earlier version. Each recomposition increments the version number, starting from 1 and continuing sequentially. This functionality is handy for restoring a desktop to a previous state.
The version represents the logical state of the deployment and is derived from the combination of Desktop customization, Gold Master, Gold Master (Snapshot/Checkpoint), and VM Name Prefix. By upgrading to the version, the administrator can choose to recreate the desktop with a specific set of deployment settings.
Steps to Use the Move to Version Option:
-
Select the Desktop: To revert to an earlier version, select the desktop you wish to restore.
-
If the administrator selects multiple desktops, the Recompose Type must be set to either Only Free VMs (Graceful) or All VMs Now (Forceful).
-
Only free VMs option: Free desktops without remote sessions will be recomposed. This option is selected by default when the Move to Version prompt launches.
-
All VMs Now: It will ignore the presence of sessions on selected desktops and initiate forceful recompose.
-
-
-
Click Move to Version to initiate the process.
-
Select the Version: The administrator must choose the desired version to revert the selected desktop to. A list of available versions (Version Number, Gold Master Name, Snapshot name, Date & Time) will be displayed for selection.
-
Click on Move.
-
HyWorks will initiate the Move to version operation.
- HyWorks may skip the Move to version for one or more selected desktops for various reasons. The reason will be provided in the logs. One reason could be that the Move to version and the current version are the same.
Update the Password of the Selected Version
The Move to version action recreates the desktop and then customizes the desktop OS using the selected Hyprep or Sysprep mechanism. However, if the user credentials used to domain-join the deployed desktops change, HyWorks should use the new credentials after recreation. The following method can be used to update the password for the version.
Download Logs
It can be downloaded from VDI > Desktops > Personal page itself. Select the desktop, then click the Download Logs button.
-
Logs will be downloaded if the desktop is powered on and the controller can communicate with the agent.
- Name Format of the downloaded logs: HyWorks-DVM-Log-[IP Address of the desktop].zip
-
An error will be shown if the controller cannot communicate with the agent.
Contents of the Downloaded ZIP File
Inside the downloaded folder, the following logs will be included:
-
Windows Desktops:
-
Desktop Agent Logs: These logs contain comprehensive information about users' desktop sessions, including connection, disconnection, and logout events, along with other related details.
-
Hyprep Logs: These logs document the Hyprep process during desktop pool cloning, including the steps taken and any relevant outcomes.
-
Sysprep Logs: These logs contain information about the Sysprep process performed during desktop pool cloning, including configuration details and preparation tasks executed.
-
-
Linux Desktops:
- All log files are located in the log folder (/etc/edcdvm/linuxDVM/Logs).
Send Message
The Send Message feature lets administrators directly notify users logged into specific desktops. This functionality is essential for conveying important real-time information or alerts to users.
The prerequisites and details of this feature are outlined in this section.
Steps to Use the Send Message Option:
-
Select the desktop(s): Begin by selecting the desktop(s) you wish to send a message to.
-
Click Send Message to initiate the messaging process.
-
Enter Message Details:
-
Title of the Message: Enter a concise title that summarizes the message.
-
Actual Message: Write the entire message to the user.
-
Severity Level: Choose the severity of the message from the following options:
-
Critical: For urgent messages requiring immediate attention.
-
Warning: For messages that are important but not urgent.
-
Information: General information that may be useful to the user.
-
-
-
Select Message Delivery Option:
-
Send Outside the Desktop Session: If you select this option, the message will be sent to the client’s base machine and displayed there, allowing the user to see it outside their desktop session.
-
Send Inside Desktop Session: If this option is selected, the message will be delivered only within the desktop session. The user will see the message while working inside the virtual desktop environment.
-
Note
-
The feature does not work for Linux-based desktops.
-
The method for sending messages outside of desktops depends on the endpoint client. It currently works only with Windows-based desktop clients and will not work on Linux-based endpoints, Android, Mac, or HyLite.
-
The send message will skip the desktops that do not have any sessions and are not powered on.
Message Delivery Methods
Messages can be sent to the desktop session or outside the desktop session using the following three methods:
-
AUEM Tray: Messages sent via the AUEM tray will appear inside the desktop session.
-
Terminal Server: This method also delivers messages inside the desktop session.
-
Virtual Channel: Messages sent through this method will be delivered outside the desktop session and appear on the client’s base machine.
To change the message delivery method inside the session: Inside the session, the administrator can set either of the message display mechanisms (AUEM Tray or Terminal Server) using the following configurations:
-
On the desktop, configure the following registry values:
-
Registry Location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Accops\DVMAgent\DVM PUSH SETTINGS
-
DisplayNotificationUsingTrayAgent: Use this method if you want to keep it true. The default value is True. If the Terminal server method is to be used, set it to False.
-
DisplayNotificationUsingTerminalServer: The default value is false. If this method must be used, set it to True; then set the Tray Agent method to False.
-
-
Save the registry settings with the appropriate values as required.
-
Restart the following services:
-
Accops HyWorks Desktop Agent
-
Accops User Experience Manager
-
-
Log out of the session and connect again.
Multi-select and Allowed Operations
HyWorks v3.4-SP2 enables administrators to perform multiple actions simultaneously across multiple desktops.
-
From VDI > Desktops > Personal section, select multiple desktops.
-
Click on the list actions.
-
HyWorks will queue up the desktops and will perform actions on them.
Note
If the administrator selects desktops that do not meet the conditions to perform the actions, those desktops may be skipped.
Allowed Actions: The Following actions are allowed while selecting multiple desktops:
-
Power Operations
-
Shutdown
-
Reboot
-
Those that do not have any sessions or are powered off
-
Power on
-
Suspend
-
Resume
-
-
Remove from Pool
-
Refresh Desktop Status
-
Move to version
-
Restore Desktop
-
Send Message
Advance Configurations
Refer to the Advance Configuration for VMs section for the HyWorks controller.