Hello all,
Just curious on how quickprep works with linked-clones. according to this table it doesn't do a sysprep. So even though you are created linked clones from snapshots wouldn't you still need a new SID per clone otherwise GPO's and other Active Directory processes would get confused or see SID conflicts?
Function | QuickPrep | Sysprep |
Removing local accounts | No | Yes |
Changing Security Identifiers (SID) | No | Yes |
Removing parent from domain | No | Yes |
Changing computer name | Yes | Yes |
Joining the new instance to the domain | Yes | Yes |
Generating new SID | No | Yes |
Language, regional settings, date, and time customization | No | Yes |
Number of reboots | 0 | 1 (seal & mini-setup) |
Requires configuration file and Sysprep | No | Yes |
Have a look at this thread and see if the explanation they provide helps. https://communities.vmware.com/message/1120905
Have a look at this thread and see if the explanation they provide helps. https://communities.vmware.com/message/1120905
Yup that pretty well clears it up. Thanks mittim12,
However if we plan on pushing out a Microsoft KMS server later on, I'm guessing I would be better off to use the VMware sysprep option in View 6 linked clones deployment instead of quick deploy?
We license via KMS and have never had any issues as a result of quickprep.
As an added note, it generally doesn't seem to be an issue with AD SIDs but rather applications tied to SIDs that tend to be an issue and generate the requirement to use Sysprep over Quickprep.