MSFN Forum: Which is first. Driver integration - MSFN Forum

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Which is first. Driver integration Delete Default or integrate

#1 User is offline   Worf 

  • Worf
  • PipPip
  • Group: Members
  • Posts: 187
  • Joined: 26-October 04

Posted 27 April 2012 - 01:59 AM

Hi.

Which is the best way to do this, should i delete windows default drivers first then intergrate my own or is it the other way round?

Regards

Worf.


#2 User is offline   Tripredacus 

  • K-Mart-ian Legend
  • Group: Super Moderator
  • Posts: 8,682
  • Joined: 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Posted 27 April 2012 - 09:07 AM

Why would you want to delete the default drivers? Are you using a special tool or something? :unsure:
DISM can't even see the built-in drivers.

#3 User is offline   maxXPsoft 

  • MSFN Master
  • Group: Developers
  • Posts: 2,748
  • Joined: 14-November 03
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 28 April 2012 - 05:26 AM

/Get-Drivers /all will give you a real good list
But I agree, best to leave them alone

#4 User is offline   winoutreach5 

  • Newbie
  • Group: Members
  • Posts: 27
  • Joined: 02-April 12
  • OS:none specified
  • Country: Country Flag

Posted 08 May 2012 - 02:18 PM

View PostWorf, on 27 April 2012 - 01:59 AM, said:

Hi.

Which is the best way to do this, should i delete windows default drivers first then intergrate my own or is it the other way round?

Regards

Worf.


Worf,

I’m trying to understand specifically what it is that you are asking. If you are going through the standard process of using Sysprep to prepare an installation of Windows for duplication, by default the Plug and Play drivers are removed.

If you are asking how to prepare an image with injected drivers for use with deployment you might want to consider the Microsoft Deployment Toolkit (MDT). MDT combines all of the official tools above into a single workbench interface that can help automate the entirety of the process. Additionally, it is compatible with Windows XP, Windows Vista, Windows 7, and Windows Server 2003, 2008, and 2008 R2, which means learning one utility to do all of your deployments. Furthermore, it is exceptionally useful in creating “universal” images as it can easily add or remove both drivers and applications from the deployment images. MDT is free and can also be used in conjunction with Windows Deployment Services (WDS).

You might also benefit from the TechNet library article Automated Installation to Upgrade to Windows 7: Step-by-Step Guide for getting started with MDT as well as how to use it to automate a Windows 7 installation. Also, there is also a helpful video on the Microsoft TechNet blog here that walks you through the process of setting up Windows Deployment Services, installing Windows AIK and installing and then using MDT.

The video demonstrates the process of creating a deployment share, injecting drivers, setting up a task sequence and then updating the deployment share for use with your deployments. From there, you could refer to the Step-by-Step Guide for assistance with creating boot media.

Jessica
Windows Outreach Team – IT Pro

P.S TechNet is having a webcast – Everything You Wanted to Know and Ask about Windows Deployment On May 15th and 17th. Registration for the 15th is here, and registration for the 17th is here.

This post has been edited by winoutreach5: 08 May 2012 - 02:27 PM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy