Jump to content

MDT2010 needs SCCM package for additional drivers

Recommended Posts


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
Link to comment
Share on other sites

  • 4 weeks later...

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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Create New...