VMware Horizon View - CMID of Instant Clones not changing

[DSJordan]

Hello!

We are testing out Instant Clones with Windows 10.  We had trouble with App Volumes in this particular environment, so we abandoned that for this deployment.  We have very few Windows 10 machines in our environment, so when the gold image tries to activate it cannot because there are < 25 machines.  I tried turning up 30 Instant Clones but the CMIDs were all the same, so none of them activated.  I tried doing slmgr / rearm on the gold image, shutting it down, taking a snapshot, and then starting 30 machines, but they all had the same CMID.

When should the CMID get changed when using Instant Clones?

Thanks for any help!

Scott

[Ray_handels]

It doesn't, that's why it's called Instant clone.. It creates a child machine from a running virtual machine thus not doing a quickprep/sysprep.

If you would like to do this, your easiest way is to use Linked clones with a composer. This way, if you use Quickprep, you can create enough machines for it to work.

[obie3335]

I am having the same issue. The CMID is not changing each pool created has the an unique CMID for the pool.

How do we get Windows 10 to activate using the KMS server? Is there a way?