Windows Server TechCenter > Windows Server Forums > Setup Deployment > Install XP via PXE from WDS -- No network driver after install completes
Ask a questionAsk a question
 

AnswerInstall XP via PXE from WDS -- No network driver after install completes

  • Monday, November 02, 2009 7:51 PMGai-jin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm not sure if this is the best forum to post in, but since this involves something I'm doing wrong in WDS, I figure it's worth a shot.

    I've used the deployment toolkit to create a boot image and task sequence that installs windows xp and several applications.  It is also supposed to inject network drivers.  The Client PC boots from the WDS server fine, and windows setup runs smoothly all the way through.  After windows setup, when the cilent boots to a desktop and tries to run the remaining scripts, it can't find the network share because the NIC driver isn't installed.  

    I have all of the drivers added in deployment toolkit, and it seems to be injecting them when it creates the boot image, but Is there something I need to do to get them injected into the actual OS setup so that it will have network access after install?

Answers

  • Tuesday, November 03, 2009 6:24 AMTim Quan - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    By default, all the drivers are deployed to the target computer. Then, Windows PE and the target operating system use Plug-and-Play IDs to identify the device drivers needed for the devices on the target computers.

     

    Please make sure that you have added the latest driver for your NIC card. Please only add one driver for your NIC card. For example, only add the driver for Windows XP or Windows Vista to the deployment share instead of adding both.

     

    Please also make sure that Your NIC card has already been installed on your clients.

     

    If the issue persists, you may try the DRIVERPATHS method to install the driver or install the driver as an application (obtain a .exe driver file).

     

    Hope it helps.

     

    Tim Quan - MSFT

     

     

    • Marked As Answer byGai-jin Thursday, November 05, 2009 3:28 PM
    •  
  • Thursday, November 05, 2009 3:28 PMGai-jin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Let's chalk this one up to "I'm an idiot."

    I was pointing it to a slightly different version of the driver.  The correct one for this pc works just fine. :)
    • Marked As Answer byGai-jin Thursday, November 05, 2009 3:28 PM
    •  

All Replies

  • Tuesday, November 03, 2009 6:24 AMTim Quan - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    By default, all the drivers are deployed to the target computer. Then, Windows PE and the target operating system use Plug-and-Play IDs to identify the device drivers needed for the devices on the target computers.

     

    Please make sure that you have added the latest driver for your NIC card. Please only add one driver for your NIC card. For example, only add the driver for Windows XP or Windows Vista to the deployment share instead of adding both.

     

    Please also make sure that Your NIC card has already been installed on your clients.

     

    If the issue persists, you may try the DRIVERPATHS method to install the driver or install the driver as an application (obtain a .exe driver file).

     

    Hope it helps.

     

    Tim Quan - MSFT

     

     

    • Marked As Answer byGai-jin Thursday, November 05, 2009 3:28 PM
    •  
  • Tuesday, November 03, 2009 7:05 PMbjohnrini Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    As far as I know, you would have to inject the drivers into the OS install also. If you look in the task sequence, you can see "inject drivers" tasks.

  • Thursday, November 05, 2009 3:28 PMGai-jin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Let's chalk this one up to "I'm an idiot."

    I was pointing it to a slightly different version of the driver.  The correct one for this pc works just fine. :)
    • Marked As Answer byGai-jin Thursday, November 05, 2009 3:28 PM
    •