Deployment Solution

 View Only
  • 1.  Updating Drivers on PXE Servers at Multiple Sites on Multiple Deployment Servers

    Posted Oct 26, 2010 05:25 PM

    Is there a way to automate the process of adding nic drivers to PXE Servers on multiple Deployment Servers? We have about 150 Deployment Servers at different sites, all on the same network and I'm looking for a way to update one location and push the exact updated Win PE PXE config out to the other sites. Exact-less the dagent settings. I want to point to the local server.

    I toyed with the idea of copy the boot.wim file to other sites, but when I tested the idea my dagent is pointing to the DS that the boot.wim was created on. I was thinking I would push out my boot.wim with the package server. Can I point my dagent using LMHosts or based on the network the machine is being imaged on?

    Any ideas on how to accomplish this would be appreciated. 

     

    Thanks



  • 2.  RE: Updating Drivers on PXE Servers at Multiple Sites on Multiple Deployment Servers

    Posted Oct 28, 2010 10:36 AM

    The drivers you add all go into a single folder on the DS.  Just replicate the drivers folder, and then make the DS's all rebuild their PXE configs.  Voila.



  • 3.  RE: Updating Drivers on PXE Servers at Multiple Sites on Multiple Deployment Servers

    Posted Nov 01, 2010 11:08 PM

    So, I need to manually recompile using the Boot Disk Creator once the drivers folder is copied? Is that what you mean by "make the DS's all rebuild their PXE configs"? Can this be done via command line or script? What is the path to the drivers folder?

    Thanks Thomas



  • 4.  RE: Updating Drivers on PXE Servers at Multiple Sites on Multiple Deployment Servers

    Posted Nov 02, 2010 09:24 AM

    Pretty much, but each DS can manage all of it's PXE configs from within the PXE Configuration Utility, but yup, that's pretty much what you do.  This is, actually, one advantage of how we do things in NS7/DS7.  Granted, it's one of the few advantages right now ;-) but it's still one reason why we're moving toward DS7 integration with NS.  NS can manage all of those PXE configurations in a single click.

    I no longer have a DS 6.x installation available, but I'm pretty sure the drivers you add go into a subfolder of Boot Disk Creator, and you can find them there - in a Custom folder I believe.  Once you find them, you'll see pretty clearly the organization.  Truthfully, many customers, once they understand this, don't even use Boot Disk Creator to add their drivers.  You capture this folder, and replicate the contents to the other DS's in your environment, and then recompile.

    Sorry for not having more specific details.  I found it once about 2 yrs ago and haven't touched it since, because I now mostly support DS 7.1.  :D