Is it recommended to user Pre-configured Windows SQL VM Template

[jafumon87]

for SQL server deployment using vRA, we use a standard Windows template and after a Windows VM is deployed, SQL installation kicks in automatically(called by the properties in VRA) using VB script and the SQL set up files are placed in a Temp folder. Problem is this is taking longer time to deploy VM.

So can we prepare a template which already has SQL installed, there by reducing deployment time.

If yes are there any pre-requests that should be taken care while preparing the template,

Concerns are : 

After a new VM is deployed it should change the SQL instance name with the VM name.

there should not be any SID conflicts since we deploy from template.

Any suggestions on how do to it?

[hawks76]

We use a clean image and deploy SQL after provisioning occurs. Creates less manual work and creates a more standard environment to reduce issues. SQL (and subsequent CUs, SPs, SSMS & SSDT) adds about 40 minutes to our build time, but it has been well worth it, as we never have any issues with SQL builds.