The DeployAnywhere feature lets you re-target an image to suit a computer that has different hardware from the model of computer from which the image was created. This allows you deploy a generic image to a range of different computers and perform a re-targeting of the computers, rather than requiring a separate image for each hardware set.
DeployAnywhere DOES Support deploying an image between different Hardware Abstraction Layers (HAL). The DeployAnywhere feature will sort out which HAL a computer requires and will load it. It will then find and install the correct mass storage driver(s) and the NIC driver. DeployAnywhere version 2.5 does not support the installation of other drivers such as graphics cards, sound cards, etc.
Note: DeployAnywhere will not cross processor levels, such as replacing the HAL from a single (Uni) processor to a Multi processor machine. The solution is to go from a Multi processor machine to another Multi processor machine.
DeployAnywhere looks for the required drivers from the deployed operating system (OS) and from the driver database. The driver Library is installed on the console computer at C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\template\common\windrivers folder. Additional drivers can be added.
DeployAnywhere supports both the Sysprep and the Non-Sysprep images. If a driver is not defined in the Sysprep image, DeployAnywhere will add and install it. However, DeployAnywhere only installs storage and NIC drivers.
DeployAnywhere will use a step that results in a "Sysprep mini-setup" process at the destination computer before it starts up into Windows. If there are third-party drivers that are required they are injected and the Sysprep process installs them.
There are some limitations on using DeployAnywhere. If you deploy an image to multiple computers, DeployAnywhere does not generate a unique computer name for each computer. The user will need to include a configuration step in a Console Task to ensure that a unique computer name is applied. A Configuration Task should also be used to join either a Domain or a Workstation. To create a Configuration Task, see the below document: