Technical Introduction

Technical Introduction


JMP (pronounced jump), which stands for Just-in-Time Management Platform, represents capabilities in VMware Horizon® 7 Enterprise Edition that deliver Just-in-Time Desktops and Apps in a flexible, fast, and personalized manner. JMP is composed of the following VMware technologies:

The JMP approach provides several key benefits, including simplified desktop and RDSH image management, faster delivery and maintenance of applications, and elimination of the need to manage “full persistent” desktops. JMP is supported with both on-premises and cloud-based Horizon 7 deployments, providing a unified and consistent management platform regardless of your deployment topology.

With the Horizon Console and the VMware Horizon JMP Integrated Workflow features, you can use a single console to define and manage desktop workspaces for users or group of users. You create a desktop workspace by defining a JMP assignment that includes information about the desktop pool, the App Volumes AppStacks, and User Environment Manager settings. After you submit the JMP assignment, the JMP automation engine communicates with the Connection Server, App Volumes, and User Environment Manager systems to entitle the user to a desktop.

Purpose of This Tutorial

The Quick-Start Tutorial for VMware Horizon JMP Integrated Workflow helps you evaluate JMP Integrated Workflow features by providing a discussion of the product and offering practical exercises.

Important: This tutorial is designed for evaluation  purposes only, based on using the minimum required resources for a basic  deployment, and does not explore all possible features. This evaluation  environment should not be used as a template for deploying a production  environment. To deploy a production environment, see the VMware Horizon 7 documentation.


This tutorial is intended for IT administrators and product evaluators who are familiar with VMware vSphere® and VMware vCenter Server®.  Familiarity with networking and storage in a virtual environment, Active Directory, identity management, and directory services is  assumed. Knowledge of other technologies, such as VMware Horizon 7 is also helpful.

Introduction to JMP

In the early years of VDI, the operating system (OS) for each virtual desktop had to be managed and patched regularly, and applications had to be updated, just as if the VM were a physical machine. In recent years, linked-clone technology sped up VM creation, provisioning, and maintenance, but maintenance windows were still required for refreshing the VM back to its original disk size. The VM also had to go through a lengthy recompose operation to apply OS and application updates. And at regular intervals VMs had to be rebalanced across datastores.

Today with JMP, components of a desktop or RDSH server are decoupled and managed independently in a centralized manner, yet reconstituted on demand to deliver a personalized user workspace when needed. For example, because VMs can be cloned in seconds, they no longer need to persist when the user logs out. App Volumes, a container-style technology, can attach applications to a VM when the user logs in. User preferences and settings for each application are applied when the user launches the application.

How JMP Works

JMP offers an alternative to managing per virtual machine. JMP decouples each aspect of a desktop to allow it to be managed on a per-user or per-group basis. As illustrated in the following figure, application-management containers are managed separately from the desktop OS. Similarly, user data files and OS- and application-specific configurations are decoupled from the OS and kept on separate file shares.

Figure 1: How JMP Technologies Manage Virtual Desktops, Settings, and User Data

The following components of JMP work together to compose a just-in-time personalized desktop:

  • User Environment Manager share  A file share that stores user-specific desktop and application settings, making them available across multiple devices, Windows versions, and application instances.

    Application settings are imported and applied at application launch. Windows settings (such as the desktop background, desktop screensaver, keyboard settings) are imported at login. When a user quits an application, or logs out of the OS, settings are exported and saved on a file share.
  • User data share  A file share that stores personal user data, documents, pictures, and so on that are redirected from specific folders inside the VM. This strategy minimizes the number of files that must be copied to the VM when the user logs in.
  • AppStack  A read-only container for one-to-many delivery of IT-managed applications. For virtual desktops, AppStacks are assigned to an Active Directory user or group, and assigned AppStacks are attached to the desktop when a user logs in.
  • Writable volume  A one-to-one, user-specific, read-and-write container for user-installed applications or for applications that require a local cache, since a writable volume appears as part of the local C: drive.
  • Instant clone  A new type of cloned VM that is created using vSphere vmFork technology to rapidly clone both the memory and the disk of a running parent VM.

You use the Horizon Console to access the JMP integrated workflow. With this one user interface, you create an assignment that defines which elements to use from all three products: View in Horizon 7, App Volumes, and User Environment Manager.

Component Requirements

The JMP integrated workflow requires that the following versions of the Horizon 7 components be installed and set up:

Note: Although you can also integrate JMP with VMware Workspace ONE through VMware Identity Manager, such integration is beyond the scope of the exercises in this tutorial. For more information about this integration, see the VMware Horizon 7 documentation.