Question about Deploy Anywhere
Deploy anywhere
This seems like an interseting method to use/send one image to different hardware. It is rather confusing though, it only supports NIC and ACHI, so why would anybody use this at all to send out an image to multiple PCs, I mean, end of the day the other drivers i.e. graphic card… pci drivers still needs to be installed on target PC. Anyway, could you clearify if I understand this correctly. I want to send out an image to two or more PCs (different hardware). lets just say I added the NIC and ACHI drivers within driver database, And once the target host is ghosted than install all the other drivers (is there I way to automate this process, I mean install all the others drivers through the share by running some sort of script??.
Another thing, lets say I use to GBW to create a bootable CD containing deploy anywhere driver database, do I have to boot through this cd all the time to see whether or not a host PC is missing particular set of drivers, can this be done through the share as well and PXE booting pc and checking it through that.
Anyway my main concern with using deployanywhere is the other drivers (grahic, pci, chipset etc). could you please shed some light on this so I can decide if it will be benefitical or not.
Mach appricated.
-mEtho
Comments
DeployAnywhere via PXE
This article may help:
How to run DeployAnywhere when a boot package is delivered via PXE
Thank you,
Randy
Hi Randall, thanks for
Hi Randall,
thanks for the quick reply, any thoughts on rest of my question, any sort of help would be much appriciated.
thanks again mate
-mEtho
DeployAnywhere vs. Sysprep
Hi there!
I'm sorry I glossed over the other items before. In all honesty, I feel DeployAnywhere works best as a disaster recovery tool than as a tool for mass deployment over different hardware. The reason I say this is because if I were to be responsible for a mass deployment, I would be using Microsoft Sysprep with a customized answer file and the appropriate drivers on the source machine, as descfribed in this article:
How to Add OEM Plug and Play Drivers to Windows XP
http://support.microsoft.com/kb/314479
The reason for this is that Sysprep is an image creation step, in that you set up the machine beforehand, create the image, and then deploy the image and be done. With DeployAnywhere, you forego the preparation and increase deployment time. It is an excellent tool for when you need to apply an image to a dissimilar machine, such as in a case where the old machine is lost or destroyed. But yes, it only applies NIC and storage drivers.
Thank you,
Randy
To automate driver installation
I have a script running in WinPE after imaging to, based on the computer model, copy a folder of drivers from the server to the computer, and set the DevicePath registry key to the drivers folder.
My script looks like this:
I got all of my information from this forum post though:
https://www-secure.symantec.com/connect/articles/hardware-independent-imaging-another-angle
And the pnppath script from:
http://technet.microsoft.com/en-us/magazine/2006.0...
Would you like to reply?
Login or Register to post your comment.