rseekell
Enthusiast
Enthusiast

Horizon Linked Clones Pool - Reuse Desktop Names

We’d like to have the automatic linked-clone pools reuse computer names.  Example: Lab of 30 has pool of 30 and naming convention of W10-012-{n:fixed=3}.  If we have to delete machines, then they come back as 031, 032, etc.  But we want it to start over at 001 and stay within the range of 001-030. 

Here are some of our pool settings:

Refresh Immediately after logoff,   Provision all machines up-front,   Name pattern with three fixed digits at the end.

In an example pool, 28 max, 24 spare, and 0 minimum, and the ending numbers are currently 004-031.

Allow reuse of pre-existing computer accounts, which doesn't have an effect on this issue.

The pool is completely enabled.

This is a concern because of a classroom management program.  It scans all the given computer names, and is not very efficient, so we limit the number of machines it has to search.  Some schools have over 100 desktops, so their pools have 3 fixed digits.  In that case, the classroom management program would have up to 1000 names to potentially scan – and we really want to avoid that.

There is a setting in the ADAM database described here in the KB.  It sounds like a setting for a different type of pool than we’re using, but the setting does exist and cause the above desired behavior. The problem is that it is not presented in the GUI or API or PowerShell, and when I edit the pool (at least in the GUI), it resets this setting. 

So question #1, is there a supported way to have the names reused?   #2, is there a way to preserve the setting in the ADAM database per the KB article linked above?

5 Replies
parmarr
VMware Employee
VMware Employee

I believe this doc would help , please refer https://docs.vmware.com/en/VMware-Horizon-7/7.2/com.vmware.horizon.virtual.desktops.doc/GUID-ED99E02...

Sincerely, Rahul Parmar VMware Support Moderator
0 Kudos
Erossman
Enthusiast
Enthusiast

Are you using horizon 7.2.0? There is a know issue with reusing names...

After an upgrade to Horizon 7 version 7.2, the VM name reuse functionality with naming pattern configuration does not work, which causes provisioning issues.

Please upgrade to horizon 7.3.2 or higher.

DDunaway
Enthusiast
Enthusiast

0 Kudos
williamgregoryi
Contributor
Contributor

Hello rseekell,

I had this same issue and after working with support it was reveled that although this issue is "Fixed" in 7.3.2 you will have to edit ADAM to set the pools to allow the reuse of existing computer names. The GUI pool settings say yes, but ADAM was not set to allow.

1. VMware Knowledge Base - 2012377

2. Once connected to ADAM you will see "OU=Server Groups". The entry to modify is "pae-VmNameReuseAllowed" and set it to a value of "1".

3. Restart provisioning on the pools.

Issue should be resolved.

Have a great day!

0 Kudos
Carston
Contributor
Contributor

I am attempting to disable this setting in 7.3.2, and one specific pool will not allow the disable. I attempt to change the setting in ADAM, but that change is not reflected in the UI, and the AD objects do not get deleted/recreated. Any ideas to fix that?

0 Kudos