Just-in-Time Management Platform

JMP Is Here! See It Live at VMworld

Earlier this year, we introduced our Just-in-Time Management Platform(JMP—we pronounce it “jump”) to blow apart the desktop status quo. It&#rsquo;s evolved into something truly special that will change the way you provision desktops.

Tuesday, 5 p.m., at VMworld U.S.is your first chance to see this game-changing technology. There&#rsquo;ll be beer, cake references and the unstoppable Harry Labana (@harrylabana), vice president of management services and strategy for VMware End-User Computing (EUC).

VMworld 2017 Breakout Session:

Modernize Management with JMP Technologies in VMware Horizon & Take a Look at Where We Are Headed”

Add ADV1608BU via VMworld U.S. schedule builder.

Too Complex. Too Slow. Too Many Breakpoints.

Most of you use a static desktop provisioning model that makes it difficult for you to:

  • Deliver workspaces quickly and efficiently to all users and endpoints.
  • Be agile to end-user requests.
  • Keep up with OS updates and patches (especially with Windows 10).
  • Manage application and OS dependencies.
  • Respond when something goes wrong.

Just-in-Time Delivery

JMP is our answer to those problems. If I were in marketing, I&#rsquo;d sell it to you as “Simple. Fast. Bulletproof.” But I&#rsquo;m not; I&#rsquo;m a product guy. So, instead I&#rsquo;ll tell you that I recognize that you&#rsquo;re currently working too hard, fighting with yesterday&#rsquo;s provisioning tools and struggling with infrastructure that&#rsquo;s beyond its sell-by date. And I want to help.

In a JMP-managed world, you define the desktop workspace that your users want, but leave the building of it to our automation engine. JMP offers a single integrated console that leverages VMware Instant Clone Technology, VMware App Volumes and VMware User Environment Manager to deliver tailored workspaces built from a common gold image.

User-Centric Automation

You identify your users (individuals and groups), tag their desired attributes (policies, apps, infrastructure, etc.) and press go. The JMP engine then automates the creation of bespoke desktops that exactly meet your users&#rsquo; needs. On the device they want.

It&#rsquo;s as simple as it gets.

It gives you more time, flexibility and, oddly, control.

Too Complex. Too Slow. Too Many Breakpoints. Solved.

Going back to how we started this blog, JMP&#rsquo;s dynamic engine gives makes it easy for you to:

  • Deliver workspaces quickly and efficiently to all users and endpoints.
  • Be agile to end-user requests.
  • Keep up with OS updates and patches.
  • Manage application and OS dependencies.
  • Respond when something goes wrong.

Moving from a static to an automated management model gives you numerous benefits. Not least amongst them is the fact that you only consume resources when your users call upon them. No more pre-provisioning. No more downtime for patching. Just-in-time delivery across your entire desktop estate.

Cloud Ready

With JMP automating the actual desktop building, simply changing the target environment for your users can move someone from an on-prem environment to a hybrid or cloud based one. You now have a solution that leverages the infrastructure you&#rsquo;ve built, to deliver the desktops your CTO told you to prepare for.

See for Yourself

We like to say that we&#rsquo;re making managing virtual desktop infrastructure (VDI) a piece of cake. Everyone likes cake, right? Join Harry and I at VMworld, and get a sneak peek at the future of JMP—we&#rsquo;ll give you beer and maybe even cake. Possibly even a copy of Fusion 10. You should be there.

The post JMP Is Here! See It Live at VMworld appeared first on VMware End-User Computing Blog.

Read more..

Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7

The best practices guide for published applications and desktops in Horizon 7 and Horizon Apps is now available!

This guide is intended for anyone installing or administering published applications or published desktops in Horizon 7 or Horizon Apps. Readers should already be familiar with basic installation and administration procedures, such as those described in Publishing Applications with VMware Horizon 7.

When deploying a Horizon 7 or Horizon Apps RDSH-based published application and desktop solution, administrators will want to consider a number of best practices. Areas of consideration include VMware ESXi host sizing, RDSH image configuration and optimization, Horizon 7 configuration and policies, antivirus solutions, provisioning, and recurring maintenance.

Administrators will also want to consider integrating VMware JMP technologies, which include VMware Instant Clone Technology, VMware App Volumes, and VMware User Environment Manager. With our latest release of VMware Horizon 7, just-in-time delivery of virtual desktops is extended to include published applications delivered from RDSH servers, bringing increased speed, scale, and simplicity.

Be sure to download and read Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7.

To comment on this paper, contact VMware End-User-Computing Technical Marketing at euc_tech_content_.

The post Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7 appeared first on VMware End-User Computing Blog.

Read more..

Just-in-Time Apps with VMware Horizon 7

With our latest release of VMware Horizon 7, Horizon 7.1 extends just-in-time delivery of virtual desktops to include published applications delivered from Remote Desktop Session Hosts (RDSH) and powered by the Just-in-Time Management Platform, or JMP, bringing increased speed, scale, and simplicity. With Just-in-Time Apps, you dramatically simplify deployments with a tightly integrated stack, fewer components, and easy maintenance by using VMware Instant Clone Technology.

This blog covers what an instant clone is and how it works, how to start using instant clones for RDSH, and what maintenance options are available. We also provide some best practices.

What Exactly Is an Instant Clone?

Instant Clone Technology leverages vmFork, which uses rapid in-memory cloning of a running parent virtual machine in a quiescent state, and copy-on-write to rapidly deploy virtual machines.

(Thanks to Duncan Epping for the original of this diagram: Project Fargo aka VMFork – What is it?)

A running parent virtual machine is brought to aquiescent state, then child VMs are spawned (forked) from the parent with a unique UUID/MAC, and the disk is rebased on the replica disk and resumed. The child VMs are then prepared with new network settings (machine name, MAC address, and so on) and restarting of the quiesced services. Because these child VMs utilize the replica disk and shared memory pages from the host, there is no dependency on the parent after cloning. Both memory and disk are copy-on-write, so if a child modifies bits of its memory or disk, a separate copy is made for that virtual machine. All of this happens without any operating system restarts.

What Benefits Do Instant Clones Bring to the Deployment and Management of RDSH?

Instant clones allow you to deploy RDSH servers more rapidly, scale more easily, and perform maintenance up to 85 percent more quickly than was previously possible. Instant clones improve security by regenerating and automatically refreshing RDS hosts on a scheduled basis. Instant Clone Technology requires half the required steps compared to View Composer when deploying or scaling.

(Thanks to Fred Schimscheimer for this diagram: VMware Instant Clone Technology for Just-In-Time Desktop Delivery in Horizon 7 Enterprise Edition.)

How Do I Provision RDSH Instant Clones with Horizon 7?

Horizon Administrator is the web interface through which you configure the Connection Server and manage your remote desktops and applications. To use instant clones, you need to add a user account privileged to join machines to the domain, create a master image, and set up a farm.

  1. Configure instant clones.

a. In Horizon Administrator, selectView Configuration>Instant Clone Domain Admins and click Add.

b. Type the username and password, and click OK.

2. Create a master virtual machine.

a. Create an RDS host virtual machine.

b. Install the Horizon Agent with VMware Horizon Instant Clone Agent selected and VMware Horizon View Composer Agent deselected.

c. Shut down the VM and take a snapshot.

3. Create a farm with the wizard by navigating to Resources > Farms and clicking Add.

a. On the Type page, select Automated Farm.

b. On the vCenter Server page, select Instant Clones and the vCenter Server used for the RDS hosts.

c. On the Identification and Settings page, provide a name in the ID

d. Complete the Provisioning Settings Here you can select how many RDS hosts you want to create and how many should stay available during maintenance operations to make sure users are not impacted.

e. On the Storage Optimization page, you can select whether to use vSAN and separate datastores for replica and OS disks.

f. On the vCenter Settings page, point to the image and snapshot created in Step 2, and select the datastores, cluster, resource pool, and network to be used.

g. On the Guest Customization page, select the domain-join account created in Step 1, and select the AD OU where the RDS hosts will be created. Optionally, you can provide scripts with parameters to adjust the RDS host during the customization process.

Creation Process

The creation of the VM template, replicas, and parents is the publishing—also called priming—process, and the creation of the RDSH VMs (the instant clones) is the provisioning process.

Publishing is done only when you create a new farm or make changes and want to update an existing farm to reflect the changes. Publishing the master image can take from 7 to 40 minutes, depending on the type of storage and number of hosts you are using. Provisioning the servers takes only 1 or 2 seconds per server. You can perform these tasks at separate times by not enabling provisioning in the Add Farm wizard, so that the provisioning process occurs either at a scheduled time or immediately after the publishing process is complete. When you scale up the pool, all that needs to be done is provisioning.

The provisioning process does not require power operations, and the clones are forked from a running parent VM, so the process takes only a couple of seconds. The engine customizes each forked instant clone. This ClonePrep process performs the following customization tasks in roughly 30 seconds, all without requiring a reboot:

  • Gives the VM a unique MAC address
  • Updates the computer account password
  • Restarts quiesced services
  • Joins the machine to the Active Directory domain
  • Activates the Microsoft license

Example deployment times (including waiting times) in our testing lab are as follows:

Instant Clones Composer Linked Clones
Total for 1 and then scaling to 51 RDS hosts 9 minutes 45 seconds 35 minutes 56 seconds
Template creation 3 minutes 38 seconds N/A
Replica creation 3 minutes 58 seconds 3 minutes 4 seconds
Parent creation 13 seconds N/A
Clone 1 RDS host 2 seconds 25 seconds
ClonePrep SysPrep (for 1 RDS host) 26 seconds 13 minutes 38 seconds
Total for 1 RDS host 8 minutes 17 seconds 17 minutes 7 seconds
Clone 50 RDS hosts 48 seconds 4 minutes 1 second
ClonePrep / SysPrep (for 50 RDS hosts) 40 seconds 14 minutes 48 seconds
Scaling from 1 to 51 RDS hosts 1 minute 28 seconds 18 minutes 49 seconds

In the previous table, note how quickly you can scale from 1 to 51 RDS hosts, with instant clones: in 1 minute 28 seconds.

In the testing lab, 200 RDS hosts can be instant cloned, including template/replica/parent creation, in less time than View Composer takes for replica creation and a single RDS host!

How Do I Ensure My RDS Hosts Stay Optimal and Up to Date?

Horizon 7 allows for easy modification of the RDS host and farms. You can use the Maintenance Wizard to either schedule automatic or recurring maintenance, or perform an out-of-band, emergency update.

  • A recurring maintenance schedule ensures that the clones are periodically regenerated. Any potential contamination is removed so that the farm runs optimally. Recurring maintenance at a specific time can be scheduled on a daily, weekly, or monthly basis.
  • Immediate maintenance can also regenerate the clone but is typically used to update the farm with patches or other updates to the master image. Immediate maintenance can optionally be delayed to a future date and time, such as after business hours.

If you perform maintenance with the current master VM and snapshot, all that needs to be done is provisioning, but you can also make changes to the master and use a new snapshot, or use a different master and snapshot.

It is possible to choose whether to log users out or wait for them to log out before performing maintenance.

Best Practices to Consider When Deploying RDSH

  • There are two recommended virtual CPU configurations when deploying RDSH. Which one works best depends on the actual application workload and is something that should be tested before making a final decision:
    • 4 sockets with 1 core per socket with a 1:1 virtual-to-physical CPU ratio
    • 8 sockets with 1 core per socket with a 2:1 virtual-to-physical CPU ratio

Make sure the ratios do not span CPUs.


The hosts used for the RDSH cluster have two Intel Xeon Processor E5-2699A v4 (a total of 22 cores).

The hosts should run a maximum of 2 (physical CPUs) * 1 (1:1 ratio) * 20 (physical cores rounded down to the closest multiple of 4) / 4 (virtual single core sockets) = 10 RDSH VMs and not 11.

This amount is equal for both ratios. The extra cores are not lost, but used for virtual networking, storage, and other host tasks.

  • The amount of memory assigned should be assessed by actual application usage. We recommend reserving the full amount of memory to make sure accidental over-commitment does not occur and no disk space is wasted with unused swap files.
  • We recommend installing all available updates to Microsoft Windows and other Microsoft products with Windows Update or WSUS when creating the image. You may have to first manually install Windows Update Client for Windows 8.1 and Windows Server 2012 R2: March 2016.
  • Run the VMware OS Optimization Tool with the default options, which can reduce the resources needed by Windows Server by 15 percent. The tool speeds up Windows and gives users a faster and better experience.

One optimization that you might want to disable is TCP/IP Offload in the HKLM settings when all host network cards are capable of offloading.

  • Space reclamation is recommended. By reducing the vmdk size that expanded by patching Window