Applying OSD Task Sequence to System But Keep Existing Image

[BzowK]

Hey Guys -

Our company has an extensive OSD Task Sequence which incorporates many scripts and custom processes. For a variety of reasons, it's been decided that we start using Dell's ImageDirect. In this scenario, once we unbox systems, they want OSD to still be applied - but to the existing image on the PC - not re-apply the OS

 

I created a Windows 7 image via imagedirect, downloaded it, and applied it to a test system. Currently, it would boot to Windows' mini-setup if powered on. I took our existing OSD TS and basically removed any steps where OSD applies the image, but steps which come after it that are still required are failing.

 

For example, for a test I did this afternoon, the "Apply Win7 Settings" step would fail which usually comes after Apply OS image, but as it's disabled, errored out with the below in logs:

 

Failed to read installation type from environment.. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.
Unspecified error (Error: 80004005; Source: Windows) (more below)

 

As I found all of the info in that step is already in the ImageDirect image, I disabled it and tried again. This time, it failed at the "Apply Network Settings" step. These settings (including joining the domain) are obviously not in ImageDirect's image.

What is the best way to approach working with what I've been asked to do?

 

Thanks!

UPDATE

 

I sent an email to Dell's ImageDirect Support today asking a similar question. I showed them how we currently prep a new system versus what we were trying to do with ImageDirect giving the two scenarios below:

 

Our Current Solution

Currently, our company does the following when receiving a new system from Dell to get it ready for a user:

1. Unbox

2. PXE boots to SCCM/WinPE boot image

3. Applies an SCCM OSD task sequence which partitions, formats, and installs Windows 7 x64 Ent

The same OSD task sequence is extensive and aside from installing the OS, applications, and joining domain, it performs numerous configurations.

Proposed Solution with ImageDirect

We are testing starting to use ImageDirect and propose to instead do the below steps

1. Unbox

2. PXE boot to SCCM/WinPE boot image

3. Apply the same task sequence – EXCEPT – for the steps which partition, format, and apply the OS (keeping ImageDirect's OS/image)

Their reply was that what we are trying to do is different than what most customers do with ImageDirect and suggested that we apply any required settings using Group Policy. Based on the fact that their solution is Group Policy without asking the depth of the task sequence we are trying to apply made me believe that perhaps the person who replied may not be familiar enough with OSD so still don't consider my issue answered.

So - I wanted to update my post to ask a couple of questions:

My Questions

1. If I have a system which doesn't have the client installed nor is joined to the domain to PXE boot it to an SCCM Boot / WinPE image then start a task sequence which will Apply Network Settings (Join the domain), install the SCCM client, then proceed with non-OS related TS steps?

2. The reason I am so fixated on PXE is that if we had to use ImageDirect, we could boot a new system, go through mini-setup and into Windows, join the domain, install the client, then start a task sequence; but having to do all of that manually would take forever and defeeat the purpose of OSD in the first place. Do you have a suggestion to accomplish this using a better method?

3. The biggest reason we are testing using ImageDirect over the current solution of installing WIndows during OSD is drivers. We are a Dell shop and currently support ~6 models. I keep our SCCM Driver database up to date using model specific enterprise CABs and use model-specific driver installation steps in our OSD TS. Still, though, we have sporadic issues with drivers not being installed & not being installed correctly. It's gotten to the point where I've added a Full Driver Installation task sequence to the end of our OSD TS which has a group per model - each with individual & conditioned steps which install the full driver package downloaded from Dell. It's the only way we can have a consistent result. I've also tried the two types of Driver Installation steps (by driver package & by category) which both have similar results. Do you have suggestions for something which may remedy this issue instead of even going the ImageDirect route?

The only other main reason we were going with ImageDirect is BitLocker. The systems we have come in from Dell for some reason come with Professional installed as our only option. Since we use BitLocker which isn't supported on Pro, we must re-image them via OSD to apply Enterprise.

So - Any suggestions for any of the above or this entire scenario? Thank you!

[anyweb]

sounds like there's an error in the unattend.xml file, try pausing the deployment before the apply windows settings step and see what it contains in c:\windows\panther\unattend\unattend.xml,

 

Before the Setup Windows and ConfigMgr step is complete you can monitor c:\windows\panther\unattend\unattend.xml to see what is happening in relation to your modifications taking place or not

After the Setup Windows and ConfigMgr step is complete, you’ll see the following has been added to your c:\windows\panther\unattend.xml file