View 7.2 running under ESXi 6.0 Update 3
160 View desktops with this numbering scheme: Student001, Student002, ...Student160
I remove Student007, View spins up a new desktop to keep the total at 160 but the new desktop is named Student161 instead of Studen007
In other words I still have 160 desktops but Student007 is not there but Student161 is
Never saw this behavior under previous versions of View. Under previous versions all desktops were always consecutively numbered
Any idea if there is a fix?
couple of maybe stupid questions:
The service account I am using is a Domain Admin so yes it has the proper priviledges
I did not have the box checked to re-use computer accounts. I checked that box, removed a few desktops and observed the same behavior where new desktops where spun up higher in the number range
I stop provisioning, deleted all desktops except 2, enable provisioning and got Student001....Student160
I then removed 5 desktops and 5 new ones were spun up, Student161...Student165
Still looking for a solution
I opened a ticket with VMWare and this is a known bug in View 7.2. A fix will be released in View 7.3
In the Adam database the value of pae-VmNameReuseAllowed is set to 0 when it should be set to 1
Does anybody know if VMware has a patch available for 7.2 which fixes the issue? I would like a permanent solution without relying on users to manually run ADSI edit after creating new pools. This is for a customer that will not have the budget to hire professional services for the 7.3 upgrade when it comes out, and was hoping to stay on 7.2 for quite a while.
Thanks!
I agree.
I have hated this so much. I wish this would get fixed.
I have a Horizon 6.2.4 Deployment and use Dedicated Desktops. When we terminate an employee we nuke the VM and a new one generates to replace it. It always goes to the bottom of the list adding a new one.
I wish Horizon was smart enough to see the missing VM and replace it instead of running up the VM ID's. Does not take long to get the VM ID's int he naming to get out of control over time.
If I could ask VMware for something I would ask them to get smarter about VM generating looking for gaps in the naming scheme so you could slot in replacements in missing holes.
Horizon 7.3 is available for download
Here are the release note, I do not see this under resolved issues
7.3 pulled out from download
new update will come in 5 Octobor , hope they will cover this issue
I opened a ticket with VMWare support. They told me two things
The first one is good news. The second one is surprising, not sure why VMWare would not list every fixed problem in Resolved Issues is beyond me
I still see View 7.3 in downloads, it is October 2nd. Where did you hear it was pulled?
We face the same issue regarding numbering scheme. I was unable to find a KB to this issue.
It would be nice to have an official statement regarding this issue and the remove of Horizon 7.3.
Unofficial sources:
Horizon 7.3 Release Pulled Temporarily
HendersonD
Are you sure you are able to download it? For me the final link to the binary is not available.
also Vmware send email
You are correct, I am not able to download 7.3. I can get to the download page where it is listed but the link does not work. I am glad I did not download it and deploy it given the bug they found. Waiting for the new code to be posted
Horizon 7.3.1 is available to download. I upgraded the lab here yesterday, so far so good. Haven't tested linked clones yet, only instant. I'll see if the bug was fixed at some point today.
Please let us know if provisioning linked clones works and whether this update fixes the original problem of numbering VMs when one is removed
Ok.. here's my environment:
Horizon 7.2 upgraded to Horizon 7.3.1
Created a new pool "BugTest" - contains 2 VM's - BugTest-01 and BugTest-02
Deleted BugTest-01
Horizon automatically created a new VM named BugTest-01
Checked ADSI edit for the pool settings, PAE-VmNameReuseAllowed is set to <not set>
Seems to be fixed, although I don't fully understand why the PAE-VMNameReuseAllowed is set to <not set>
Thx for sharing your acknowledgement.
I am still waiting for an official VMware KB, which tells me how to workaround the bug. I don't like to update the environment again.
I have a pool called Sandbox. The master image is called Sandbox0 and there are only three desktops, Sandbox001, Sandbox002, and Sandbox003