Prepare Accops Hyper-V Manager (AHM)

For smooth integration of Accops Hyper-V Manager (AHM) with the HyWorks Controller, use the guidance below:

• Supported Versions

• Supported Features Matrix

• Prerequisites

• Configuration Process

• Guest Tools

Detailed Specifications

Supported Versions

Provider	Supported Versions	Supported Hypervisors	Hypervisor Version
Accops Hyper-V Manager (AHM)	v4.1.0.23929 (Same as Controller, not an independent entity)	Microsoft Hyper-V	Windows Server 2025, 2022, 2019, 2016

Controller Support	Supported Versions
HyWorks Controller	v4.1 (4.1.0.23929) or later.

Network Requirements

Parameter	Value
Port	38903
Protocol	HTTP / HTTPS

Note

In HyWorks v4.1, the Accops Hyper-V Manager service runs locally on the HyWorks Controller Management node. Therefore, the port does not need to be opened on any external firewall. The port is mentioned only to indicate the port used by the service.

Supported Features Matrix

Feature	Sub Feature	Sub Feature	Accops
			AHM (Accops Hyper-V Manager)
VM Details	OS Information	-	Yes
	Network Adapters/ IP Addresses	-	Yes
	Hostname	-	Yes
Desktop pool with existing VMs	Using Non-provisioned VMs	-	Yes
Desktop VM Provisioning	Clone Type: Linked/Full/Shadow	-	Full Clone
	Automatic Distribution of VMs as per load	Best Host selection	Yes
		Multi-Datastore and Best Storage Selection based on size	No
	Clone from Snapshot/ Checkpoint	Feature Support	Yes
		Create Snapshot from Management Console	No
	Disk persistence	Persistent	Yes
		Non-persistent (Create/ Delete VM Restore point on User Logoff)	Yes
	VM Profile (v3.6+)	Deployment Location & Hardware Specifications	No
	Recompose	Preserve Network/ MAC Address	Yes (HyWorks v4.1-HF1)
		Graceful/ Selective Recompose	Yes
		Override server defaults of VM distribution	No
	SHD Provisioning	Automatic Deployment of Session Teams	Yes
	Capacity planning (Automatic deployment and power management)	Multi-session or shared hosted desktops	Yes
		Dedicated/ Single-session Desktop [v3.6-SP2]	Yes
		Schedule Action support	Yes
Desktop Power Operations	-	-	Yes
OS Support on Provider	Windows Desktops: Windows 10, 11	-	Yes
	Windows Servers: Windows 2016/2019/2022/2025	-	Yes
	Linux Desktops: Ubuntu/ xUbuntu 22/24	-	Yes
	Linux Desktops: RHEL 9.4	-	Yes
Desktop Access Mechanisms	Remote Desktop	-	Yes
	Console Connect	-	Yes
HyLabs support	Scheduled Provisioning and Delivery	-	No
HyLabs (Additional Features)	Create/ Delete Resource Pools	-	No
Virtual IP (Session host IP virtualization)	Adding an IP Address to a network adapter	-	Yes
vTPM Support	Feature Support (Cloning the vTPM-Enabled Machines)	-	No
	vTPM Aware Cloning (Selecting the best host based on vTPM support)	-	No

OS Support on Providers

As AHM currently serves only as an intermediate module between HyWorks Controller and hypervisors/hypervisor clusters (with HyWorks v4.1: Microsoft Hyper-V), it supports all OSs supported by the member hypervisor.

OS Support on Providers:

Feature	Sub Feature	Supported on providers
OS Support on Provider	Windows Desktops: Windows 11,10	All connectors
	Windows Server 2025/2022/2019/2016	All connectors
	Linux Desktops: Ubuntu / Xubuntu 24/22	All connectors
	Linux Desktops: RHEL 9.4	All connectors

Important

Linux (Ubuntu/Xubuntu 24/22 and RHEL 9.4) is supported on HPE Morpheus Software - HVM Hypervisor. However, some issues during provisioning in HyWorks have been identified and are being tracked with the HPE technical team.

Feature Comparison - Provider

Click here to view the Supported Feature Matrix Comparison between all Accops-supported Hypervisors.

Prerequisites

Accops Hyper-V Manager Installation

To configure AHM as a connector, the Accops Hyper-V Manager service must be installed on the management nodes.

Accops Hyper-V Manager service installation has no additional prerequisites. It can be installed easily on the HyWorks Controller management node during Fresh mode or Maintenance mode (Using the Add New Component flow) installation wizard.

Hyper-V Connector Installation on Targeted Hyper-V Servers

AHM in release v4.1 targets Microsoft Hyper-V hypervisors. Before starting configurations, all targeted Hyper-V servers (including those that are members of Hyper-V clusters) should have the Accops HyWorks Hyper-V connector installed in Hyper-V mode.

Refer to Hyper-V Connector Installation.

Configuration Steps

To configure the Accops Hyper-V Manager in HyWorks as a connector for virtual desktops and applications, ensure that you have completed the following prerequisite steps:

1. Install the AHM on the management node.

2. Install the Hyper-V connector on the target.

Once these steps are correctly completed, you can proceed with the two-step configuration process.

1. Configure Accops Hyper-V Manager in HyWorks.

2. Configure Hyper-V Hosts/ Clusters in Accops Hyper-V Manager.

Configure Accops Hyper-V Manager in HyWorks

Follow these steps to add AHM as a connector in HyWorks:

1. Go to HyWorks Controller Management Console > Settings > Configure > Connector.

2. Click Add.

3. Configure a new connector with:

   1. Connector Category as On-premise Virtualization.

   2. Type as Accops Hyper-V Manager.

   3. Host Address is by default https://localhost:38903. Not editable as the Accops Hyper-V Manager service gets installed locally with HyWorks Controller.

   4. Name: Provide a logical name for the new connector. The following characters are allowed: _ SPACE () {} # @: - with a maximum length of up to 100 characters.

   5. Advanced Settings:

      1. Memory Threshold (%): Default 90%. Maximum memory usage allowed for host selection during VM cloning and migration at power-on or resume. Only hosts below this threshold are considered.

      2. CPU Threshold (%): Default 90%. Maximum CPU usage allowed for host selection during VM cloning and migration at power-on or resume operation. Only hosts below this threshold are considered.

      3. MAC Address Range Configurations: Introduced in v4.1-HF1, HyWorks (with AHM and a compatible Hyper-V connector v4.1.0.439 or later) sets locally administered addresses for all VMs deployed via AHM. The following configurations are available:

         Configuration	Description and Specification
         MAC Prefix	Base MAC prefix for allocation. F2-AC-AA (Default). The following two additional prefixes are available: F2-AC-BB F2-AC-CC
         Start MAC Suffix	Start of the allocatable MAC range. 00:00:01 (configurable).
         End MAC Suffix	End of the allocatable MAC range. FF:FF:FF (configurable).

         Important

         By default, the AHM connector uses locally administered addresses for VMs deployed via HyWorks.

4. Click Test Connection to check service reachability.

5. Click Add to continue adding a new connector of type Accops Hyper-V Manager.

Configure Hyper-V Hosts/ Clusters in Accops Hyper-V Manager

Once an instance of the Accops Hyper-V Manager connector is added to HyWorks, the next step is to add member Hyper-V hosts to it.

Mandatory Prerequisite: All targeted hosts already have the Hyper-V Connector installed.

Follow these steps to configure Hyper-V hosts:

1. Go to HyWorks Controller Management Console > Settings > Configure > Hyper-V Hosts.

   1. The page lists the added Hyper-V Hosts.

2. Click Add.

3. Add Host - General wizard:

   1. Provide the host address of the target Hyper-V hosts.

   2. Click Get Host/Cluster Details.

      1. Member of Hyper-V Cluster: If the provided host entry is a member of any Hyper-V cluster, all the cluster Hyper-V hosts will be listed with their hostname, reachability status, IP address, and an option to add them to the Accops Hyper-V Manager.

         1. Ideally, all cluster hosts should be added. (HyWorks and then Accops Hyper-V manager will be using the best host for provisioning with shared storage available.)

      2. Standalone Hyper-V Host: If the provided host entry is a standalone host, retrieving the details will simply show the status message.

   3. Click Add to continue adding the fetched host(s).

4. Hosts will be added and will be listed in grid view with the appropriate status.

5. Refresh/Update recently added AHM connector:

   1. Navigate to HyWorks Controller Management Console > Settings > Configure > Connector.

   2. Select the recently added AHM connector > Edit > Click Update (No need to change any configurations).

   3. Wait for the update to finish.

6. The Accops Hyper-V Manager Server has been successfully configured and is now ready for the next stages of deployment.

Guest Tools on VMs

As AHM currently serves only as an intermediate module between HyWorks Controller and hypervisors/hypervisor clusters (with HyWorks v4.1: Microsoft Hyper-V), it depends on hypervisor-specific guest tool requirements. The VMs should be installed with the appropriate guest tools for Hyper-V.

Refer to Hyper-V Guest Tools Installation for prerequisites.

Locally Administered MAC Address Management, Allocation, and MAC Preservation

Supported Versions: The following modules with the specified versions support this feature.

• HyWorks Controller: v4.1-HF1

• AHM: Same as HyWorks

• Hyper-V Connector: v4.1.0.439

Feature Description:

• Configurations to specify the MAC Address Range in the Add/Edit wizard of the Hyper-V Connector

• MAC Allocation Workflow

  • Initial Provisioning:

    HyWorks Controller > Check Configured MAC Pool (Range) > Allocate available MAC address > AHM Provider provisions desktop VM > Assign MAC during VM provisioning > Store Desktop and MAC mapping in Controller Database

  • Recreate / Recompose Workflow

    HyWorks Controller > Fetch existing MAC mapping in Controller Database > Returns assigned MAC > HyWorks Controller Provision desktop VM > AHM Provider reapply previous MAC address

  • MAC Recycling Workflow

    Desktop Deletion > Permanent delete triggered > HyWorks Controller releases mapped MAC address to MAC Pool > Mark as available > Ready for future provisioning

    Desktop Deletion > Deleted from HyWorks only > MAC Address is not released.