Deployment and Imaging Group

Hello I’m in the process of evaluating if Ghost Solution Suite 3.0 is the right product for my department to purchase.  I have downloaded the 15 day trial and have reached a point where I became stuck.  I keep receiving “Error -99 during imaging process” When I’m trying to deploy a image onto a computer.  Can you please assist me with error before my trial expires.

This is most likely a result of the Default drive letter being F: in automation.   If your system has a few drives in it then when we try to map F: to the network on the client there will be an error noting that the drive is already in use.   

If you install HF1 and then rebuilds your automation environment the new default is supposed to be M:  This may not be the only issue but I would recommend you to try this first.  

Link to HF1 document is here.   You can download it from the trial pages and install it to his trial no HF1 install.

http://www.symantec.com/docs/DOC8871

Link to a long discussion on the ways to manually change the drive letter here.  (ds6.9 but same steps)

http://www.symantec.com/connect/forums/change-default-drive-mapping-automation-partition

What boot meathod are you using?   PXE, USB automation disk, or Enbeded automation partition?   

Also take a look at the following known issues list for more items to be aware of. 

https://www-secure.symantec.com/connect/forums/gss-30-known-issues-please-read-first-posting

Thanks

Thanks for the reply.

I downloaded the Hotfix but when I try to run it I get "Cannot proceed with the installation. No previous installation of Ghost Solution Suite 3.0 is detected on this computer"   Could this be because I installed Ghost Solution Suite 3.0 on the "D" drive instead of C?

I hadn't heard of an issue of non c drive installs but I have only personally done c drive installs.    Too much history of issues in support when using non standard install locations.   

I will add it to my list of things to test for the HF1.     

For now if you modify the mapped drive and rebuild your automation (pxe or embeded automation partition) then you will likely be past the 99 error.   drive mapping isn't the only thing that will cause it but most common that I have seen.   If you have a laptop can you remove the cd drive?    That would eliminate one local drive letter and for testing maybe would allow you to take and restore images without changeing the F drive. 

@ ICHCB - there is an issue with the Ghost 3.0 installation not finding the ADK if it is installed on D:\.

I suspect the Ghost 3.0 installation process has something hard coded to C:\ and therefore any installs to a different drive letter are going to have problems at some point.

So I reinstalled Ghost 3.0 Suite and applied the hotfix.  Everything is installed on the C drive and I still recieve the same error message.  I even tried to create a backup of a computer and received the same message. Any ideas???

are you seeing an error message on the target machine?  for a lot of my machines I have had to add -ntexact to the end of the Additional Parameters string in the deployment job.

Did you confirm that when in automation you have a drive letter mapped to the express share?

Still the number one reason that this error will come up.   The default drive letter is F while in windows PE this was changed with the HF to M drive.   It is possible that the setting didn't correctly get applied and your client is using a lower letter than M while in windows pe still.    If this is the case then the same workaround of changing the drive letter for your automation is required. 

How are you booting your clients to automation?  PXE? 

Hi Yes the error on the target machine. Where should I add ntexact. I'm a newbie to the Ghost Suite I'm using the trial software.

I found that even after the application of of the hotfix, the automation partition on the client was still pointing to the F: drive, I had to remove the automation partition and re-install it to fix the issue. After I did that I never got the error. I actually have the system installed on the d: drive and I can't say I've seen the ADK error?

when you are setting or modifying the job properties , the second field is Additional Parameters:

the box is pre-populated with -clone,MODE=create,SRC=1,DST=%IMAGE_FILENAME% -sure

go to the end of that string and append -ntexact

https://support.symantec.com/en_US/article.TECH130961.html

Here is a complete list of switches that can be added to the Additional Parameters field.

Depending on the system you are trying to reimage, this behavior can also be caused by trying to reimage a system that has a solid state drive.  Newer versions of ghost attempt to perform a trim operation when it detects the hard drive is solid state media.  You can avoid this by adding a -notrim switch to the distribute disk image task.  The -notrim and other swtiches such as -ntexact can be added to the text box labeled "additional parameters." 

I'm using automation.  I went in and a manually change to force the agent to use W drive. Lets see what happens