That's a strange place to pull drivers from. I would suggest this location is not accessible to your deployment server.



My understanding is that DeployAnywhere looks for drivers in the DriversDb folder on your deployment server share. You need to make sure the required driver is in there. There is a GUI to manage this, on the Tools menu in DS.



In the days before DeployAnywhere, the 'old way' of doing it was that you had to tell Sysprep where the drivers were, in the sysprep advanced settings when creating an image. This would then copy the driver store in to the actual image to be deployed. Or you could run a script after imaging, to copy the correct drivers from your driver archive.



~Mike~

Thanks MP.



What I ended up doing was just copying the files to that location on the image I created.



It almost seems like the drivers itself were looking for the file(s) there, vs deployanywhere being the culprit.



Whats weird though is that the driversDB already had those drivers in there, so I am not sure if deployanywhere was using the base driver for the PRO 100 VE from altiris, or the additional one I added to the ddb.





Only major Issue I have now with my master image is the weird way that some older hardware gets their default netbios name set to "New Computer" causing sysprep to halt when naming the PC since spaces aren't allowed.