Quick question, hopefully.
Is there a way to limit the way that VMWare View 3 names VMs that are
automatically generated? In other words, if I say I want a maximum of
10 VMs, currently View will name them PC1, PC2, etc to PC 10, but then
if I have a machine destroyed, the next PC will be PC11. I'd like to
force view to reuse machine names, so that I only ever have PC1 - PC10
I'm deploying VMWare View 3 as a pilot program at my company. We have a
piece of licensed software that is very expensive, and while our
licensing agreement allows for virtualization, the license assignment
is based off of workstation name. We'll have hundreds of users logging
into this system, but only a portion of those at any given time, and if
we can force View Manager to restrict the naming of the new VMs that
are spawned it'd be an easy way to enforce licensing compliance while saving money. I could use
persistent VMs, but half the beauty of View is that I can destroy the
VMs automatically after one use and spawn off a new one, giving
everyone a fresh, clean machine to work on.
Couple questions.
1) When you delete the VM, are you also deleting the desktop from within the View Administrator?
2) Are you using a Custom Guest Customization spec? If so, when you specify the computer name, are you using a specific name or having the computer name be the same as the VM name?
-Lazlo...
I'm using an automated desktop pool with linked clones, and in View Manager I set the clones to automatically delete themselves after first use.
I've noticed a similar problem. I have a non-persistent pool and the machine numbers kept increasing. What I found worked for me was to disable provisioning, and then delete the desktops via the view admin. Once VC deleted all the VMs, I re-enable provisioning and it started back at 0001.
-jonathan
In my deployment, I now have gaps in the Virtual Desktop naming scheme, as I've removed some desktops in the mix, I never had to delete the whole pool so far
I wish this could be fixed in the next release of View.