I have been having the same issues with Vista images. The only solution I have found so far is a repair of Vista after the image has been pushed down. This is definitly not the way I would want to do any kind of mass deployment, but we are not moving to vista yet (an no future plans to) so it is just me testing it with the DS.

Here are some things to try when you hit this problem.

• When restoring the image, use the –RESTORESIG in RapiDeploy. (The solution can only be used when performing one to one imaging).
• After the restore process is completed but before the computer reboots back to Windows Vista, run a WinPE script to call BCDEDIT.exe. These are the commands to run:
  
  bcdedit /store c:\boot\BCD /set {default} device PARTITION=d: (or C: or boot if it is a single partition installation)
  bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=d: (or C: or boot if it is a single partition installation)
  bcdedit /store c:\boot\BCD /set {legacy} device boot

• Use Sysprep before creating the image.
• Add a Run Script task just before the capture image task - add the following to call BCDEdit this will properly prepare the drive for capturing
  
  REM Execute BCDEdit and prepare for imaging.
  REM Find the system root and append system32 and BCDedit
  %SYSTEMROOT%/system32/Bcdedit.exe -set {bootmgr} device BOOT
  %SYSTEMROOT%/system32/Bcdedit.exe -set {default} device BOOT
  %SYSTEMROOT%/system32/Bcdedit.exe -set {default} osdevice BOOT
  

i have noticed this doesnt happen when you do 1 of 2 things.

1. image in linux automation
2. replace dagent with aclient in automation. You can do that by replacing the runagent.bat from the \\server\express\bootwiz\platforms\winpe\x86\templates\runagent.bat and copy that file and paste it to

\\server\express\bootwiz\platforms\winpe2\x86\templates diretory.

You will have to regenerate the winpe images after you do that.

I did image in Linux, the problem was still there. The AClient is not supported in Vista either, so I dont see how that would help at all.

It does not matter what preboot is used to capture the image. The client needs to prepare for imaging before it reboots into automation. Prepare for imaging means DAgent to execute the bcdedit so it could remove the uniqueness from the client (Volume, Disk, Partition) and then reboot into automation for the image capture.

This could also be done without an agent doing the "Prepare for imaging" execute the commands that green eyes produced reboot the machine and make sure that a preboot is the first boot so an image could be captured.

nelo