MDT - Lenovo Sysprep and Capture failing

[Decimas6]

Hi,

 

We have some new Lenovo B50s here, of which I've been trying to capture a Windows 8.1 Image on through my MDT sysprep and capture task sequence, but it keeps failing. The task sequence will run, it will get to step 16/23 (Execute Sysprep), Sysprep will pop up, get to the "Processing generalize phase" and hang there for hours until cancelled, Deployment workbench will display it as "unresponsive". The same task sequence works perfectly other machines, with the same OS, only difference being brand/hardware.

 

Now, I can sysprep the machine manually, but after that I have no way of capturing the image. Is there some sort of capture only task sequence I can set up and run in Windows PE?

I will post the BDD log on Monday when I can, but does anyone have any ideas why sysprep keeps going unresponsive this way?

 

(I know that creating images is best done on a clean VM, but we don't have virtualization facility at the moment.)

[cooka]

You could sysprep it manually, set it to shutdown after sysprep, make a winePE stick and use Imagex to capture the image. Boot from the winpe media and capture with imagex..

 

Imagex.exe /capture C:\ \myimage.wim 'MyImage'

 

Building winpe with imagex - https://emeneye.wordpress.com/2012/04/13/creating-a-winpe-usb-drive-with-imagex/

Building winpe - https://technet.microsoft.com/en-us/library/cc709665(v=ws.10).aspx

[jamesfed]

Is this Windows 10 that you are trying to sysprep? If so have you removed any of the built in 'Modern UI' style applications before the sysprep?

[Arthur]

Is this Windows 10 that you are trying to sysprep?

Windows 8.1.

 

 

- - - Updated - - -

 

I know that creating images is best done on a clean VM, but we don't have virtualization facility at the moment.

Could you not install Hyper-V on a PC running Windows 8.1 Pro or Enterprise?

[jamesfed]

How about removing Windows 8.1 built in apps (through PowerShell script by way of example) then? If so you could be running into this error - Windows 8.1 SCCM sysprep fails – (0x00004005) | my world of IT

[Decimas6]

As I left on Friday I updated the deployment share and set off the task sequence in one last hope, and to my surprise (because I don't think I changed anything) it got passed Sysprep, and looked like it was going to work. Coming in this morning, it had failed, but with a different error at least! Not enough space to create the WIM. After a bit of searching I am guessing what happened is that it tried to use one of the UEFI partitions while creating the WIM, instead of the C partition. I can't see a specific way around this anywhere, and unfortunatly no logs or error codes were saved, just that it was related to ZTIDiskpart.wsf.

 

Windows 8.1.

Could you not install Hyper-V on a PC running Windows 8.1 Pro or Enterprise?

 

I could, but I don't have a machine with more than 4GB of RAM, which makes things a bit difficult.

 

 

How about removing Windows 8.1 built in apps (through PowerShell script by way of example) then? If so you could be running into this error - Windows 8.1 SCCM sysprep fails – (0x00004005) | my world of IT

 

This could be it, but why would I be able to sysprep normally and not through a task sequence?

[Arthur]

I could, but I don't have a machine with more than 4GB of RAM, which makes things a bit difficult.

Is it possible to temporarily borrow some additional RAM out of another PC to bump it up to 6GB or 8GB?

[Decimas6]

Is it possible to temporarily borrow some additional RAM out of another PC to bump it up to 6GB or 8GB?

 

The only machines capable would be the IT PCs, but I'm not likely to get 2 of them taken out of use. I think I will just have to take the image using one of the old laptops and hope everything sticks.