Ghost Solution Suite

Hi,

I have W2K8 x64 installed on a UEFI machine.

When I start this system with WinPE, gdisk32 shows three partitions on the disk :
- the EFI partition (200 MB)
- the MicroSoft Reserved partition (MSR : 128 MB, this partition has no "type" mentionned)
- the Windows partition (30 GB)

I have captured an image of this system using GSS 2.5.
Then I cloned this image on a similar machine.

When I start the cloned machine with WinPE, gdisk32 now shows only two partitions on the disk :
the MSR partition is missing
(which is confirmed when I open the image with Ghost Explorer : it contains only 2 partitions,
one "unknown" which is the EFI partition and one "NTFS" which is the Windows partition).

Probably a consequence of the MSR partition lack, the cloned system is unable to start.

Is there something I can do to have the three partitions captured by GSS ?

Thanks,
Jean-Pierre

GSS does not officially support cloning EFI systems. Probably it is not captured because partition type is unknown. You can try capturing this partition raw but even then GSS 2.5 can only restore EFI partitions as an MBR disk. You probably want disk to be restored as GPT right?

Hi Eugene,

MSR partition type looks to to be unknown : no type is displayed by gdisk32 for this partition when I execute the program in WinPE.

The system is installed on a GPT disk.
I did not try to capture the MSR partition only but the full disk in raw mode.
It solved the problem : after cloning, the target system starts the cloned W2K8 system.

There is a little poblem remaining : after the Clone step, I defined a Configure step in the task
to change the machine name and network settings (using a Custom Configuration)
but the step could not succeed (didn't find the Windows partition to update).

So, I replaced the Configure step with a "Software and File actions" step in which I launched
Ghconfig32 to manage the name and network settings changes.
It worked well for the machine name modification but not for the network settings :
the machine has a dual-port NIC and the new IP address was applied to the "wrong" port
(the one which has no cable connected).
I didn't find a way to fix this problem.
I had the same trouble (wrong NIC port used for network settings) with a Configure step
in a task executed against a W2K8 64-bit system installed on a non-UEFI machine (MBR disk and no EFI partition installed).

Thanks.
Jean-Pierre