T
theta121
I have a 2016 server template that I've created in Vsphere 6.5. When I deploy a VM from this template and use the vmware customization specification (sysprep option to change server name and join this vm to the domain), it is changing the NTFS permissions on the entire root of the D: drive so that all authenticated users have full modify permission at the root of the drive. If i manually deploy a VM from this template and manually change the name and add to domain, the permissions are not being affected. This only happens when running through sysprep. I have already opened a case with Vmware and they said i had to talk to Microsoft as they have no control over what sysprep is doing. There are no special scripts or any other commands being run during sysprep; it only changes the VM name and adds it to the domain. Do you have any idea what is changing NTFS permissions on the deployed servers? I've tried this with two completely different 2016 templates and two different customization specifications and it's happening on all of them. This is not happening with 2012 R2 servers. The OS is installed on C: and the D: drive is for application installations. Any ideas how to keep sysprep from changing NTFS permissions?
Continue reading...
Continue reading...