i have a vcenter 6.5u3 setup with 3x hosts and i’ve been trying to make a new ESXi template of windows 2012 r2 (and eventually a template of win 2016 server) with these items covered:
– a new/unique windows SID (on each vm creation from template)
– new windows computer name (ie “WIN-GEVW232WED” – although I realize I can manually change this one after deploy)
– using the windows admin or administrator account and keeping all of my template’s apps, desktop items and settings (ie i install bginfo which shows stats on the desktop background)
I understand really the only/proper way to create a template where on each new deploy there will be a new/unique Windows SID, is to run sysprep as the final step of my template creation, before i send the template to my vcenter content library.
however sysprep essentially resets my administrator account, so I lose all of my apps settings and other items I set up in the original template (for example Bginfo is gone).
i made another template, and didn’t run sysprep at the final step, and of course all of my administrator account settings/apps were *not* wiped, however the windows SID and computer name are exact duplicates of the templates/other clones.
The only solution I have read/come across, but have not tested is (during my template creation) to create a new Windows account, for example “Bob”, set it as administrator, then apply all of my apps/settings, and run sysprep at the final step.
so i have 2x questions, please:
1-do I lose any win privileges or functionality by using an account like Bob set as admin, versus using the built-in admin/administrator account? (I know security best practices is to disable the win administrator account, but these are mostly tests/lab VM‘s)
2- what is the best way to create this template such that all of my apps/settings aren’t wiped on each deploy (but i still achieve the 3x requirements i have at the top of this post)?
View Reddit by jimmy58743 – View Source