Skip to content

Recompose desktop pool v2

Recompose v2: Graceful Recompose in HyWorks v3.4-SP1 or Later

Accops HyWorks provides a recompose option for deployed desktop pools, allowing administrators to re-provision all desktops while preserving the assignment and other configurations.

In earlier versions, recomposing a desktop pool involved deleting all VMs and creating new ones, leading to downtime for users as they had to wait for desktops to become available or force the recomposition. The latest version of HyWorks Controller supports VM recreation for free VMs while preserving configurations. Occupied VMs are recreated once they become available, allowing administrators to initiate a recompose operation on a pool even when some VMs are connected without disrupting running sessions.

Supported in version: HyWorks Controller v3.4-SP1 or later

Connector Support: Graceful recompose and Revert to version are supported with below session providers:

  • vCenter (Full Clone only)
  • Azure
  • Nutanix

Challenges in Previous Recompose:

  • The recomposition requires 100 % downtime.
  • The IT Admin needs to monitor the recompose process actively.
  • There was no option to revert to previous images and pool settings.
  • There was no selective rollout of VMs.

Advanced Features in Latest HyWorks Recompose:

  1. Options to recompose a specific number of desktop VMs.

  2. Version management: All VMs can be associated with a specific image version.

  3. Reverting to a specific version: Option to revert to any previous VM versions.

Benefits for Administrators:

  1. Selective rollouts for improved flexibility.

  2. Reduced monitoring requirements.

  3. Easy rollback to previous versions.

  4. Version management for better identification.

New Recompose Options

The new recompose offers the following options for administrators:

  1. All VMs Now (Forceful): This option functions similarly to earlier versions, where all VMs are deleted upon initiating the recompose, and new VMs are created. To initiate forceful recompose:

    • Edit a desktop pool

    • Go to the Deployment tab.

    • Enable checkbox for Recompose checkbox.

    • Select Recompose type as All VMs Now (Forceful)

    • Save the pool.

This option is supported by all session providers that support dynamically provisioned desktop pools.

  1. Only Free VMs (Graceful): This feature is integrated into the latest HyWorks Controller and offers two recompose rollout options:

    1. All Free VMs: All VMs that are not in use are instantly deleted and recreated, while occupied VMs are redeployed once they become available.

      • Edit a desktop pool.

      • Go to the Deployment tab.

      • Enable the Recompose checkbox, select the Recompose type as Only Free VMs (Graceful), and select the Recompose rollout type as All Free VMs.

      • Save the pool.

    2. Limited (Specified no of VMs): It provides an option to redeploy only a specific number of VMs, and for redeploying the VMs, first, it checks for the free VMs and then redeploys VMs as per the number configured. For initiating graceful recompose with recompose rollout type as Limited (Specified no of VMs):

      • Edit a desktop pool.

      • Go to the Deployment tab and enable the checkbox for Recompose.

      • Select the Recompose type as Only Free VMs (Graceful), select the Recompose rollout type as Limited, and provide the number per the requirement.

      • Save the pool.

Note

  • For graceful recompose, it is mandatory to select "Clone from checkpoint."
  • The checkpoint feature is available in Azure providers, while administrators of other providers must create snapshots/checkpoints from their hypervisor management portals.
Version

In desktop pools, the "Version" now represents a specific set of configurations associated with the deployment. This version is linked directly to the following pool configurations:

  • Desktop customization

  • Gold Master

  • Gold Master (Snapshot/Checkpoint)

  • VM Name Prefix

Move to Version

The latest HyWorks Controller introduces the Move to Version functionality to maintain recompose history and enable future VM redeployment based on previous configurations. Administrators can revert VMs or the entire pool to any earlier version.

  1. Move to Version from Pool Page: For redeploying the whole pool:

    • Select the desktop pool and click on the Move to Version button.
    • Current and previous version details will be displayed in a pop-up window.
    • Select the version details to which all VMs from the pool should be moved.
    • Optional: If applicable, select and update the domain password for the selected version before moving. For more details, see the Update Domain Password section.
    • Click the Move button, and all VMs from the pool will be moved to the selected versions.

  2. Move to Version from VMs Page:

    • On the VMs page, select one or more VMs to be moved to a specific version and click the button.
    • Choose Recompose Type as Only Free VMs (Graceful) or All VMs Now (Forceful)
    • Select the version and click the Move button to redeploy a particular VM(s).
    • Optional: If applicable,select and update the domain password for the selected version before moving. For more details, see the Update Domain Password section.

  3. Move to Version from Fix Desktop Page:

    • On the Fix Desktop page, if the selected desktop is valid for an update password, the Update Credentials tab will be visible as there won’t be the versions pop-up to select versions.

Update Domain Password

Feature Overview: Update Domain Password in HyWorks Management Console
Introduction

The Update Domain Password feature in the HyWorks Management Console allows administrators to update the domain password stored in a specific version of a virtual machine (VM) or pool. This feature is crucial for maintaining the integrity and accessibility of virtual environments when domain passwords are changed or expired.

Feature Description

When moving VMs or pools to a previous version, administrators are presented with an option to update the domain password stored in that version. This feature is only available for applicable VMs or pools and ensures that the stored password is synchronized with the current domain credentials. It is important to note that this update only affects the versions saved in the HyWorks database, not the actual domain.

Key Components:
  • Domain Username: The username stored in the version (read-only).
  • Domain Password: The new domain password to be stored.
  • Confirm Domain Password: Field to re-enter the new domain password for confirmation.
  • Buttons:
  • Test: Validates the new password before it is saved.
  • Save: Saves the updated password across all applicable versions of the pool.

This feature was introduced to resolve the issue where previously, if the domain password was changed or expired, the only option was to recompose the pool.

Use Cases
  • Password Synchronization: Ensures that the stored version passwords remain up to date with the actual domain, preventing access issues.
  • Security Compliance: Helps in maintaining compliance by allowing quick updates to passwords across stored versions after a domain password change.
Accessing the Update Domain Password Feature

To access the Update Domain Password feature:

  1. During Move to Version:
    • Initiate the Move to Version process for a VM or pool.
    • After selecting the desired version, check if the Update Domain Password option is available.
    • If visible, proceed to update the domain password as needed.
  2. Fix desktop:
Using the Update Domain Password Feature
Step-by-Step Guide
  1. Select a Valid Pool: Ensure the pool is either domain-joined or has versions. The feature is only applicable to these types of pools.
  2. Select a Version: During the Move to Version process, choose the desired version.
  3. Update Credentials: If applicable, an Update Credentials tab will appear.
  4. Note: If the domain password is not updated, the existing password in the version will be used.
  5. Check Box: Select Update Domain Password to proceed.
  6. Fields and Buttons:
    • Domain Username: Read-only, displaying the username saved in that version.
    • Domain Password: Enter the new password.
    • Confirm Domain Password: Re-enter the password for confirmation.
    • Test: Optionally test the new password to ensure it is correct.
    • Save: Save the updated password. This action will update the password across all relevant versions.

Note

  • The test will fail if the user is not part of the registered authentication server.
  • Repeated failed attempts may block the user in the directory, depending on the applied policies.
  • The Update Password feature updates the password in the versions, not on the actual domain.
Best Practices
  • Regular Updates: Update stored passwords promptly after any domain password changes to prevent access issues.
  • Testing: Always test the new password before saving to ensure it is correct and prevent account locks.
Troubleshooting
  • Failed Test: Ensure that the user is part of the registered authentication server before attempting to test the password.
  • Access Issues: Verify that the correct username and password are being used, and that the update was applied to all relevant versions.
Frequently Asked Questions (FAQs)

  1. Q: Does updating the domain password affect the actual domain?

    • A: No, the update only applies to the stored versions in the HyWorks database.

  2. Q: What happens if I don't update the password?

    • A: The version will use the previously stored password, which may lead to failure of domain join of the machines.
Conclusion

The Update Domain Password feature is an essential tool for maintaining synchronization between stored version credentials and actual domain passwords. By ensuring passwords are up-to-date, administrators can prevent access issues and maintain security compliance.

Version History
  • Version ?? - Initial Release, August 2024.
Process to Recompose Selective VMs

If it is needed to apply the recompose to only selective VMs, the following process can be followed:

  1. Edit the desktop pool.

  2. In Deployment tab > Enable checkbox for Recompose checkbox.

  3. Select the Recompose type as Only Free VMs (Graceful), select the Recompose rollout type as Limited to, and provide the number as "0" per the requirement.

    1. Select the appropriate snapshot/image to be associated with the version. (if needed)

  4. Save the pool. This will help create a version without pushing upgrades to any VMs.

  5. Now go to the Desktops page and filter out desktops from the pool updated in the above step.

  6. Select one or more desktops and click on Move to version.

  7. In the Move to Version window, a list of versions will be displayed with details like (Version Number, Gold Master Name, Snapshot Name, Date, and Time).

    1. Select the version.

    2. Click on Move.

  8. The selected VM(s) will now be recomposed and moved to the selected version.

  9. Desktop pages and logs can be checked to check the progress and status of the tasks.