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.
- Edited by Jazz.be 15 hours 57 minutes ago Adding specs