Home / server / Questions

Questions[mdt-2010](server)

Martin Hope
Tim Brigham
Asked: 2012-10-18 07:36:25 +0800 CST
  • 2

How do I handle driver problems associated with creating a new WIM file using a previously created image as a base?

I am using a custom MDT image which installs Windows 7, Office 2010, etc which was created from a previously deployed base image of Windows 7 + SP 1 + updates.

When the driver injection is enabled I receive a group of messages (collected from different logs, screens, etc). If I turn the preinstall driver injection off things work as expected. If I leave it on I receive the following messages.

  • windows cannot install required files
  • 0x80004005 8004004
  • non zero return code ltiapply rc=31
  • Unhandled error returned by LTIApply: a device attached to the system is not functioning. (-2147024865 0x8007001F)
mdt-2010
Martin Hope
Don
Asked: 2011-12-20 14:25:46 +0800 CST
  • 4

About a year ago we implemented WDS and MDT. Using this we have been successfully deploying Windows 7 x86 and x64 on every PC and laptop we have. We put the OS on, then add on Office, Adobe, Antivirus, etc. Also, I have it set to do Windows Updates from our WSUS server. The question I have is, is there anyway to speed the process up or slipstream in some of the updates? It seems that it takes about as long to do the Post Installation Windows Updates as it does the OS and all of the application installs combined. The only thing I can think of is to make a new OS capture with Windows 7 w/SP1 so it doesn't have to install SP1 via the update task. Is there any other way that I might speed this process up? Any suggestions would be greatly appreciated, thanks.

wds mdt-2010
Martin Hope
Cylindric
Asked: 2011-12-14 08:19:57 +0800 CST
  • 5

I am not sure if I am confused as to the purpose of MDT.

We need to deploy a standard Windows 7 build to about 100 new computers, and more as time goes on.

Having followed a whole bunch of documentation, tutorials and white-papers etc, it seems that MDT will always go through the full processes of

  • installing windows
  • installing applications

Whereas what we need is a simple "take image of reference machine" followed by "clone image onto target". This should be much faster than the full installation routines followed by MDT.

Should I be doing something else with the captured WIM from MDT? Can I simply put it into WDS somehow as a "ready to copy" image?

deployment wds mdt-2010
Martin Hope
Mitch
Asked: 2011-03-12 10:03:49 +0800 CST
  • 3

I have the custom image captured. Import the image and files. Prepare the customsettings.ini and the boot.ini to minimize the questions the deployment team will need to answer. Everything works like a charm on virtual machines but when I map to the scripts folder on the deployment share and double-click litetouch.vbs it creates the c:\minint folder, subfolders, and a couple of log files then nothing. Here's what the log files look like:

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property CleanStart is now = ]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Microsoft Deployment Toolkit version: 5.1.1642.01]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property Debug is now = FALSE]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[GetAllFixedDrives(False)]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Anyone encounter this before or know what might be happening/not happening and can direct me in the right way? I've only found a couple of other references to this anywhere and they had no solution/cause listed either. I'm stumped.

mdt-2010