Deployment Solution

I have been having problems restoring my captured .gho images on my windows 7 machine. Ideally I would like to use Altiris to do this, however it won't even work when I use Ghost 11.5.1. I have tried chkdisk as well as wiping the disk using gdisk64. Any suggestions would be helpful.

Is this issue in DS 6.9 or DS 7.1?

What problem are you facing , can you elaborate.

I am using DS 6.9. When I try using DS to capture and restore the image it fails saying it can't be used for x64. So I assume it is just accessing the wrong application. I also have tried booting the computer into automation and using the command prompt there. I access ghost64.exe and try to capture and restore it. It can capture the image just fine but when I try to restore it I get the 36000 error. I have tried using the command line to do it and it gives me the same error. I have looked through other posts and tried different methods and none have worked thus far.

Sounds to me like you are having problems distinguishing somewhere two of the WinPE architectures Deployment Server supports - x86 and x64.

When capturing and deploying images of a 64-bit OS, you don't need to use a 64-bit WinPE. At the imaging level, you are just dealing with the capture/deployment of an NTFS filesystem.

It sounds to me like you are booting into the 32-bit flavour of WinPE, and then trying to execute a 64-bit application. This is not going to work. 

Try using Ghost32.exe

Kind Regards,
Ian./

Thank you for that suggestion. Unfortunately when I try to run ghost32.exe "the system cannot execute the specified program", where as ghost64.exe works just fine.

Hi -sorry too many assumptions on my part ;-)

Some questions then,

1. When you say that the console reports is can't be used for x64, what exactly does it say?
2. When ghost fails there is normally a GHOSTERR.TXT file. Can you post it's contents?
3. What version of Ghost are you using
4. You say capture is fine, but restore fails. Are you restoring to different hardware?
5. Are you capturing and restoring entire disk images, or are you targeting partitions? Your specific command lines might be useful here.

Here are the answers to your questions.

1. The consoles states "Error: Unable to locate Imaging tool for Windows x64 environment."

2.  I have attached the GHOSTERR.TXT file.

3. I am using Ghost 11.5.1

4. I am trying to capture and restore on the same computer. The hardware is the same. After it fails I re-image it using Altiris and .img file, before I try again.

5. I believe I am capturing and restoring the entire disk image. While in Altiris Window PE2 x64, I am using the command:

ghost64.exe -clone,mode=restore,src=/Images/Windows/testGhost4.gho,dst=1 -sure
 

Am I using the wrong command?

Thanks for you help.

Attachment(s)

GHOSTERR_12.TXT   36 KB 1 version

The fact that you got the same error when executing ghost manually means that the issue isn't the command-line.

It might be that rdeploy can handle something that ghost can't. OEM partitions perhaps? Have you tried wiping the drive with gdisk to ensure it's clean before starting?

I have tried using gdisk to wipe the drive. It hasn't worked either. I get partitioned blocked. Is there another method I can try to wipe the drive?

I used gdisk64.exe 1 -diskwipe. Was that correct?

I think this should work,

 gdisk64.exe 1 /diskwipe 

Out of interest, what is the output of just running,

 gdisk64.exe 

You can pipe this directly to a file with,

 gdisk64.exe > F:\GDISK_OUTPUT.TXT 

so you don't have to copy everything by hand...

Have you seen this doc yet?

http://service1.symantec.com/SUPPORT/ghost.nsf/f622fe1b00b168bc882570dc007a01d2/06df7b028e074efa08256831007a9b1f?OpenDocument

Here is my gdisk64 output:

Disk  Partitions  Cylinders  Heads  Sectors  Mbytes     Model
  1        1               19457     255      63         152627.8  Hitachi HTS543216L9SA02

I have tried most of the methods for the internal error 36000 found at:

http://service1.symantec.com/SUPPORT/ghost.nsf/f622fe1b00b168bc882570dc007a01d2/06df7b028e074efa08256831007a9b1f?OpenDocument

none of them have worked.