Understanding the DeployAnywhere feature
Updated: 16 Jun 2010 | 4 comments
This issue has been solved. See solution.
Hi,
As I understands it, the DeployAnywhere feature let you create a single, template, image file that can be used on computers other than the computer model from which the image was created. What i'm not fully understand, is why the DeployAnywhere data-base only includes network and storage drivers when the target computer models has also other drives (video, audio, chipset) that are different than the ones on the source image file.
Can somone please explain it to me?
Maybe I don't get it...
Thanks
Discussion Filed Under:
Comments
It also fixes the HAL. DA is
It also fixes the HAL. DA is just enough to make sure your clients will boot sucessfully w/ network access. There are plenty of other utils out there to take care of the rest.
....I agree it's kind-of lame not to take care of everything in DA, but that would be a massive driver library for Symantec to maintain. I thought I read on the forums a while back that this was going to be added in the future, but I can't really remember. Someone please correct me on this.
You may be interested in a utility called UIU or even www.driverpacks.net
cheers,
I understand... Thank
I understand... Thank you.
hum... If it fixes the HAL it means that I don't have to use "mysysprep" and I can run the sysprep as a part of the create image task?
That's would be a lot easy to maintain that way
Explorer
Yes. This is done as part of image creation, and this eliminates any worries about the HAL during deployment. It does require downloading the drivers onto the source machine. If you later need to add new drivers, you can use the Ghost Explorer to save the file folders into the image, then edit the sysprep.inf to add those listings.
Thank you,
Randy
If you later need to add new
Great peace of info rght there. Very helpful.
Thanks
Would you like to reply?
Login or Register to post your comment.