No, I Will Not Fix Your #@$!! Computer → Customize Guest Issue

We have a Windows 2008 R2 Template that's used to spawn VM's from. Upon creating the new VM, we use the "Customize the operating system" mainly to change the SID.
We don't use a custom sysprep file, the server is NOT joined to the domain (the NIC is turned off anyway), and the administrator password is left alone.

The problem we run into is after the server boots up from performing the sysprep stuff, we are unable to log into the server using the administrator password. Yes, we know the password. I've actually converted the template to a VM, changed the password, then cloned with the same results. No access using the administrator password. Have i tried creating an alternate account to see if I can get in that way? No...but that's a fine idea and I will do so right now.

It seems the sysprep is hosing up the administrator password.

Edit - Guess I should have mentioned we're using vSphere 5.1. Not digging the web client.

Did the password get changed in the customized template within the Customization Spec Manager? Converting the actual template changing the password will do nothing when using the customization.

Also, after deploying, there is a time where it is just the default install, then the OS will reboot and the customization will take place.

Is the local administrator account active? Last time I had to create a template for 2008 R2 for some RDS servers I ran into issues with Sysprep disabling the local administrator account.

I ended up doing as you said already and created a separate local admin account in the template and using that to get it on the domain.

Are you using any sort of unattended file to customize the server?

I have a 2008R2 template that I ran sysprep on and then shutdown > converted to Template, then when deployed it asks me to set the password on first run.

Changing the password in the customization wizard does nothing. The password is still unknown. I even tried making the password on the template blank, but no luck. I did notice when the Administrator password was blank, upon first boot I would automatically be logged into the server. I then changed the password and allowed the server to reboot for the sysprep changes. When it came back up, I still couldn't log back in.Yes. The local administrator account is active. I can log into it when the template is a VM.No. To my knowledge there is no unattended file being used.

I ended up creating a 2nd account with admin rights and just using it to log in. I'm still not sure what the issue is, but can't really spin my wheels on this anymore. Thanks for everyone's input.

Did you read my second line that there is a period of time that it take for the customization to happen. On our here, it sits for about 5 minutes, reboots and then does the sysprep/customization.

I feel that either 1, the password is incorrect in the customization, (which is easily changeable). 2, If you have more than one customization your selecting the wrong one. 3, Your not letting it get to the point of rebooting to do the customization.

I'm not a VMware expert, but there is something off here.