VMware Cloud Community
dchmax
Contributor
Contributor

Issue with deploying Windows 2008 R2 from a customized template

I'm having an issue with deploying a W2K8 R2 server from a customized template. I start out by building a W2K8 R2 VM from scratch, install tools, and install patches. Once the VM was shutdown I converted it to a template. When deploying without customizations I have no issues. When I use customization I get the following message.....

"autochk program not found - skipping AUTOCHECK"

....then BSOD

"STOP: C000021a Fatal System Error

The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a"

and the process repeats. Any direction at this point would be wondering. Thanks in advance.

David

Reply
0 Kudos
26 Replies
vmroyale
Immortal
Immortal

Hello.

What version of vCenter are you using?

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
Reply
0 Kudos
dchmax
Contributor
Contributor

vCenter 4.1, esx host are 4.1 as well.

Reply
0 Kudos
dchmax
Contributor
Contributor

Has anyone else had this issue and was able to resolve it?

Reply
0 Kudos
arnie123
Contributor
Contributor

I have the same problem. Can't find a reason or a solution for this either.

Have you managed to get any further insight?

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Seems a Windows related problem...

Have you verify that the template can boot?

Have you add some 3rd part programs?

For example:

http://www.diskeeper.com/blog/post/2009/12/30/Program-not-found-skipping-AUTOCHECK-revisited.aspx

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
dchmax
Contributor
Contributor

The template boots when I do not customize. The template is pretty bare, no third party programs. I have a ticket open with support but we are not really getting anywhere. I'm pretty sure a Windows 2008 R2 templete is supported in my configuration so I figured they might have some insight.

Reply
0 Kudos
ESA75
Contributor
Contributor

I have the same problem with Win2008R2 on ESXi 4.1 (vCenter 4.1).

Does this problem has a solution?

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Which kind of license are you using?

I use multilicense Windows Server 2008 R2 (enterprise & datacenter) and I've no problem (on 4.1).

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
dchmax
Contributor
Contributor

Really not sure. The keys are from a Select 7 agreement. Not sure how to tell. It is Volume Licensing.

Reply
0 Kudos
ESA75
Contributor
Contributor

In my case the cause of problem was Windows 2008 R2 MSDN.

When I try make customased clone from normal (not MSDN) Windows 2008 R2, I had no problemm.

Reply
0 Kudos
MattG
Expert
Expert

Any known cause or resolution for this issue?

-MattG

If you find this information useful, please award points for "correct" or "helpful".

-MattG If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
dchmax
Contributor
Contributor

No such luck here. Support seems to have many open cases and will be opening a case with MS soon.

Reply
0 Kudos
ldrouet
Contributor
Contributor

Hi,

I've got the same problem here with Vsphere 4.1 and vcenter 4.1.

Is there any feedback from the support ?

Best Regards

Ldr

Reply
0 Kudos
brapoport
Contributor
Contributor

I had the same issues when I created a Template from a windows server machine, while it was still running. After re-creating the template from a shutdown original VM, the issue went away.

cdc1
Expert
Expert

I can confirm that re-creating the template from the parent VM while it's powered off is the solution to this.

I just had a customer with the same problem.  They had created a template from a powered-on Windows Server 2008 R2 VM and, after deployment, upon startup they received the BSOD.

They shutdown the parent VM, re-created the template from it, and now deployment works fine.

dchmax
Contributor
Contributor

I'll go ahead and test this and see if the issue goes away.  Not sure if this matters but are you registering your OS with MS before creating the template?

Reply
0 Kudos
dchmax
Contributor
Contributor

So I finally had time to run through the motions  again and it seems to have worked.  Built a Windows 2008 R2 Std VM on ESXi 4.1 Build 320137.  Here are the steps I followed.

- installed W2K8 R2 Std via ISO

- Installed tools

- manually loaded the correct display adapter driver (VMware SVGA 3D WDDM)

- shut the VM down

At this point I've not activated or entered a key

- converted to template

- deployed W2K8 from template

- custom deployment, system name, key, ect

- boot new VM

- once at log on prompt I let it sit, after about 30 sec it shutdown and sysprepped the system

- all looks good.

I'll update if I run into more issues.

CDC and Brapoport, thanks for your help.  I'm trying to figure out how to give you guys points.  Make a post and I'll mark it the solution.

Reply
0 Kudos
mnisadmin
Contributor
Contributor

I had the same problem.

Virtaul center 4.1 update 1

ESXi 4.1 update 1

guest - win2008R2 64bit

When I tried to clone the vm > I got autochk program not found

The solution was to shutdown the guest then clone it.

Reply
0 Kudos
gjacknow
Contributor
Contributor

I had the same error when cloning a running VM.   While it would seem you can avoid the situation by shutting down the VM when clonng or creating a template...Sometime you can't do that.  I found a solution to fix the issue in the comments here: <http://briandesmond.com/blog/how-to-sysprep-in-windows-server-2008-r2-and-windows-7/

You need to boot the VM off the windows disk and choose repair and command prompt.  You will probably have to get into the VM bios to change the boot order to boot of the CD.  then...

#34 re: How to Sysprep in Windows Server 2008 R2 and Windows 7

Friday, April 08 2011 10:17 PM by Dan

Same problem with "Autochk program not found. Skipping autocheck."

Fixed by clearing nodefaultdriveletter volume attribute via:

diskpart

list volumes

select volume 1

attributes volume

attributes volume clear nodefaultdriveletter

Reply
0 Kudos