Configure and Register the Machine Manager

Omnissa App Volumes operation mode is determined by configuring a machine manager. You cannot change the operation mode of App Volumes after you configure the machine manager.

Prerequisites

• Ensure that the domain policies do not enforce password expiration for the service account on the machine manager to be configured.

• Ensure that you are aware of the hypervisor connection types.

  For more information about these types, see Types of Machine Manager Configurations

Note:

• If you are configuring a vCenter Server as the machine manager, ensure that you have the required vCenter Server permissions.

• If you have configured Entra ID as the registered domain, VMware vCenter Server or Single ESXi Host cannot be used machine manager.

Procedure

1. From the App Volumes Manager console, click CONFIGURATION > Machine Managers.

2. Click Register Machine Manager.

3. Select and configure the type of machine manager.

   Machine Manager Type	Description
   vCenter Server	If you select a vCenter Server instance as the first configured machine manager, you can add and configure additional servers. If the App Volumes Manager connects to the vCenter Server through an IPv6 connection, then you must provide the DNS of the vSphere as the host name. Ensure that you are aware of the considerations when hypervisor connection type is VMware vCenter Server. For more information about the considerations, Types of Machine Manager Configurations. Follow the instructions as mentioned in step 4.
   ESXi (Single Host)	Enter the host name, user name, and password for the ESXi host. Follow the instructions as mentioned in Step 4.
   VHD In-Guest	This connection type does not require any credentials. Ensure that you have created a file share to configure NTFS permissions. The CIFS share must be created on a stable network, which can handle the applications residing on the share for VDI desktops. On a file server, create an empty folder and name the folder. Share the folder and grant full access permissions on the file share to any logged-in user. As part of the machine manager configuration, App Volumes Manager automatically imports the volumes and templates to the CIFS file share. After configuring and registering the VHD In-Guest machine manager, configure NTFS permissions on the imported folders. Keep the UNC path or the name of the file share location handy. You need this information when configuring the storage for this machine manager type. If you have used the Azure Marketplace to deploy App Volumes Manager and skipped the automatic storage provisioning, then you must manually add the file share to App Volumes Manager. Depending on whether the file share is non-domain joined or on-prem Active Directory domain joined, follow these prerequisites: Non-domain joined file share Have the following information handy: Storage account name of your Azure storage account. Storage Account Access key 1 or Storage Account Access key 2 in the Access keys page of your Azure storage account. On-prem domain-joined Active Directory file share In your Azure subscription, ensure that you have already completed the required configuration to enable the on-prem AD DS authentication and authorization: Enable AD DS authentication for Azure file shares Assign share-level permissions. Assign directory/file-level permissions. Mount file share. Note: The following file share configurations are not supported: Azure AD DS authentication, Azure AD Kerberos for hybrid identities, and AD Kerberos authentication for Linux clients Follow the instructions as mentioned in Step 5.

   To view the permissions required by the service account, click Required vCenter Permissions.

4. If you have selected Machine Manager Type as vCenter Server and ESXi, perform the following steps:

   Note: For ESXi, you only need to provide the hostname, username, and password.

   1. Provide the following information:

      Option	Description
      Hostname	The host name of the Machine Manager. For example, server.your-domain.local. For App Volumes on VMware Cloud on AWS, the host name must be of the form vcenter.sddc-xx.xxx-x-xx.vmc.vmware.com
      Username	The user name to access the machine. Note: For a better performance, it is recommended that you use a local account. For information about how to Create a Local User Account in vCenter Server, see the vCenter Server Configuration documentation at VMware Docs.
      Password	The password for the user name.
      Fast Attach	When selected, volumes are attached to entities in fast mode. Important: Fast Attach feature is supported when you have the following system requirements: VMware ESXi and vCenter Server 8.0 Update 2 and later App Volumes agent 4, version 2303 and later VM version 21 and later If your vSphere version is earlier than the supported version for Fast Attach, volumes continue to attach without the Fast Attach functionality.
      Mount ESXi	When mounting, connect directly to ESXi servers. Note: When this option is selected, all vSphere hosts require the same user credentials. This option is not applicable for App Volumes on VMware Cloud on AWS.
      Mount Local	Select this option if your VM's datastore has local copies of volumes and you want to mount the local copies.
      Mount Queue	Select this option to queue requests to the VM host. Decreases the number of active connections to vCenter Server and ESXi. This results in increased performance and decreases the burden on the vCenter Server.
      Mount Async	Wait for the mount request to complete in the background. Increases App Volumes Manager server throughput. Requires the Mount Queue option to be selected.
      Mount Throttle	Limits the number of actively processing mount requests. Decreases load on the vCenter Server or ESXi servers. Requires the Mount Queue option to be selected.
      Maximum number of concurrent mount operations per queue	The maximum number of concurrent mount operations per queue. Use the servers entry in clock.yml to configure this field. Default value is 5. Note: Each vCenter Server and ESXi server uses a separate queue for every manager process.

   2. Click Save.

      The configured machine manager is displayed on the Machine Managers page.

   3. If you have selected Machine Manager Type as vCenter Server, you can connect App Volumes Manager securely to a vCenter Server by following the procedure as mentioned in Establish a Secure vCenter Server Connection.

   4. (Optional) Create a custom role on the vCenter Server.

      For more information about how to create a custom role, see Create a Custom vCenter Server Role.

5. If you have selected Machine Manager Type as [VHD] In-Guest Services, perform the following:

   1. Click Next.

   2. On the CONFIGURATION > Storage page, click Add File Share.

   3. On the Add File Share page, search for the file share location.

      Details of the file share such as Name, UNC Path, and Permissions are displayed.

   4. (Optional) Enter the Username and Password for the file share.

      Note: These credentials are used by App Volumes Manager and App Volumes agent.

      Username must follow the Domain\Username format.

      Username and Password must belong to the service account, which is configured with permissions to access the packages and Writable Volumes on the file share. App Volumes uses the service account to access the volumes on the file share. As a result, it is not necessary to configure NTFS folder permissions for agent machines when using App Volumes with VHD In-guest operation mode.

      When adding the file share path, modify the file share URL to a path which can be understood by Windows.

      For example: Modify the file share URL https://<storage_account_name>.file.core.windows.net/file_share_name to the following path \\<storage_account_name>.file.core.windows.net\file_share_name.

      If the existing file share is a non-domain joined file share, then enter the following information:

      • In the Username field, enter the Storage account name.

      • In the Password or Storage key field, enter the Storage Account Access key 1 or Storage Account Access key 2.

   5. Expand the name of the file share and click Add.

   6. On the Confirm Add screen, select Add.

   7. On the CONFIGURATION > Storage page, select the Default Storage Location for Packages and Writable Volumes.

   8. Click Next.

   9. On the Confirm Storage Settings window, choose when you want to import the volumes:

      • Import volumes in the background - App Volumes Manager dispatches a background job to import the volume and the display goes back to the manager console immediately.
      • Import volumes immediately - App Volumes Manager waits for the import to be completed and the console is not responsive until either the process is complete or 10 minutes have elapsed.

   10. Upload Templates.

   11. Optional: Select the Dynamic File Permissions checkbox.
       For more information about the setting, see App Volumes Manager Configuration Settings Page.

   What To Do Next

   Configure NTFS permissions on imported volumes and templates folders. For information about these permissions, see Types of Machine Manager Configurations.