Horizon Cloud with Hosted Infrastructure 17.2 Release Notes

|

Updated on: 19 OCT 2017

Horizon Cloud with Hosted Infrastructure 17.2 | 19 OCT 2017 

Check for additions and updates to these release notes.

Links to release notes for other versions: 16.6 | 16.6.1 | 16.11 | 16.11.1 | 17.1 | 17.1.1

What's in the Release Notes

The release notes cover the following topics:

 

Product Documentation

To access the product documentation for all deployment models of Horizon Cloud, see the VMware Horizon Cloud Service documentation landing page.

Note: In the 17.2 release, the Horizon Cloud Getting Started and Administration guides have been combined into a single Administration guide.

Compatibility Information

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

New Features

Farms for RDS Hosts

A farm is a collection of Microsoft Remote Desktop Services (RDS) hosts that provide multiple users with session-based desktops and applications. Farms simplify the management of the RDS hosts. You can create farms to serve groups of users that vary in size or have different desktop or application requirements.

Before you can assign session-based desktops or remote applications to end users, you must create the farms to serve those desktops and applications. A farm can provide either session-based desktops or remote applications.

For more information, see the Farms section of the Administration guide.

Cloud Monitoring Service

The Cloud Monitoring Service (CMS) significantly expands Horizon Cloud's monitoring capabilities.

Note: The vRealize Operations Desktop Agent component of the Horizon 7 Agent must be installed for this feature to work.

New reports that draw data from the CMS are listed below.

  • On the Dashboard page:
    • Utilization - View utilization data for RDS desktops and remote applications.

  • On the Reports page:

    • Desktop Health - View list of desktops, which can be filtered by assignment or error status. Click on a desktop to view report including CPU usage %, memory usage %, disk IOPS, and active/disconnected sessions.

    • Utilization - View graphs for user and session trends, protocol and client usage, access type (internal or external), session duration, and service type.

    • Session History - View session information by user, including last login time, session duration, weekly average use, and average session length.

    • Concurrency - View per-assignment data for capacity, number of concurrent users, peak concurrency, and applications in use.

Note: There is a new setting called User Session Information that allows user and domain data to be used by CMS. This feature is enabled by default and can be accessed in the Getting Started wizard and in General Settings. If it is disabled, the following are not provided: 

  • The Unique User Summary feature of the Utilization report
  • The Session History report

URL Redirection

This feature allows you to define URL handling rules where the Horizon Client redirects URLs from the end user's client machine to a remote application or session desktop in your environment. A URL redirection configuration gives the Horizon Client information about which URLs should be handled by one of your desktops or remote applications instead of being opened by the user's local system.

  • You can configure URL redirects on the Assignments page. See the Assignments section of the Administration guide for more information.

  • Configured URL redirects are listed on the URL Configurations tab of the Reports page.

Console Access to Desktops

You can now launch a console interface to any desktop VM directly from the Administration Console. To facilitate this, there is a new Launch Console option on the assignment detail page and on the Imported VMs page. See the Assignments section and the Imported VMs section of the Horizon Cloud Service Administration guide for more information.

Option to Enable/Disable HotPlug Capability for New Desktop Assignments

You can now enable/disable the HotPlug functionality for desktops in a new desktop assignment. When this functionality is disabled, network adapters do not appear in the Quick Add/Remove area. This makes it more difficult for users to put their VMs into an unusable state.

When you create a new assignment, there is a new setting called HotPlug Enabled, which is set to Off by default. When set to On, it enables HotPlug functionality for all desktops in the assignment.

Note: You cannot make this setting for existing assignments.

Emergency Direct Desktop Connection When Broker is Unreachable

In an emergency situation where the broker is down or unreachable but the network is still working, you can globally instruct all DaaS Agents to allow temporary RDP native access so end users can connect without the broker being functional.

To enable this temporary functionality, add the registry keys described below to the desktop VM(s), either directly or via GPO policy. Add the keys in one of the following locations, depending on whether the DaaS Agent is installed on a 32-bit or 64-bit Windows system:

  • HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware DaaS Agent (32bit)

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent (64bit)

Key Type Value
AllowDirectConnections DWORD

0 = do not allow direct connections

1 = allow direct connections.

DirectConnectionExpiryInUTC REG_SZ Date and time until which direct connections are allowed if direct connections access is enabled (AllowDirectConnections = 1). Date and Time Format: YYYY-MM-DD HH:MM:SS

 

This functionality requires the following:

  • DaaS Agent 17.2 is in use.

  • RDP access is not being blocked via View or any other GPOs.

  • The user is in a group associated with a desktop assignment. The DaaS Agent configures the same users/groups for RDP access in the desktop (local RDP group).

Note: The default Group Policy refresh interval is 90 minutes. You must perform additional steps to force a refresh sooner than that. See the relevant Microsoft documentation for more information.

Access to Local Files with Remote Applications Using File Redirection

The file redirection feature allows users to open local files in entitled remote applications that support given file type.

The feature is enabled in the Horizon Client when the Open local files in hosted applications option is selected.

This functionality allows users to do the following:

  • Open a local file in a remote application by double-clicking the file in the client machine or by right-clicking, selecting Open with, and choosing the remote application in the menu.

  • In the remote application, browse the complete folder where the file resides.

  • Save changes made using the remote application to the local client disk.

  • Register an entitled application as a file handler for the file types that those applications can open, or chose to open with the remote application a single time.

    When an application has been set as the default handler:

    • the file's preview icon will be the entitled application's icon in the application launcher page

    • the file type description will be overridden by the remote application, if any.

    • double-clicking a file of that type will launch the View Client.

Note: File types will be supported based on the extension of the file.

Automatic Agent Pairing

Agent pairing now occurs automatically when you create an image. In the New Image dialog, when you select the desktop to use for the image, the system initiates the pairing process. Within about 30 seconds, the Agent Status will show as Active.

With this new feature, you no longer have to do either of the following:

  • Make the Agent Pairing setting before installing the DaaS Agent.

  • Configure the DaaS Agent after installing it.

Requirements for this feature:

  • You must have the latest agents installed.

  • The image you are creating must on a vSphere cluster. It cannot be on a standalone host.

  • You must remove any stale values for the MonitorAgent.ini and DesktopMgrAddresses registry keys.

  • If you have automation built around the manual pairing process, you will need to make a small update due to the change in the default value of the EnableBootstrap registry key.

    Your updated automation flow should be similar to the following:

    • Download the bootstrap file.

    • Update the MonitorAgent.ini file.

    • Explicitly set the EnableBootstrap registry key to 1.

    • Restart the DaaS Agent service. The Daas agent will now wait for keytool to be run.

    • Run keytool. Once successful, the agent should be up soon after.

    Important: The DaaS Agent service MUST NOT be restarted after the keytool succeeds.

  • Even though the manual pairing mechanism is supported, using the automatic pairing process is recommended.

True SSO (Single Sign-On)

True SSO (Single Sign-On) is a VMware Horizon technology that incorporates VMware Identity Manager, allowing users to authenticate to Microsoft Windows, retaining all of their normal domain privileges, but without providing Active Directory (AD) credentials.

With True SSO, a user can log into Identity Manager using any non-AD method (for example, RSA SecurID credentials) and once authenticated, the user is able to launch any entitled desktop or app (hosted from any domain) without being prompted for a password again.

True SSO uses SAML (Security Assertion Markup Language) to send the User Principal Name (for example, jdoe@example.com) to the identity provider’s authentication system to access AD credentials. The system then generates a unique, temporary certificate for the Windows login process.

  • True SSO is configured on the Active Directory settings page.

  • Before you can configure True SSO your environment must do the following.

    • Configure at least one VMware Identity Manager (IDM).

    • Complete the infrastructure setup for True SSO as described in the Horizon Cloud With Hosted Infrastructure 17.2 Administration guide.

Top of Page

Other Changes in this Release

Auxiliary Account Required for Active Directory Domain Registration

You are now required to include credentials for an auxiliary account when you are registering an Active Directory domain. The username and password for the auxiliary account must exist in the Active Directory for the registration to be completed successfully.

Maintenance Notice Option Removed From Edit Assignment Mode

In previous versions, when you took an assignment offline using the Edit Assignment Mode option on the Assignments page, you had the option to add a custom maintenance notice that would be displayed in the legacy Desktop Portal interface. This option has now been removed.

REST API Changes for RDSH Workflows

There are three categories of REST API changes related to RDSH workflows:

  • Methods supported for VDI assignments but no longer supported for RDSH assignments

  • Methods no longer supported

  • Methods now being used for vIDM

For lists of the APIs in these categories, see Appendix: REST API Changes

Product Support Notices

New DaaS Agent and Horizon Agent

The following new agent versions are available:

  • DaaS Agent 17.2

  • Horizon 7.3.1 Agent (required by the above agent)

It is recommended that you upgrade to DaaS Agent 17.2 and Horizon 7.3.1 Agent once your platform has been upgraded to Horizon Cloud 17.2. If the environment has an older Horizon Agent, the DaaS Agent and Horizon Agent should be upgraded simultaneously.

Desktop Portal Access Not Available After Horizon Cloud 17.2

User access to desktops using the Desktop Portal will no longer be available after the current release. Beginning with the next major release of Horizon Cloud, users will have to access desktops using Workspace ONE, the HTML Access portal, or the Horizon Client.

ThinApps Not Supported for Windows Server 2016

Direct launch of ThinApps is not supported on VMs running Microsoft Windows Server 2016. The latest release of ThinApps provides only experimental support for Windows Server 2016. See the ThinApps release notes for more information.

Best Practices

Knowledge of the following facts is useful before using Horizon Cloud.

Compatibility with other VMware Products

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

Browser Experience

The Administration Console is compatible with recent versions of Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Microsoft Edge. Even though you can try using Apple Safari, use of the Administration Console in Apple Safari is not supported in this release.

Updating Agents on Images and Assignments

The following are minimum agent versions required for using the agent update feature.

  • The image or assignment must already have DaaS Agent 16.6.0.4408091 or higher in order to perform a DaaS Agent update.
  • The image or assignment must already have Horizon Agent 7.0.3.4612900 or higher in order to perform a Horizon Agent update. 

Resolved Issues

The following issues have been resolved in version 17.2.

  • AppStacks with names containing some non-English characters were failing to import successfully. This has been fixed so that import occurs as expected. [1815669]
  • For Dedicated Desktops - Instant Clone assignments, using the Update Agent Software feature to update the Horizon Agent was failing, and also caused any other agents being updated together with the Horizon Agent to fail. This issue has been remedied so that these failures no longer occur. [1849770]

Known Issues

  • In workflows that result in the system creating VMs, such as creating farms, images, and assignments, if you have entered a name that is longer than 12 characters, the name in the system is truncated. As a result, unexpected results might occur from the truncated name.

    Workaround: Limit entered names to 12 characters or less.  [1966118]

  • In the User Activity report, the displayed weekly average (hrs) is not intuitive. Due to this issue, the weekly statistics fluctuate along the time because the calculation logic is dividing the current week's duration by seven (7) and not rounding up to a whole week. For example, when you select the last 30 days, the data for completed weeks is unchanged but the data for the current week is divided by seven (7). The current logic is weekly average (hrs) = daily average (hrs) * 7 days, resulting in the last 30 days weekly average = (total duration / 30 days) * 7 days.

    Workaround: None.  [1817065]

  • When a second RDSH app is opened in the Desktop Portal, the first gets disconnected. If Log Off Disconnected Sessions is set to "immediate" for the farm, then first app gets logged off as well.

    Workaround: Do not set Log Off Disconnected Sessions to immediate.  [1966618]

  • When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails and True SSO cannot be configured successfully.

    Workaround: Use only ASCII characters in the names of your True SSO templates.  [1957829]

  • During a farm's rolling maintenance, reduced availability for end user RDS session desktops and remote applications might occur. If there are no end user sessions on all of the farm's servers just before the maintenance window, all servers are shut down at the same time for maintenance. Then, if high demand occurs for user sessions to the RDS desktops and remote applications that are served by that farm right after the maintenance process begins, the farm will not be able to accept even a single user session for a span of three to five minutes. Administrators are advised to be aware of this risk when planning their maintenance windows.

    Workaround: None.  [1943984]

  • If you add the same group to the Super-Administrator role and the Demo-Administrator role, users in that group will not have full access to all expected functions.

    Workaround: Do not add the same group to the Super-Administrator role and the Demo-Administrator role.  [1963653]

  • You cannot edit the number of sessions per RDSH server once a farm is created.

    Workaround: None.  [1932001]

  • The Administration Console reports a farm's servers' DaaS agents are active and their VMs are in success state several minutes before the VMs are actually ready to use for assigning RDS session desktops and applications using that farm. Due to this known issue, after you create a farm and the Administration Console indicates the farm's servers are ready for you to start assigning RDS session desktops or remote applications using that farm, when you navigate to Assignments screens, you see on-screen messages about needing RDSH servers or farms out of capacity. These symptoms result from the Administration Console reporting the farm's servers are ready several minutes before the connection broker to the Horizon agent on the server VMs is completely ready.

    Workaround: To avoid this issue, delay creating assignments using a farm for at least 15 minutes after the user interface indicates the farm is ready.  [1941076]

  • If you are updating from Horizon Agent 7.0.3 or 7.1.0 to Horizon Agent 7.2.0 or 7.3.0 with both Instant Clone and Persona Manager selected, the update will fail. 

    Workaround

    • Traditional Clone image or assignment:
      • Manual update - Deselect View Composer and Instant Clone during update.
      • Silent install - enter following command.

        VMware-viewagent-x86_64-7.2.0-5748532.exe /s /v /qn VDM_SKIP_ADD_LDAP_MACHINE_ENTRY=1 ADDLOCAL=ALL REMOVE=SVIAgent,NGVC

      • Update Agent Software function in Administration Console - Add the following command line parameter.

        ADDLOCAL=ALL REMOVE=SVIAgent,NGVC

    • Instant Clone image or assignment:
      • Manual update - Deselect View Composer and Persona Management during update.
      • Silent install - enter following command.

        VMware-viewagent-x86_64-7.2.0-5748532.exe /s /v /qn VDM_SKIP_ADD_LDAP_MACHINE_ENTRY=1 ADDLOCAL=ALL REMOVE=SVIAgent,VPA

      • Update Agent Software function in Administration Console - Add the following command line parameter.

        ADDLOCAL=ALL REMOVE=SVIAgent,VPA

    [1904019]

  • When you push updates for a traditional clone assignment, a small number of VMs may enter a PXE boot error state. For example:

    • PXE-E53 : No boot filename received
    • PXE-MOF: Operating System not Found.

    Workaround: This is a storage issue, so there is no workaround in Horizon Cloud.  [1969642]

  • When attempting to create a new assignment or expand an existing assignment, you may see an error indicating that there is not enough capacity to complete the operation, even though you have confirmed that there is sufficient capacity. This occurs because the system sometimes fails to detect additional capacity being consumed by Instant Clone functionality.

    Workaround: Contact your VMware representative to remedy this issue.  [1956345]

  • When you uninstall AppCapture from the Control Panel in a non-English environment, the text in the 'Delete program data?' screen of the uninstall wizard will appear in English.

    Workaround: None.  [1965376]

  • When a user is entitled to a dedicated desktop assignment, that assignment appears under Assignments in the user detail information shown when you click on the user's name in the Administration console. However, after the user launches a desktop from the assignment, it no longer appears in the user detail information.

    Workaround: None.  [1958046]

  • If you click the name of a farm on the Farms page and then click the Servers tab when power operations are ongoing for multiple servers on the farm, the tab might occasionally be blank.

    Workaround: Click the refresh button to refresh the page.  [1974580]

  • If you change the name of a farm or VDI desktop assignment, it takes an hour for the Desktop Health report's Assignment drop-down menu and Assignment column to reflect the new name.

    Workaround: Wait an hour before expecting the new name to appear in the report.  [1756889]

  • The formatting in the CSV files exported from the Desktop Health, Concurrency, and Session History reports do not precisely match the ones you see displayed on the screen. For example, the column headings might be different, the CSV files have more columns of data than in the on-screen tables, and the Session History CSV file gives the last login time as the UNIX time in milliseconds.

    Workaround: None.  [1895363]

  • When the end user clicks the Reset menu action on their browser-based RDS desktop session, the Logoff action is temporarily disabled for up to 5 minutes. To reset a desktop means to reboot the desktop's underlying VM. For RDS desktops where there are multiple users with sessions using the same server, the system appropriately prevents a single user from performing the reset action. However, due to a known issue, when the end user clicks the Logoff action after clicking Reset, a message says the desktop cannot be logged off.

    Workaround: Wait five minutes and then re-click Logoff to log off the session.  [1974704]

  • When users are connected to a VDI host via Blast, data from those users is not included in the bandwidth and latency graphs in the Desktop Health report.

    Workaround: None.  [1969066]

  • In Microsoft Windows Server 2012 R2 and higher, reusing the same farm name with a different domain in the same Active Directory forest can lead to domain join failures due to duplicate service provider names (SPNs). See the Microsoft KB article 3070083.
    Workarounds:

    • Avoid reusing farm names.
    • As described in that Microsoft KB article, disable duplicate SPN checks in the Active Directory domain.

    [1969172]

  • When you click Test Pairing during the True SSO setup process, the system sometimes reports that the pairing failed even though it did not.

    Workaround: If you receive a message that the pairing has failed, wait a minute and retry. Normally this will result in a successful pairing.   [1973565]

  • Some pages in the Administration Console do not display correctly in the Safari browser.

    Workaround: Use a different browser to access the Administration Console.  [1956356]

  • When using the Administration Console in Microsoft Internet Explorer 11, you might see placeholders instead of the actual text strings. This issue is due to static content being cached in the browser. It is a temporary issue that will clear when the browser cache is cleared.

    Workaround: Try logging out of the Administration Console, clearing the browser cache, restarting the browser, and then logging back into the Administration Console.  [1977016]

 

Appendix: REST API Changes

There are three categories of REST API changes related to RDSH workflows, as described below.

Methods supported for VDI assignments but no longer supported for RDSH assignments

Accessing these methods will return UnsuppotedException for RDSH assignments.

Class Name Method Name API Mapping Alternative API
DtPoolImpl assignGroup rest/v100/infrastructure/pool/desktop/{poolId}/assign/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl assignGroup rest/v100/infrastructure/pool/appsession/{poolId}/assign/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl assignGroup rest/v100/infrastructure/pool/session/{poolId}/assign/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl removeGroup /dt-rest/v100/infrastructure/pool/desktop/{poolId}/remove/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl removeGroup /dt-rest/v100/infrastructure/pool/appsession/{poolId}/remove/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl removeGroup /dt-rest/v100/infrastructure/pool/session/{poolId}/remove/domain/{domainId}/group/{groupId} Not Needed for RDSH Pools
DtPoolImpl getUsersAssignedByAdmin /dt-rest/v100/infrastructure/pool/desktop/{poolId}/admin/users Not Needed for RDSH Pools
DtPoolImpl getUsersAssignedByAdmin /dt-rest/v100/infrastructure/pool/appsession/{poolId}/admin/users Not Needed for RDSH Pools
DtPoolImpl getUsersAssignedByAdmin /dt-rest/v100/infrastructure/pool/session/{poolId}/admin/users Not Needed for RDSH Pools
DtPoolImpl assignUserToPool /dt-rest/v100/infrastructure/pool/desktop/{poolId}/assign/user/{guid} Not Needed for RDSH Pools
DtPoolImpl assignUserToPool /dt-rest/v100/infrastructure/pool/appsession/{poolId}/assign/user/{guid} Not Needed for RDSH Pools
DtPoolImpl assignUserToPool /dt-rest/v100/infrastructure/pool/session/{poolId}/assign/user/{guid} Not Needed for RDSH Pools
DtPoolImpl removeUserFromPool /dt-rest/v100/infrastructure/pool/desktop/{poolId}/remove/user/{guid} Not Needed for RDSH Pools
DtPoolImpl removeUserFromPool /dt-rest/v100/infrastructure/pool/appsession/{poolId}/remove/user/{guid} Not Needed for RDSH Pools
DtPoolImpl removeUserFromPool /dt-rest/v100/infrastructure/pool/session/{poolId}/remove/user/{guid} Not Needed for RDSH Pools
DtPoolImpl delete /dt-rest/v100/infrastructure/pool/desktop/{poolId}/delete /dt-rest/v100/farm/manager/farms/session/{poolid}

Method: Delete

DtPoolImpl delete /dt-rest/v100/infrastructure/pool/appsession/{poolId}/delete /dt-rest/v100/farm/manager/farms/session/{poolid}

Method: Delete

DtPoolImpl delete /dt-rest/v100/infrastructure/pool/session/{poolId}/delete /dt-rest/v100/farm/manager/farms/session/{poolid}

Method: Delete

DtPoolImpl getVirtualMachines /dt-rest/v100/infrastructure/pool/desktop/{poolId}/vms /dt-rest/v100/farm/manager/farms/session/{poolid}/allservers

Method: GET

DtPoolImpl getVirtualMachines /dt-rest/v100/infrastructure/pool/appsession/{poolId}/vms /dt-rest/v100/farm/manager/farms/session/{poolid}/allservers

Method: GET

DtPoolImpl getVirtualMachines /dt-rest/v100/infrastructure/pool/session/{poolId}/vms /dt-rest/v100/farm/manager/farms/session/{poolid}/allservers

Method: GET

DtPoolImpl isVMRefreshRequired /dt-rest/v100/infrastructure/pool/desktop/{poolId}/refresh/required Not Needed for RDSH Pools
DtPoolImpl isVMRefreshRequired /dt-rest/v100/infrastructure/pool/appsession/{poolId}/refresh/required Not Needed for RDSH Pools
DtPoolImpl isVMRefreshRequired /dt-rest/v100/infrastructure/pool/session/{poolId}/refresh/required Not Needed for RDSH Pools
DtDesktopPoolImpl get /dt-rest/v100/infrastructure/pool/desktop/{poolId} Not Needed for RDSH Pools
DtDesktopPoolImpl getUserDesktopMappings /dt-rest/v100/infrastructure/pool/desktop/{poolId}/user/desktop/mappings Not Needed for RDSH Pools
DtDesktopPoolImpl update /dt-rest/v100/infrastructure/pool/desktop/{poolId}/update Not Needed for RDSH Pools
DtDesktopPoolImpl getAllVirtualMachines /dt-rest/v100/infrastructure/pool/desktop/{poolId}/allvms Not Needed for RDSH Pools

Methods no longer supported

The methods listed below have been deprecated and will be deleted in the near future. Accessing these methods will return DtApiException.

Class API Method
DtSessionPoolImpl /dt-rest/v100/infrastructure/pool/session/{id} get
DtSessionPoolImpl /dt-rest/v100/infrastructure/pool/session/{id}/update update
DtSessionPoolImpl /dt-rest/v100/infrastructure/pool/session/{id}/updateServerDensity updateServerDensity
DtApplicationSessionPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/remoteapps getRemoteApplications
DtApplicationSessionPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/updatewithapps updateWithApplications
DtApplicationSessionPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/setcmdlineparam setCommandLineParam
DtApplicationSessionPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/getcmdlineparam getCommandLineParam
DtRemoteApplicationImpl /dt-rest/v100/infrastructure/pool/{poolid}/remoteapp/{id} get
DtApplicationImpl /dt-rest/v100/infrastructure/pool/application/{id}/update update
DtApplicationImpl /dt-rest/v100/infrastructure/pool/application/{id} get
DtUserDefinedAppImpl /dt-rest/v100/infrastructure/pool/user/defined/application/{id}/delete delete
DtPoolManagerImpl /dt-rest/v100/pool/manager/create/session/pool createSessionPool
DtPoolManagerImpl /dt-rest/v100/pool/manager/create/session/pool/{elementId} createSessionPool
DtPoolManagerImpl /dt-rest/v100/pool/manager/create/appsession/pool createApplicationSessionPool
DtPoolManagerImpl /dt-rest/v100/pool/manager/create/appsession/pool/{elementId} createApplicationSessionPool
DtPoolManagerImpl /dt-rest/v100/pool/manager/applications findApplications
DtPoolManagerImpl /dt-rest/v100/pool/manager/create/userdefinedapp createUserDefinedApp
DtPoolManagerImpl /dt-rest/v100/pool/manager/delete/userdefinedapp deleteUserDefinedApp
DtPoolManagerImpl /dt-rest/v100/pool/manager/upload/userdefindappicon uploadUserDefinedAppIcon
DtPoolManagerImpl /dt-rest/v100/pool/manager/modify/userdefinedapp modifyUserDefinedApp
DtDesktopPoolImpl /dt-rest/v100/infrastructure/pool/desktop/{poolId}/remoteapps getRemoteApplications
DtGoldPatternImpl /dt-rest/v100/infrastructure/pattern/gold/{id}/applications getApplications

Methods now being used for vIDM

The methods below will work only for vIDM. They will be marked as deprecated, but will not return an exception.

Class API Method
DtApplicationSessionPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/applications getApplications
DtPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/groups getGroupsOfPool
DtPoolImpl /dt-rest/v100/infrastructure/pool/appsession/{id}/users getUsersOfPool
DtPoolManagerImpl /dt-rest/v100/pool/manager/pools getPools
DtPoolManagerImpl /dt-rest/v100/pool/manager/mapping/users/pool getDesktopPoolOfUsers
DtApplicationIconImpl /dt-rest/v100/infrastructure/application/icon/{md5sum}/icon getIconData