Capture img OK - Install that captured img NOK

Hi,

I'm having this strange thing:

I have a base HP image for thin clients.

This base image can be used in a task sequence for installation of existing image package, no problems occur.

The problem occurs when I first build and capture from this base image, then use it to install as an existing image.

During the build and capture there seems to be no obvious problem, it runs and finished nicely with all updates and software in it.

When I deploy the captured image it stops after the step "Setup Windows and Configuration Manager". It simply stops going further and the TS finishes with errors 0x80004002 and 0x80004005.

I feel tempted to reduce the problem as follows: When an installation went through the "setup windows and configuration manager" once, it can't run though it for a second time. It seems unable to switch from PE to full os mode in an installation TS, after being captured with SCCM in a capture TS.

Two different scenarios:

1. I use the base image in an installation task sequence, I manually captured the image with imagex and added it in an installation task sequence. I experience exactly the same problem.

2. I mount the base image (dism) and do some offline stuff on it (file copy and updates etc), I capture the image with imagex and add it in an installation task sequence. I DO NOT experience the problem.

So it looks like I can go through the "Setup Windows and Configuration Manager" process once, but not twice.

Does the capture task sequence not handle the ConfigMgr client correctly? In scenario 1 I made sure the client was removed with "ccmsetup /uninstall". There seemed to be no errors in the installation/uninstallation logs either during the capture TS, or even installation TS. Also after installation of the installation TS, when the problem occur, the ConfigMgr client is perfectly functioning.

Is there an obvious thing going on here? Could it be related somehow to the write filters? I don't think so since it works fine in scenario 2.

I can post some logs but I'll have to go through it again first to obtain them.
But these are the errors that occur in SMSTS.log:

Error Task Sequence Manager failed to execute task sequence. Code 0x80041002
Failed to create an instance of COM progress UI object. Error code 0x80040154
ReleaseRequest failed with error code 0x80004005

SCCM 2012 SP1 - 7804.1600
Server 2008 R2

Really could use some help here.

Regards!


  • Edited by Jazz.be Friday, May 22, 2015 3:49 PM Adding specs
May 22nd, 2015 3:41pm

What I'm trying now is to Build a new image with B&C TS but I disabled the last step group, the one that does the preparation and the capture.

I'm capturing the image manually with imagex (I did remove ConfigMgr manually) and then I'll try to use that image.

If it works, then I'm tempted to think that something in the step group "Capture the reference machine" in the B&C TS is making it impossible to go through the "Setup Windows and Configuration Manager" later in the installation TS.

EDIT: The installation TS stops at installation of the ConfigMgr Client. Apperantly the write filters are turned on, which makes it impossible for the ConfigMgr Client to be installed. If I want to proceed with this test I have to disable the write filter either before capturing the image, or in the installation TS before the ConfigMgr Installation. I'm not sure if the latter is possible, since the computer is in WinPE the whole time before that critical step.
When I let the TS do the whole Build and Capture I'm not running into this write filter error.

EDIT2: I booted from the captured image, the one that I build with SCCM but captured manually with imagex, and I noticed that the write filters are disabled. Though when used in an installation TS it stops because of errors "Cannot install over embedded OS with WF enabled on the system drive". So I guess I can't test this scenario. Not sure how write filters are turned on once it's used in a TS. Is there a parameter in imagex?
  • Edited by Jazz.be Tuesday, May 26, 2015 3:43 PM Update
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 11:53am

Yes I captured a new image after upgrading to CU5.

Did you add a PATCH= option to Setup ConfMgr step or not? It doesnt matter, did you upgrade site server or not, the OSD part should be taken care of additionally.

http://blogs.technet.com/b/ryanan/archive/2014/01/31/applying-a-configmgr-hotfix-during-the-client-installation-of-an-os-deployment.aspx

I do make sure the client is also updated to CU5 during installation, I did not use the patch switch however, I used the less supported method of putting the msu in a subfolder.

But it works, the clients (even when the TS fails) are nicely upgraded to CU5 version.

June 2nd, 2015 12:00pm

But it works, the clients (even when the TS fails) are nicely upgraded to CU5 version.

There are issues using this method. Don't use it.
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2015 12:08pm

There are issues using this method. Don
June 2nd, 2015 12:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics