• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1841
  • Last Modified:

SCVMM 2012R2 VM deployment not inheriting admin password

Greetings Experts -

We recently created an SCVMM 2012R2 server which is using WS2012R2 as its OS.  That box is managing a single Hyper-V server running WS2012R2.  Before I go into details about my setup I'll ask up front "the password entered into the template does not carry over into the deployed VM - why?".  Here's how I get to that question.

I've created the most basic template possible out of a 2012R2 VM.  I did this via:
-> in the SCVMM 2012R2 admin console I go to the "VMs and Services" screen
-> right-click the target VM to be templated and chose "Create > Create VM template"
-> for the template name I enter something like "2012R2 Controller"
-> I leave the "Configure Hardware" screen at defaults
-> on the "Configure Operating System" screen I confirm the "Operating System" field is correct, I put * for "Identity Information", I put in a complex Admin Password, I put in a known-good product key
-> on the "Select Library Server" screen I chose the only Library server we have
-> on the "Select Path" screen I browse to the "Library\Templates" folder
-> on the Summary screen I press "Create"
-> after that is done I go to the "Library" screen and then to "Templates > VM Templates"
-> I right-click "2012R2 Controller" that I just made and go to "Properties"
-> on the "Hardware Configuration" screen under "Cloud Capability Profiles" I checkmark Hyper-V
-> on the "OS Configuration" screen I confirm that all the info I entered during the template creation process is still there
-> I press "OK" to close the window

Then I create a new VM from that template via:
-> in the SCVMM 2012R2 admin console I go to the "VMs and Services" screen again
-> I click "Create Virtual Machine" from the menu ribbon up top
-> on the "Select Source" screen under "Use an existing virtual machine, VM template, or virtual hard disk" I look under "Type: VM Template" and choose "2012R2 Controller" that I made above
-> on the "Identity" screen I put in a name for the new VM such as "2012R2 test deploy"
-> I leave the "Configure Hardware" screen at defaults
-> I leave the "Configure Operating System" screen at defaults as all my previously entered data is still there
-> on the "Select Destination" screen I choose the default "Place the virtual machine on a host" with "Destination: All Hosts"
-> on the "Select Host" screen I choose our only host
-> I leave the "Configure Settings" screen at defaults
-> I leave the "Add Properties" screen at defaults
-> on the "Summary" screen I press "Create"

Deployment of the new VM begins, but when it gets to 81% it stops.  I right-click the VM and choose "Connect or View > Connect via Console".  I then see the VM sitting at the sysprep deployment screen asking for me to enter an Administrator password.  Huh?  Didn't I put this in earlier?

My question - why is the administrator password not inherited from the wizard as I put it in?  This was never an issue in SCVMM 2008R2 so I'm not sure what's going on here.  It seems pretty straight forward and seems like it should 'just work' but maybe I'm missing something?

  • 2
1 Solution
annexitAuthor Commented:
A quick follow-up.  After some additional testing I found that using the same procedure for a Windows 8.1 x64 template results in the deployed VM being stuck as well, but this time at the 'PC Name' screen... and the PC name is clearly set to * in the template, so it should be automatically generated.

Interestingly using the same procedure with Windows 7 x64 does NOT have any of these issues...

I'm starting to think this is a glitch in the admin console.
annexitAuthor Commented:
I figured this out.  I copied these VMs from a SCVMM 2008R2 system where I had to manually sysprep the VMs before making them into non-customized templates (as SCVMM 2008R2 doesn't know how to template 8/2012+ via the usual GUI method).

When they were copied to the SCVMM 2012R2 system I forgot to delete the unattend.xml file inside the VM at C:\Windows\System32\Sysprep.  Apparently leaving an unattend.xml file there overrides the settings in the GUI during deployment as the unattend.xml settings were configured to prompt for a machine name (in 8.1) and for an admin password (in 2012R2).

After deleting the unattend.xml file and re-templating the VM I can now deploy these without issue.

Education experience for sure.  :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now