[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 330
  • Last Modified:

MDT 2013 - Image Capture fails to upload image

I am attempting to capture and upload an image. The drivers for the hardware imported into MDT. Downloading images works fine.

I run the litetouch script from within the OS but when the system reboots to create the WIM and upload to the server the NIC drivers are not found. Why?

I should also add that this was working. I am unaware of any changes made other than driver imports for new models.

Thanks!
0
MarkMelanson
Asked:
MarkMelanson
  • 8
  • 4
1 Solution
 
Cliff GaliherCommented:
The upload happens using the windows PE environment which is a different image and therefore will require direct injection of the NIC drivers in there as well. Of course I *strongly* recommend using a VM to build reference images. The whole process can be automated, no extra hardware is detected making the reference image more stable and smaller in size, and no driver injection is required for the capture process... ever.

If you read any worthwhile walkthrough of MDT or talk to anybody who is considered an expert in the field, you'll quickly see that using a VM is considered a standard practice these days.
0
 
MarkMelansonAuthor Commented:
I am using a VM (vSphere 5.5) as well as physical PCs. They act the same.
The drivers are imported into MDT.
The ISO created by MDT works fine.
I am using the standard Sysprep and Capture task sequence.

Is there some other step required that I am missing to get the drivers into the WIM that is installed to the hard drive? I was under the impression that it uses the same WIM as WinPE.
0
 
MarkMelansonAuthor Commented:
The MDT server is Windows Server 2012 with Data Dedupe enabled on the data drive only. We have been running dedupe for several months but I thought I'd throw that out there.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Cliff GaliherCommented:
No, it does not use the same WIM. Are you booting the capture process from a VM? It doesn't sound like it...
0
 
MarkMelansonAuthor Commented:
Yes.

Boot Windows.
Run cscript \\MDTserver\depshare\scripts\litetouch.wsf
0
 
MarkMelansonAuthor Commented:
OK. So I took a look around and found \Capture WIM\Boot.wim

Is it required that I inject the NIC drivers into that? That would make some sense anyway.
0
 
Cliff GaliherCommented:
For a VM it usually isn't necessary. The PE image usually has all necessary basic NIC drivers which work with both ESX and hyper-V VMs. But for physical machines, yes, that is where you need to inject NIC drivers.
0
 
MarkMelansonAuthor Commented:
We are using VMXNET3 not e1000 so that makes sense. Odd that it worked before if the drivers have to be injected by hand.

I did not see any mention of this in the documentation for MDT. Still looking though...
0
 
Cliff GaliherCommented:
For reference images, it o's best to use basic drivers (e1007) and to avoid installing VM enhancements such as VMWare Tools or Hyper-V integration servers. Use legacy hardware emulation where possible. Again, this is only a reference image and it will be sysprepped which means hardware detection will be done again for each machine during the deployment phase using the reference image.

Additionally, VMWare does not officially support Tools in PE and doing so is a but of a pain.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011710

There are benefits to using VMXNet on a VM running production workloads, but there is no reason to do so for a reference image.
0
 
MarkMelansonAuthor Commented:
I build the reference image on vSphere and have never had a problem uploading the image utilizing VMXNET3 and the Standard Client Task Sequence.

I think what I need is a definitive answer to the following question. When the WIM is copied to the hard drive and then set to boot from it where do the drivers come from?
0
 
MarkMelansonAuthor Commented:
Yes! It is now working again. Here is what I have observed.

The missing NIC drivers were listed in the MDT GUI but I do not think the files were actually existing in the file system. I say this because after closing a re-opening the GUI several times over the course of this nightmare they finally disappeared from the GUI (WTH?). I re-added them and now all is well.

Coincidentally to that I had opened the drivers.xml in notepad but made no changes.

That is NOT cool.
0
 
MarkMelansonAuthor Commented:
Accepting my own answer such as it is.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 8
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now