sccm 2012 injecting drivers into offline sccm captured wim file

Hi

I need to create an offline .wim file so that the images I create via sccm can be sent out via usb stick direct to our
pc suppliers who can ship the machines prebuilt to site.

I know how to capture an image, and upload to the server, and then redeploy out - pxe is working ok.

However for simplicity i want a solution whereby the image/.wim file is on a usb stick, and has directory of "drivers" on the same usb stick where the "base/golden" image is when installing onto new machine "out of the box" with our "corporate build" at the pc suppliers.

Once this is fixed, i would then only have to copy up new "drivers" to same usb stick/s with the "base/golden" image and the image would reference this directory and install the relevant drivers - i think via a wmi query?

I don't know how to do this but know that it is possible, but not done it before in win7 or xp.


The only thing that we will then need to be done once the p.c is delivered to site is for it to be added to the domain - we don't require this task to be added into this .wim file as it won't work as the pc suppliers won't have a network connection to our network to add the machine to the domain

Thanks for any replies in advance.
Michael MurphyAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Michael MurphyConnect With a Mentor Author Commented:
Hi

I have got this now complete and apologies for not replying sooner.

I have apps fully configured and deployed, windows config settings configured, and drivers injected and working - this is for 2 machines - 1 desktop and 1 laptop.

This is working 100% on a usb stick via SCCM - create task sequence media - this has been done not via MDT.

I am now moving on to MDT to inject the windows updates into the .wim file.

The only issue I have now is speed of install it was 30 mins and now 90 mins, so i will be opening a new ticket. thanks everyone.
0
 
David Johnson, CD, MVPOwnerCommented:
Use MDT instead (you should have installed MDT and integrated it with SCCM as it adds about 200 more deployment options).. Within MDT create a MEDIA folder and copy off the contents of the 'content' folder to the usb stick.
0
 
Michael MurphyAuthor Commented:
Thanks David , are there any walk through.guides for this solution anywhere? I am a sccm rookie any links woukd be appreciatedWill feed back asap. Many thanks
0
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.

 
Adam LeinssCommented:
#1 resource for SCCM/MDT OSD: http://deploymentresearch.com/

BTW, I have both SCCM 2012R2 and MDT 2013 in my environment and I just use MDT 2013 straight up.  OSD in SCCM 2012R2 is very fincky...MDT 2013 just works great by itself.
0
 
Adam LeinssCommented:
I paid for these out of my own pocket from Amazon, but they are highly rated:

Deployment Fundamentals, Vol. 5: Building a Real-World Infrastructure with Windows Server 2012 R2, Mdt 2013, and Powershell:

http://www.amazon.com/gp/product/9187445093/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

System Center 2012 R2 Configuration Manager: Mastering the Fundamentals, 3rd Edition:

http://www.amazon.com/gp/product/9187445085/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

Johan Arwidmark is an absolute beast when it comes to OS deployment and I've chatted with him several times on the forums.
0
 
Michael MurphyAuthor Commented:
hi thanks for all replies.

I have installed MDT2013 onto SCCM2012 server, not had a chance to use it today.

My colleague side tracked me into using another method which seems to have worked, but may not be
the best method.

I will try and explain the best I can as it's been a LOOOOOOOOONNNNNNG day !

Create reference pc manually "base/golden image" - captured this via capture media.

We loaded and injected the drivers into the boot image x64, and then have created separate tasks for Add Drivers
as separate tasks which are scheduled after installing the base image.

I need to prove this works again tomorrow as ran out of time.- will update you.

Thoughts?
0
 
David Johnson, CD, MVPOwnerCommented:
SCCM takes forever to test in comparison with MDT so if you are a consultant carry on with SCCM if you just need to get it done use MDT

Don't forget to integrate MDT into SCCM or you will not see the benefits.  SCCM will not export to a USB stick or an .iso but MDT will.
0
 
Michael MurphyAuthor Commented:
Hi David

SCCM is real pain in the.... moving on I will give MDT a go I am definately not a consultant and a complete rookie with SCCM.

I maybe misunderstanding your point re USB, and I am not an expert, but I have deployed the captured image via usb stick - I have proven this today - unless  i am mistaken.

Also you can do this by using ImageX aswell - this isn't SCCM but it can utilise the .wim file and install.

The next avenue I am looking at is IIS as this maybe the issue after googling around - but i am not an expert - i used a walkthrough plus assistance to do this install.

http://iboyd.net/index.php/2009/01/09/troubleshooting-sccm-and-bits-downloads/

http://myitforum.com/myitforumwp/2011/11/09/sccm-waiting-forever-for-content/
0
 
Adam LeinssCommented:
When I watch MDT, its injecting the drivers via DISM before the image is applied via ImageX.  You probably could add all the drivers in one go to the "golden image" with DISM, but I don't know if that's a good idea.  You generally just inject the drivers needed via WMI and not add them all in one go as Windows may pick the wrong driver if multiple versions of the driver exist.
0
 
Michael MurphyAuthor Commented:
Hi

Please ignore last paragraph re iis and URLs will.remove asap but cant remove as on mobile. Will feedback more asap thanks everyone
0
 
Mike TLeading EngineerCommented:
Hi Michael,

You really need to concentrate on MDT to build a reference image. That is OS + patches + Visual C++ in flavours. Do this on virtual hardware NOT physical. You can use vmware or hyper-v - it doesn't matter. What matters is not capturing hardware you don't want.

Once that is done, concentrate on building a driver library for each model you have. Organise it by model and by feature. Then import the model and all sub-folders into SCCM.

Once you have that you import the reference WIM and create a task sequence and add in drivers using WMI filters.

Once you have that sorted you can create a media based deployment or a deployment for distribution.

The MDT only option is to create a Production share (to keep them separated) and import the drivers into MDT instead, and then use the  "LiteTouch OEM” Task Sequence.

Note, MDT is not as good at dealing with drivers as SCCM so personally I would persevere with SCCM for the final stage.

If you want extra help, the best advice I can give is for you to buy the Deployment Fundamentals book by Johan and Mike - there are now 5, so pick the best one that suits you.

Mike
0
 
David Johnson, CD, MVPOwnerCommented:
How many images do you want to support? Unless you are in a large corporation that bulk buys hardware and only use a few models you will end up with having to support 10's if not hundreds of different hardware models and mfr's  .. Been there done that with ghost ... Never Again.. MDT and 1 reference image, per o/s and leverage mdt to get the correct drivers installed and not by using Plug and Pray to select the correct driver from a hundred of drivers but to query the hardware and install only the correct drivers, Dell and HP make it easy, Lenovo not quite as easy.but  doable...  The only time I use thick images is for AutoCAD since it takes forever to install and setup.
0
 
Michael MurphyAuthor Commented:
Solved own problem.
0
All Courses

From novice to tech pro — start learning today.