Ghost Solution Suite

Ghost Solution Suite 2.5 using PXE boot deployment via network


I have an existing and functional Windows 7 Ghost image that is currently deployed on several models of Desktop using the Ghost Console server. We have just purchased 10 new laptops, and have 80 new desktops arriving within a few weeks.

I can successfully deploy a Windows 7 image to the laptops but because my Win7 image is missing the new laptop drivers (NIC, Sound, Display etc) I am unable to finish the configuration task to join the domain due to lack of network connectivity.

I have read that the microsoft deployment methods allow for pkmgr.exe to install patches and drivers to an offline .wim image when in the WinPE environment.

Is it possible to do something similar using ghost? So that on the laptop, in the WinPE environment - Ghost can inject the missing laptop drivers into the Windows 7 OS as it is being installed? This would allow continued connectivity to the ghost console after booting into Windows 7 and a successful configuration task to name the laptop and join it to the domain.

Hi,
You need to run Deploy anywhere for achiving hardware independent imaging.
Please see https://www-secure.symantec.com/connect/articles/how-use-deploy-anywhere-after-restoring-ghost-image-0

Thanks

DeployAnywhere fails when run as a Task from Ghost console - Seems to run in Evaluation mode is that normal?
It states that two drivers are missing - the physical nic drivers and the intel wireless-N drivers.
Both of these have already been added to the DeployAnywhere driver database as well as the WinPE image we use.

I'd open drivers.manifest.txt in Winpe folder and visually inspect entries for this driver. make sure that it contains entries that match manufacture (I am sure it will) but also importantly device id 4238. Subsystem matters little.

Have checked drivers.manifest.txt - DeviceIDs aren't included in this file at all, on any of the hundreds of drivers.
But there are entries for my 'missing' drivers.




Also checked pci.manifest.txt - this does have device ID listings and the two 'missing' drivers are most certainly listed there in full - including the Vendor, device and Subsystem IDs.