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

I suspect you have lost network connection when you get to this point.  Make sure you have the correct drivers being applied after the OS install and before this step..  Also, when you get to this step, open a command prompt (F8) and see if you have an

I am also concerned about you removing the ConfigMgr client. Did you actually do a ccmsetup.exe /uninstall in your B&C? If so, that is unnecessary and you should let the B&C do the Prepare ConfigMgr Client for Capture' s

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.

• Edited by Jazz.be 16 hours 5 minutes ago Update

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.

• Edited by Jazz.be Tuesday, May 26, 2015 3:43 PM Update

Take a look at ccmsetup.log, if your TS stops at Configuring CM client step.

Also it sounds for me that you have some king of a hazard thingy going on there, why to do stuff with imagex?

If youre planning to use only ConfMgr for every deployment, just use original Capture template to create the image with ccm client inside, dont disable any steps. Remember to integrate latest CU to your Setup ConfMgr step in B&C and deployment TS By using =PATCH command. CUs have some potetial bug fixes to OSD, and they are only applied during TS, if you enter the =PATCH path.

Take a look at ccmsetup.log, if your TS stops at Configuring CM client step.

Also it sounds for me that you have some king of a hazard thingy going on there, why to do stuff with imagex?

If youre planning to use only ConfMgr for every deployment, just use original Capture template to create the image with ccm client inside, dont disable any steps. Remember to integrate latest CU to your Setup ConfMgr step in B&C and deployment TS By using =PATCH command. CUs have some potetial bug fixes to OSD, and they are only applied during TS, if you enter the =PATCH path.

It's getting confusing with all the test scenarios I've been describing.

The root problem is still that my installation stops even though I completely used SCCM for capture and for installation.

I use imagex to bypass the capture step in SCCM, to see if that step is contributing to the problem.
I'm trying that because when I do the install with a base image I have no problem. The problem only occurs if I complete a B&C with SCCM. So something is wrong in that captured image I'd say.

Yes I'm on CU5

Is the CU5 also in the image?

When your Deployment stops, what your smsts.log and ccmsetup.log is telling you?

Is the CU5 also in the image?

When your Deployment stops, what your smsts.log and ccmsetup.log is telling you?

Yes I captured a new image after upgrading to CU5.

These are some errors that happen when the deployment stops:

ReleaseRequest failed with error code 0x80004005 TSManager
Task Sequence Manager could not release active TS request. code 80004005 TSManager
Process completed with exit code 2147749890 TSMBootstrap
Exiting with return code 0x80041002 TSMBootstrap
Process completed with exit code 2147749890 OSDSetupHook
Task sequence completed 0x80041002 OSDSetupHook

Back to my test scenario:

I used the standard B&C task sequence to build my machine, but I disabled the capture steps.
I captured the machine manually with imagex, and it works.
The task sequence ends with error code 0, though some errors still appear, some same as the ones above.
But the task sequence seems to work now.

Difference between working scenario and non working scenario is the Capture steps in the B&C task sequence. 

I checked the logs from the capture and there seems to be nothing wrong.
The task sequence and ccmsetup ends with error code 0
We're deploying R2 soon so perhaps that would help.