I'm trying to create an image of an HP Elitebook 8470p laptop that is brand new. The image creation starts just fine and after about 5 minutes it fails with the Ghostcode error 19922
I've been using this particular ghost enviroment for several years and I've ghosted hundreds of computers with it so it should work. I suspect the problem is related to the particular laptop.
Attached is the ghosterr.txt file.
Any and all comments are greatly appreciated.
WD
On a side note, I like how Symantec 'brags' on this forum with
Symantec Ghost Solution Suite 2.5 is the industry’s most widely-used deployment, system management, and computer imaging software solution.
Yet they are killing this product....
Anyways, I've been experimenting with imaging the surface pro. If anyone else has any info to contribute, please post!
I've been playing with this for the last week. Here's some info:
Boot to USB:
Start your surface pro while holding down the + volume button. Disable "Secure Boot Control"
Reboot the surface and hold down the - volume button to boot to USB.
Ghost:
The surface pro will only boot to a 64-bit OS, so the standard Ghost boot CD/USB won't work. You will need to snag a copy of WINPE4.0 from microsoft and build your own WINPE boot drive.
See here for some more info on building WINPE:
http://www.deploymentresearch.com/Blog/tabid/62/En...
Since you will be using the 64-bit WinPE, you will need to use Ghost64.exe, not the standard Ghost32.exe.
Challenges:
The surface pro uses UEFI, as mentioned before. Ghost doesn't support this apparently; however I remember reading a forum post over at Symantec that hinted at the original developers including code to support it, so who knows.
Windows 8/ Surface Pro uses the GPT file system, not MBR, so this is another challenge. People say Ghost doesn't support that, but I can verify that the original documentation does include a section about GPT support, so it should work.
My attempt to deploy a ghost image to the surface pro "worked" because Ghost doesn't really care what it's deploying to. As long as it sees a disk, it will write the image to it. I was unsuccessful; however, in getting the surface pro to boot to Windows. It just kept going back the EUFI bios screen.
Last comments:
My image was built using VMware workstation, as I've been building all my images this way, and I did not have the partition setup as GPT. I'm suspecting this is why it would not boot. I have not yet had a chance to test further.
I have been using Ghost v15 for backup for a couple of years now. I have started receiving an exception 800706be I have spent hours diagnosing this problem....poking around on the Internet for a fix....replacing my external hard disk, etc.....trying a process of elimination as to what the problem may be. Finally.....I tried Acronis and it works fine......no issues. I prefer to stay with Ghost .....however I am not sure if Ghost is a discontinued product.....it is not even listed in the products list below under Backup and Recovery.
1.Symantec Ghost Solution Suite 2.5 Windows 7 이미지 복제 완료한 후 Windows 7 정품 인증을 다시 받아야하는 문제가 발생합니다. 해결 방법이 없는건지요?
2.Sysprep 적용시 복제된 Windows 7 운영체제에서 정품 인증을 완료하였으나 재부팅한 후 정품 인증을 받아야 하는 과정이 반복됩니다.
Original question posted by Meckron:I used the Erase Machine tool (which only worked in PC-DOS, not WIN-PE, but that's not a big issue) to destroy a machine that was no longer needed. The machine was erased and all went fine. I went to delete the machine out of my database to recover the license and it won't delete. It says that it's part of a report or task, but I've double-checked every task/report and the Executed Tasks folder and have not seen this machine as part of anything else, aside from the Erase Machine task (which, with the log, has long been deleted).
Any ideas on how to remove this machine from the database?
Solution:
Go to your tasks and make sure that you have no tasks referencing that machine name. For instance, I ran into the same issue. I resolved this by checking the properties of each task. I found that my last restore task had the machine name listed in there. Once I pointed it to another machine name, clicked save, and closed the task, I was able to delete the machine.
It would be pretty redundant to have the delete command in the menu, to only have to use a script to get rid of it. Hope this helps, it worked for me....
Hi Everyone.
First of all, forgive me if this is not the right place to put this question.
I have a customer who has a specific need and I have to know what is the correct Symantec product I should use to accomplish the goal.
The customer has a lab with a lot of computers and, eventualy, he needs to install a new program to all computers (the installation of a new program is just an example... another tasks maybe needed too).
He does not want to install this new program, take a new image of this computer and deploy the new image to all other computers.
What he wants is to install the new program in a "main" computer, the image is automatically updated by this "main" computer and the updated image is deployed to all other computers. This is something like to create an updatable baseline...
Wich Symantec program do it? Ghost Suite or some Altiris Product (wich one?)?
I realy appreciate any reply.
Thanks a lot.
Regards,
Fabio N.
I know this has been talked about extensively but I still cannot get this to work. We have new Optiplex 790's and I need to Ghostcast an image. I have followed all the instructions regarding adding the Intel 82579LM NIC drivers and the Pre-OS Rapid Storage drivers to the WinPE editor. I AM using the Vista 32 bit drivers, also. I have imported them and yes, I have clicked the check box. I then format to a USB key.
Whenever I boot from the USB it starts loading the initial windows files and then BSOD's every time. Weather I configure SATA as ATA or AHCI....
The BSOD is BAD_POOL_HEADER. 0x00000019
Please help....Thanks!
Hi
When i shutdown Ghost32.exe and close the Dos boxes then WinPe reboots the machine and i have to quickly pull the USB stick out before it restarts.
Is there something i can change so WinPe exits to shutdown instead or restarting?
Thanks
We deploy windows based servers appliances (Windows 2003 / 2008 Standard Server), all of which run in a "Kiosk" sort of fashion. We buy a multi activation key from Microsoft and have a special server build that needs to look and feel the same at each site (ie security – ip addressing – server name – licenses etc) – all servers are created equal on same exact hardware.
A while back we used Ghost (DOS) 8.2 to create our windows 2003 server image file. When we cloned the images everything came over from the image file. Today our manufacturing company told us to use Ghost (DOS) 11.5.1 with sysprep.exe. I really didn’t think sysprep was necessary since each build server should be the same. In addition it’s a pain to clone my image of the server; hence I saw that the interfaces (names / ip addressing / metrix etc) were blank. I also noticed that the Microsoft license has been reset to invalid. Is there any way around sysprep? Why is this info not appearing on my cloned image? Am I missing something? Please give me some pointers on how I can this process easier.
Thanks,
Ghost - line command.
c:\ghost\ghost.exe -clone,mode=load,src=c:\ghost\images\6550-R4\0362012.gho,dst=2 -sure -rb
We're using Ghost 11.5.1.2266. I start a session, when I boot to the E6520 to Ghost, navigate to multicast, they all pull a 127.0.0.0 address. I'm using WINPE Vista 32 bit drivers when creating the USB Ghost boot disk, the NIC cards are all the same (Intel 8579LM), using 11.15.12.0 drivers. There is no error message being thrown at any point in this process
Experiencing this issue on Optiplex 990's however with any other machine in our environment we are able to Ghost over the network. The difference with those machines is they're older models (755's 620's Etc) we can use DOS drivers to create those Ghost boot USB's.
Please advise if any other information is needed.
Thanks
In Windows Server 2012, when creating a New Configuration Set I get this error when using asterisks as wildcards for the computer name:
"You must specify a valid computer name, that does not contain any '*' characters"
Symantec's own configuration instructions say to use asterisks as wildcards, so I'm not sure why this error appears, unless it has to do with compatibility of my version of Ghost Console (11.5.0.2113) with the OS. Any help is appreciated. Thank you.
Hi,
I am having problems deploying my images from ghost console, and am receiving "ERROR - to virtual partiton - could not defragment virtual partition"
clients - chipPC thin client running windows embedded standard SP3 intel atom n270, 1GB ram, 2GB SSD hard disk
Server Windows 2003 R2, program version 11.5.1.2266.
Image is windows embedded standard . NTFS size 1998.3 MB, Data 1559 MB
cd/bootable hard disks work fine - I can boot into WINPE - map a network share and upload the image, then name the machine.
However I dont want to visit the machines individually as I have more than 500 to image at once!
I believe the problem is when it is trying to create the virtual partition - it is trying to find continuous space perhaps....
When I boot into windows embedded, it does not contain the defrag executable in system32. I have tried dragging a copy in from WINXP but it is then missing .dll files.... If I try and load it into MMC it does not allow defrag to be used as a snap in - so I assume Windows embedded has defrag stripped out.
I have used a 3rd party program "JK Defrag Portable", and defragged the drive first and then re-imaged. this does not work. The Console always seems to want to defrag the drive....
the virtpart.dat file that gets created into root C: as part of the task is 207mb. I have deleted this and tried to run the task again. still the same impact.
any help much appreciated!
thanks
craig
I have a WINPE file that I use for ghost. It has ghost32.exe in the system32 folder and that gets called from the startnet.cmd file. When ghost launches the command window is minimized and not available. If I unminimize it and look at it, it just sits there with a flashing cursor until I close Ghost.
This is what it looks like:
I would love to have access to the command window while Ghost is launched.
I know the Ghost WIM that gets made by the the ghost suite wizard on the Vista platform actually did this but since I am making my own WIM's now I seem to have lost that functionality.
This is what the Ghost solution suite wizard makes for you. It works great:
Can anyone please tell me how to make that command window active and available WHILE ghost is running? i know it is possible because it works fine if you build a vista based WIM using the built in utility Ghost provides.
My startnet.cmd looks like this:
wpeinit
start ghost32.exe -ib -rb
Hello
I am trying to reimage a optiplex 790 with a windows 7 32 bit version. my GHOST CAST version is 8.0.0.984. I have created images for optiplex 780's before with no problem. i really dont know what the issue is, any info about this is much appreciated.
thanks
I followed the Symantec Article TECH110220 "How to use Ghost to create a WinPE boot DVD with a Ghost Image on the same disk" and the drive that I Ghost is not bootable. I ran the image manually and get an error that the bootmgr is missing.
We are trying to create an image of a Lenovo-M82 Windows 7 computer. We are using GhostCast server 11.5.1.2266. These are new windows 7 installations. The GhostCast session starts normally and gets part way throught (79% and once 99%) and then errors out with a "an internal inconsistency error 39000". We have run chkdsk, defrag, etc. and still get this error. We have also tried on other computers of the same type all new installations with the same errors. We have tried running chkdsk and defrag without results.
Any help would be greatly appreciated.
Art W.
Okay, so I'll try to be detailed while being brief (if that is possible.)
I have a new Lenovo X1 Carbon that needs to be imaged using GSS 2.5.
The only ethernet connection on this machine is a USB-to-Ethernet dongle. The model is an Asix Ax88772b. I am able to PXE boot to WinPE, but there is not an IP Address when booted to WinPE. I'm assuming this is because WinPE does not have the correct driver.
I found this forum article: https://www-secure.symantec.com/connect/forums/lenovo-x1-carbon-imaging-ds-71-ghost and tried downloading the attached driver. I tried downloading the Lenovo driver from their site. I tried exporting the driver from the copy of Windows 7 that came stock on the machine. I tried downloading Lenovo's SCCM driver, AND I tried downloading the XP, Vista, and 7 driver directly from Asix's site.
Whenever I try to import these into WinPE via the Ghost Boot Manager, it says "Failed to import driver (driver name). Failed to find any drivers to add."
I have successfully added drivers to the preboot images previously using these steps: http://www.symantec.com/business/support/index?pag...
I have also tried throwing the drivers from these sites onto a flash drive, PXE booted, and used the "drvload" command to test them. WinPE says they loaded successfully. However, I am still not able to obtain an IP address.
My brain hurts and I'm frustrated. Any help? Any at all? Because you would be my hero. I would yell your name from the rooftops.
Thanks.
We've been sitting on ghost for over a year after getting it when we purchased something else. I'm just beginning to try it out as I'd like to be able to image some of our PCs and servers. I have it the console installed on Windows Server 2008 and I'm trying to image a Windows XP machine but I keep getting an error that says it failed druing the Initialization step. I'm not sure where to go from here or what to look for to resolve this so I'd appreciate any comments/suggestions.
This is on Symantec Ghost Console v11.5.1.2266.
Thanks.
Hello everyone,
We have a number of standalone computers that run critical applications. We have created backup images using various products. But I would like to standardise this, meaning to just have one solution that we can use to create a backup image of all our standalone computers. I am also looking for a solution that is hardware independant.
I am investigating the Ghost Solution Suite and would like to propose this solution to my manager.
Can you share your experiences with me if you have used this solution for your standalone computers? if not Ghost Solution Suite, then what solution do you use and can you share with me your experiences?
NB. We have ITMS Suite 7.1 but the standalone computers that I am refering to are not configured to the "standard" of our organisation and thus not connected to our network.
Thank you in advance
Bonjour, j'utilise la console ghost pour descendre une iamge Windows 7 et ensuite faire un DA. Cela fonctionne très bien avec un type de machine mais pas sur mes dell 390. En fait sur la première c'est bien le disque c: qui est actif mais pas sur les dell 390 (f:). Donc, en lisant sur le site :https://www-secure.symantec.com/connect/forums/clone-task-w-deploy-anywhere-continuously-running-not-failing DA veux descendre les drivers dans c:\ddb mais pas sur le (f:).
Que puisje faire pour que DA fonctionne correctement?
Merci d'avance