What version of Ghost are you having trouble with?
The version of Ghost in GSS2 automatically tries to edit the new Boot Configuration Database in Vista if it detects Vista in the image you are cloning. I'm not aware of anyone who has reported a problem like yours with GSS2.
It sounds more like you are using an older version of Ghost, which doesn't know about the changes to the boot process introduced in Vista. Vista records the "disk signature" of the volume it is set to boot from in a new database that replaces the old
boot.ini file, and it is probably complaining that it can't find the original disk it used to boot from.
There is a procedure for making Vista not try to boot the volume identified by the disk signature saved in the BCD database, but to boot from the currently bootable partition in the disk's MBR. It was first described
by Alan Adams at the MSDN forums - essentially, running these commands on a Vista system:
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
can make it disk-signature-neutral and so you may be able to deploy using an older version of Ghost.
I've not personally used this procedure, but others seem to have had success with it. You can also try the "
-fdsp" switch in Ghost, but if it works for you the above procedure is more widely applicable.