Windows Linked Clones & Sysprep

[gamename]

Hi,

I am able to create linked clones without any trouble (thanks LucD!). But, the windows LCs always keep the name and SID of the "parent" and they never join the domain. 

What should I do differently in the linked cloning process so that they auto-configure themselves with a new machine name, SID and join the domain?  I assume that means rerunning sysprep somehow. Correct?

Looking through the docs I could find, there doesn't seem to be a definitive answer.

Thanks,

-T

[mattboren]

Hello, gamename-

As part of the cloning process, are you specifying an OSCustomizationSpec to be used to customize the new VM?  That would be a way to:

1. change the guest OS "hostname"
2. generate a new SID
3. join the new VM to a domain
4. etc.

If not, give it a try with one.  If so, are you having problems with the OSCusSpec applying?

[gamename]

Those questions pointed me in the right direction.  I had not added the existing template (which did the SID changes) into the customization spec for the linked clone.

Thanks for the help.