If you’ve ever run into this error when composing linked clones with VMware Horizon View Composer, you are very much not alone. This is a common error that ultimately comes down to this: your Composer database already has an entry with that VM name in it. There are 3 ways to fix it depending on your View version and scenario. But first, let’s understand the issue.
The ADAM database is the heart and soul of your Horizon View environment. It contains all sorts of great stuff from Pool inventory, to persistent disk assignment, to licensing information. Long story short, if you lose your ADAM database, you straight up lose. Be a winner and backup your database!
Using the Horizon vCenter Orchestrator (vCO) plugin allows you to automate provisioning tasks, allow end user self-service tasks, configure entitlements and more in VMware Horizon 6 thereby reducing the need for internal email correspondence and exception handling.
I love me some Apple. However the Pebble Smart Watch cannot be ignored!
Guest Post Ahead! If you are a VMware user that has discovered the joys and simplicity of Virtual Appliances, you have probably run in to applications built on top of VMware Studio’s VAMI utilities. VAMI is the background service that provides the administration page for configuring and updating VMware Studio-based appliances.
Horizon 6 brought us many exciting changes. One of the more memorable ones is the addition of support for certified Linux Guests. At the time of this writing, Horizon 6 supports RHEL 6.6, Ubuntu 12.04, CentOS 6.6, and Neoukylin 6/6U1.
Trying to use NTFS with your OwnCloud server? You may be running into some challenges.