Recently, I have been working with Instant Clones in my lab. Although I have found this easy to get up and running (for more information, see my blog here), it hasn’t been easy to find best practices around configuring Instant Clones, as they are so new.
I reached out to the engineering team, and they provided me with the following best practices for using Instant Clones in VMware Horizon 7.0.2.
Check OS Support for Instant Clones
The following table shows what desktop operating systems are supported when using Instant Clones.
|Guest Operating System
||64-Bit and 32-Bit
||64-Bit and 32-Bit
||Enterprise and Professional
For more information, see the architecture planning guide.
To read the rest of this blog please check it out on VMware.com here
With the release of VMware Horizon® 7 and VMware Identity Manager™ 2.6, it is now possible to configure VMware Identity Manager to work with Horizon Cloud Pod Architecture when deploying your desktop and application pools over multiple data centers or locations.
Using VMware Identity Manager in front of your VMware Horizon deployments that are using Cloud Pod Architecture makes it much easier for users to get access to their desktops and applications. The user has just one place to connect to, and they will be able to see all of their available desktops and applications. Identity Manager will direct the user to the application hosted in the best datacenter for their location. This can also include SaaS applications as well as the applications that are available through VMware Horizon 7.
For the full blog please see my blog on VMware.com
One of the great new features in VMware Horizon 7 is the ability to stop desktop administrators from accidentally deleting a desktop pool that is currently full of active desktops. Once this feature is enabled the administrator will have to delete all of the desktops before deleting the desktop pool.
In this blog I will document how to configure the Desktop Pool Deletion feature. Before you configure this setting you should be aware that this is a global setting and as such once enabled it will be enabled for all desktop and application pools.
Follow these steps to enable the Desktop Pool Deletion feature
- Upgrade all Connections Servers to Horizon 6.2
- Note that signed Certificates are required
- Start the ADSI Edit utility on the View Connection Server host.
- In the Connection Settings dialog box, select or connect to DC=vdi,DC=vmware,DC=int
- In the Computer pane, select or type localhost:389
- Double click on the object CN=Common, OU=Global, OU=Properties
- Edit the pae-NameValuePair attribute
- Add the value cs-disableNonEmptyPoolDelete=1
- Click Add and OK
- Now when you try and delete a pool you will see the following message