Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


MDT2010 needs SCCM package for additional drivers

- - - - -

  • Please log in to reply
1 reply to this topic




  • Member
  • PipPip
  • 115 posts
  • Joined 16-November 04

Not sure if this is the correct forum but I have to add some new driver sets to an existing XP image and if I do the ISO will be to large for burning onto a DVD - even dual layer DVD. USB is out of the question due to the need for extra securtiy they are not allowed in the environment.

My thoughts are that we use SCCM to deliver the image now via a package and I was thinking of creating an SCCM package, not an OSD driver package, with the addtional drivers that could be accessed in the final steps of the build process by our onsite setup people.

Just wondering if anyone has done this sort of thing and your thoughts on how best to design and build this? I was thinking maybe a folder stucture with an HTA to get called???

If this is the wrong forum sorry.

As always thanks for the help...

Edited by randalldale, 18 July 2012 - 10:14 AM.

How to remove advertisement from MSFN




  • Member
  • 39 posts
  • Joined 15-April 04
I would suggest upgrading to MDT2012 and re-evaluate your deployment. Use a sysprepped image (include all Core NB/SB HDC drivers) uploaded with ImageX into a WIM file. Build a WinPE 3.1 image and include your XP.WIM as an added file in the resulting WinPE 3.1, burned to a DVD. this link covers most of what you need: brianleejackson.com/tag/sysprep

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users