Quantcast
Viewing all articles
Browse latest Browse all 497

VMware View Planner multi-remote PCoIP test with linked clones

So I was able to run the VMware view Planner local mode test no problem, however, I am having some troubles trying to do it with linked clones here.  I think part of my problem is that the instructions I am following in the user guide here are a bit unclear.  The part that is confusing to me is on page 56 of that document it says to use "View to Provision a Pool of Desktop Linked Clones.  Follow the View documentation to provision as many clones of the desktop template virtual machine as you wish to test. These should be created as an automated linked clone pool with floating assignment. You must also use identical values for the pool_id and poolname parameters. "

This is fine, however, right underneath that it says to "Use vCenter to Provision Client Linked Clones" and then goes on to explain the steps needed.  So do I need to create a view clone pool and create Client Linked clones in vCenter?  That seems unnecessary.  However, in the instructions for actually running the test headed "Create a Multi-VM VDI Run Profile," step d says:


In the Desktop / RDSH Name Prefix: field, enter the VM name prefix you provided in “Use View to Provision a Pool of Desktop Linked Clones” on page 56.


and step j says:

In the Client Name Prefix: field, enter the VM name prefix you provided in “Use vCenter to Provision Client Linked Clones” on page 56.


I tried just creating a clone pool using view, I based it off the snapshot that is created once the view planner client installer completes, I named the pool_id and poolname the same, as well as the prefix of all the VMs.  However, when I try to run the test, it doesn't work.  Any clarification here would be greatly appreciated.  I'm using a brand new installation of vsphere 5.5 U2, view 6, and view planner 3.5. 


Viewing all articles
Browse latest Browse all 497

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>