[sccm 2012] Windows 7 Image Capture

[lmrogers]

Hi All,

 

I'm having trouble with capturing a Windows 7 image using SCCM 2012 R2. I have built the task sequence and it builds fine but something happens after preparing the ConfigMgr Client and preparing the OS. It does not fail with any error code though, it just does not go through the capturing process.

 

I have a Windows 8.1 task sequence for build and capture set up and running absolutely fine.

 

 

Thanks in advance

[Qas]

Is the OS that you are trying to capture activated?. If not, activate it and try again.

[lmrogers]

We do not activate Windows in our task sequences, they are activated after deployment through our KMS server. There is a Windows 7 image/task sequence on our server that was made by the person that used to work here, which is set up in the same way and has made a successful capture.

 

I just can not see whats wrong/different.

[Qas]

I have seen this issue before where our KMS server hadn't yet activated the computer. As a result, I was unable to capture it. After manually activating it against our KMS server the problem went away.

[lmrogers]

I have tried putting our KMS key into the task sequence but it fails. When it does not capture it will not login either it comes up with a User Profile Error. Also the reference machine is never joined to our domain.

[Arthur]

I'm having trouble with capturing a Windows 7 image using SCCM 2012 R2.

Are you creating your image in a VM?

[Qas]

Run slmgr.vbs /dlv and see what the remaining windows rearm count. If it is 0 then your capture will fail.

 

If you are not running the capture on a vm check out this post http://support.microsoft.com/kb/2525084/en-us?wa=wsignin1.0

Edited February 6, 2015 by Qas

[Norphy]

Make sure that the command prompt is enabled in your boot image. Try to capture your image again and when it fails, press F8 to bring up the command prompt. Look for the SMSTS.log file (I think its in x;\windows\temp\logs but I can't remember off the top of my head) and copy it to a USB stick or map a network drive and copy it onto that. Examine the log file in the cmtrace.exe log viewer that cones with ConfigMgr and post what the error is. There will be an error of some kind and hopefully that'll explain it in something resembling English

[free780]

Are you using sccm software updates? Some updates trigger a double reboot.

You shouldn't need to activate to capture. If you can activate non domain PCs your kms must be set up fairly insecure.

[lmrogers]

Yeah I'm using a VM for my build and captures, I've checked the logs and there is nothing about why its failed to capture, the only errors there seem to be are application installation failures. We are not using SCCM software updates either.

[lmrogers]

Looking at the task sequence it was deployed to all machines for media and pxe, i deleted those deployments and set up a deployment for my build and capture collection and it seems to working now, its just capturing the reference machine now.