User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive


I have used the latest version of the ENGL Driver Manager (latest internal BETA) software to create driver packages and application packages in my SCCM 2012 RC test server.
The appropriate packages have been created successfully and are visible within the SCCM 2012 Console.
The packages were distributed to the distribution point then added to an existing task sequence


The Task sequence reports an error when attempting to deploy it:

This task sequence cannot be run because the
program files for SCO00015 cannot be located on a distribution point.

Resolving the error:

To review the actual error message within the WinPE environment:

  • Press F8 to launch a command window (this needs to be configured in the appropriate boot image properties page)

  • Launch cmtrace.exe from the command prompt.

    (cmtrace.exe is a replacement for trace32.exe and is included by default in the WinPE boot image)

  • Accept the prompt to make this the default log viewer.

  • Open x:\windows\temp\SMSTSLog\smsts.log file. This gives all the information about the task sequence and any errors.

Reviewing the log file I get the following error(s)

Failed to resolve selected task sequence dependencies. Code(0x80040102)

A google search on this error code gave some useful information but nothing that appeared to help resolve the issue.

I then switched back to the System Center 2012 Configuration Manager Console. SCCM 2012 has a different look and feel to SCCM 2007 which makes things interesting when tracking things down.

The console has a "Monitoring" section. This has several options that let you check the status of different SCCM 2012 components.
Selecting Overview -> Distribution Status -> Content Status allows you to check the status of individual packages.

Select the Package that is reporting an error. In this case SCO00015

Right Click on the package then select View Status

Four tabs are now visible

Success Status information is currently unavailable for this deployment
In Progress Waiting for prestaged content
Error Status information is currently unavailable for this deployment
Unknown Status information is currently unavailable for this deployment

Reviewing the "In Progress" Asset Details the description says:

Distribution Manager is waiting for the package SCO00015 content to be prestaged on the distribution point. 
You must manually prestage the package SCO00015 on the distribution point before the content will be available.

This confirms that the package has not been updated on the distribution point.

Switching back to the Software Library > Overview > application Management > Packages > VMware, Inc.

I can view the packages created by Driver Manager.

Right click on the VMware-Virtual-Platform-Win7-x86-2 package (SCO00015)
Select Properties
Review the package details.

Distribution settings has the setting "Manually copy the content in this package to the distribution point" set.

Change this option to "Automatically download content when packages are assigned to distribution point"
Click apply.
Right click on the package.
Select "update distribution point".
The distribution point now updates successfully.
Reviewing the content status for the package it shows

Content was distributed to distribution point

PXE booting the virtual machine I now have a task sequence that deploys successfully.

I have reviewed other packages that were created by Driver Manager or created manually. These default to "Automatically download content when packages are assigned to distribution point" and as expected distribute successfully to the distribution point when assigned.

At some point when initially reviewing the package properties I must have been changed the distribution setting without noticing!

SCCM2012 looks different to SCCM2007 which makes troubleshooting issues interesting until you find your way around the console.
Prestaging content is also a useful feature to have if you are aware that it exists and don't enable it on a package by mistake!

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

We have had reports that the Windows 7 unattend process can stall at the "completing installation" screen.

This can occur in the following scenario:

  • VMWare virtual machine
  • Windows 7 iso attached to virtual machine
  • USB pendrive containing unattend files attached to virtual machine

Remove the USB pendrive once the Windows 7 installation process has rebooted for the first time.

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

When deploying an Imaging Toolkit project to a machine we expect to have administrator rights in order for the deployment process to complete successfully.

ZENworks DLU and GPO policies can be inherited by the machine as soon as it is registered. These policies may then impact on the local user the build is using when then may cause problems with phase 3 of the build process.

We recommend that any policies that are inherited by the deployment process (Machine or Installer user) have a requirement set on them to ensure that they are not active while a build is in process.

This requirement is detailed in our product documentation :

It is possible to identify if a policy is being picked up by a machine by reviewing the deployment process log file (ztoolkit.log) on the machine:

[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] ActionSet processing BEGIN 
[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] Current Task: PolicyManager
[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] Current Task Status: Downloading
[06-Mar-12 11:06:12] [ZapphookZcm] [Debug] ActionSet processing END

As you can see there is a policy being processed but there is no indication which policy is being processed.

We have just published a TID that shows how to list the ZENworks policies that are picked up during the deployment process.

For more information check out

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

When you use Zclonewiz to create a clone of a built machine (more information on Zclonewiz here: ) you will need to deploy the clone image to machines.

We have published a TID that talks you through setting up a Clone menu within Zim.

This TID will give you the ability to do the following:

  • Configure a clone master machine as an img multicast master.

  • Create a server image of a clone master machine.

  • Configure a clone target machine as an img multicast client machine .

  • Restore a clone image from the ZENworks imaging server to the target machine.

  • Populate ZISD with the computername and other appropriate attributes.

For more information check out TID 2012003

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

A new dawn

So, I had planned to start the new year with a new blog and post occasional updates on what we're currently working on, what we're hoping to work on and every now and then a comment on the quality of the coffee we're drinking.

We're already into Feburary and this whole blog thing still hasn't happened.... Oops!

There have been some good reasons though and now is probably a good time for me to take some time out to tell you all about some of them.


First of all I suppose I had better introduce myself. My name is Steve Gibbs and I am one of the developers here at ENGL. Some of our longer-term customers may remember me from my helpful support incident updates and news forum postings. (Well, in my mind they were helpful anyway!).

I have since stepped back from that side of things a little and now take some of the feedback we get from those incidents and postings as well as enhancement requests and try to turn that into new product features and enhancements. How that process happens is probably a story for another day though.

The actual "bloggy" bits

Ok, let's get on to the interesting stuff!

I'll break this down into sections as this could end up more like War and Peace than a blog entry as I try and catch up on things. That way if you need to nip off for a cup of tea and a biscuit in the middle of it you'll have more chance of finding your place again.

Hopefully the next entry will be a lot more, umm, concise! I may have to set myself a 140 character maximum...

ZENworks customers

For those with ZENworks, we have been working for over 12 months on the next version of the ENGL Imaging Toolkit, codename "Kamino". We're currently undergoing final approvals testing and beefing up the documentation (more on that in a bit) and aim to release later this month.

Whilst a lot of the work we have been doing is 'behind the scenes' or 'under the covers' or any other metaphor for 'stuff you probably won't actually notice but has an unbelievable effect on the whole package', we've had a lot of feedback on things you'd like to see as well as some ideas of our own and here's a quick list of some of the items we've managed to get into this release that you can look forward to:

  • Improved documentation. I know, seems like an odd place to start, but we've spent a lot of time and energy re-vamping our documentation for this release as it is one area we know our customers and evaluators struggle with. Expect to find a much more logical structure, more information, more pictures and, due to popular demand, we will have documentation available in PDF format
  • Improved driver processing. The driver processing engine has been heavily modified and now correctly analyses even more driver packages. Analysis can also be performed as a standalone task to check what is going to be created before making an entire new driver image. Driver properties are also now updated based on analysis and include an option to 'force' install a driver....
  • Improved driver installation. Drivers that don't or won't install during mini-setup and require installation are now handled natively by the build process. As part of this the build will compare the hardware on the machine with the hardware IDs we matched when discovering the driver. If the hardware ID is not present (for example a machine of the same type which doesn't include a wireless card) then the driver will not be installed unless the 'force' option was set.
  • Support for 3rd party imaging. All new for this release is support for 3rd party imaging using a WinPE version of Zim. This supports 99% of the current Zim functionality and also includes methods to natively restore WIM images (including add-on images). Note that we haven't by any means ditched native ZENworks imaging and for most people this is still the more flexible method of restoring images.
  • Support for Windows 7 Thin PC. Deploy Windows 7 TPC with ENGL Imaging Toolkit, bam! Enough said.
  • Improvements to the Build Console File Library. Several improvements have been made to the file library, not least the ability to relocate all your files simply by changing the path in Options.
  • Project locations not limited to local media. Projects can now be stored on network paths and files will be processed locally to avoid the restrictions with the WIM image format rather than forcing you to store projects on a local disk.
  • ... and more!


SCCM and MDT customers

We have also been busy on our other products too, with beta testing on ENGL Driver Manager 2.1 now well under way. As with Imaging Toolkit a lot of the work is hidden from view but some highlights of this release are:

  • Support for Microsoft System Center Configuration Manager 2012. As well as SCCM 2007 we now support SCCM 2012. Whatever else holds you back from SCCM 2012 it won't be us!
  • Support for Microsoft Deployment Toolkit 2012. As with SCCM, if you want to use MDT 2012 go right ahead. Driver Manager 2.1 has been designed to work with both MDT 2010 and 2012.
  • Improved driver processing. The driver processing engine has been heavily modified and now accuarately analyses even more driver packages.
  • Improved Machine Library. Many changes have been made to the Machine library and it also now includes the ability to move the machine library simply by changing the location in Options.


There's more?

Yes, there's more! Our wireless LAN configuration tool hasn't escaped the development team either and will also be ready to support Microsoft Configuration Manager 2012 when it is released.

Blog done

So, whilst I catch my breath I hope you can see why it's taken a while to get this blog started and, fingers crossed, we'll have the chance to tell you about some more exciting news from the development team soon.
If not, we should at least have 5 minutes to comment on the coffee ;-).