Symantec Ghost Internal Error 36000
Kenya Ahyet
Is it possbile to enter this type of host name on the Configuration of Computer after Deploying a Master Image? We are planning to Put the MAC Address of the Computer, What VLAN it is, Computer Type (Laptop or Desktop) and lastly last 5 Serial of the Computer
We observed that with GHO image file of > 15GB, the maximum number of multicast clients allow to connect and cloning is 32 only. If using a small GHO image like (3-6GB GHO), it able to multicast to more clients, eg: 36 clients for our use-case. The setup is with Cisco managed switch and properly configured for IGMP and etc. All experiments done with same network and setup, just different GHO image size. From ghost logs able to see all clients did connected to GhostCast Server, but GhostCast Server only replied to 32 clients and no more.
Update: Recompiling one of our WinPE bootdiscs hasn't helped. Same error across at least 6 different hardware configs ranging from notebook to desktop to workstation. I can't even see a window being called for the Deployanywhere task - whilst running it by hand you see the expected output so this appears to be an issue with our upgrade or a straight up major bug in RU6.
I created a image by Ghost and try to use Ghost Explorer to delete some useless files from the image. When I delete a fold, the ghost explorer seems idle whlile delete one file. The status bar shows "delelting file XXXX.YY", and keep the statment witout fresh the file name. I can only browse the file list, nothine else can be done. I have to close the application though it mentioned that stop the operating can damage the image file. And the image file does danmaged. I have tried to open it by ghsot explorer, tried to recovery the image to disk by ghost, both the applications crashed. I use ghost to check the image, and it gives a error message "Internal error 36000, An internal inconsistency has been detected, If the problem persits... " There are really improtent files in this image, and I have no backup. Such problem happend on ghost explorer does trouble me a lot. Can anyone help me recovery the image file and find my files back? attachment is the error log created by ghost. May it can help.
I know this is an old error, but I have only ran into it now and cannot find a way around it. Using ghost32.exe v11.5.1.2266 - I created a GHO image spanning over 23 GHS files. I deleted a couple of files using ghost explorer and then it seemed the image was corrupt when trying to restore the image to a drive. It said it is not a valid image file. After doing some checks I managed to "fix" the header to a point that it now sees it as an image and reports the data size correctly, etc, but when the clone from image starts it immediately stops with application error 10024. When doing intergrity check it shows - Bad Image header expecting type:4(412). Error log shows error 10024, Bad Magic.
Is there a way to pxe boot without an agent but see the image file that you need to select and did an image will come down on that laptop or computer? How do I get a image onto a laptop that just came from the factory ? I'm using ghost 3.2.
The Problem we are running into is that the Windows Professional and Office MAK key are not carrying over to the imaged computers properly casuing activation to fail. Any idea why that would be and is there a solution to solve this?
In the Generalize section of unattend.xml PersistAllDevicesInstalls is set to True. Execute sysprep \oobe \generalize \unattend:C:\unattend.xml. Prior to doing so in an attempt to quiet the store disable wireless adapater (Probably not best way, but I doubt this is contributing to issue). On reboot I can clearly see some command window open and close. Sysprep stalls with an error from Synaptics about an error when an uninstalling. I can't even get access to keyboard or mouse to take a look at the system to see what else sysprep feasted itself on. I know you can also hard code into the registry the above mentioned setting. This last time around I neglected to do so. But what is bugging is me why the unattend did not process. I know it went through it because there is a section for creating a secondary admin type account.
I also tried to uninstall the Synaptics software and force windows to use a generic driver, which worked. But post sysprep re-boot I got same error. How is this possible when the offending software uninstalled before running sysprep again.
I PXE boot computer labs for imaging. My Ghost (3.2 R3 at the moment) PXE server lives on a Windows 2008 R2 server that I use for Ghost. DHCP is managed by central IT, and I have applicable DHCP options set to make PXE go. PXE works fine when I boot a machine in legacy BIOS mode. It gets a link, gets an IP address, downloads the PXE boot menu, times out appropriately, it's all good.
I changed the bootfile name in DHCP from BStrap/X86PC/BStrap.0 to BStrap/X86PC/BStrap.efi. I try to PXE a machine in UEFI mode, it gets a link, gets an IP address, downloads the NBP file successfully, and then exits without an error.
I haven't been able to find much concrete information on this topic and would like some feedback. I'm creating a Windows 10 image (with the proper VL in place) in VMware and would like to use this image as the "standard image" that I can use to deploy. My question is how viable is this through Ghost?
I manage a 30 PC computer lab for a department at a college. We configure the image, sysprep it, the deploy it. With Windows 10 however, that produces insanely long load times. Some students report waiting up to 5 minutes to log in. Log offs can also take 5-10 minutes.
I've taken steps such as keeping the number of programs in the base image to a minimum and installing everything afterwards with scripts, I've also removed all of the Windows store apps and our group policy campus wide disables the windows store.
2.) When doing the scripted imaging, the partitioning part confuses me. All of the drives are NTFS formatted SSDs. Do I need a custom script or can I use diskpart? If I need a custom script, are there any resources on what that would look like?
I'm trying to pull a Windows 10 Education 64-bit image and the computer will boot to automation but once it gets to the Client Record Updated screen it just sits there and never starts the create image job. The computer name and MAC address fields remain blank. I've tried recreating my boot images 3 times, reinstalling my WADK, and tried tinkering with PXE settings but I can't get past this. Any help is appreciated. If you need more info let me know.
I've been manually creating fresh WinPE boot disks for years, copying the full "\ghost" directory from boot disks originally made with Ghost Solutions Suite and just dropping a small batch file to run the application as WinPE loads. It works flawlessly and allows us to import dozens of Dell WinPE drivers from their .cab files in a single DISM command; we used to do this with GSS, but adding individual network and storage drivers to the boot disks via the Bootwiz application was always too tedious.
My question is this: within the \ghost directory there are many executables, .dll files, and scripts (like gdisk, ghconfig, etc. etc.), but are they necessary for Ghost64.exe to function, or is that single executable the only one I need to incorporate into my boot disk? NOTE: These disks are NOT for booting to automation, or any other complex task; they are SOLELY used to manually image machines 1:1 from external hard drives or to manually boot and join them to a GhostCast Server session running a local technician's console, typically with a private network switch for small multicast jobs. I've built a WinPE 10 boot disk using only the Ghost64.exe application and it appears to be working just fine - I just want to make sure there isn't some hidden catch I'm not aware of.
I'm not sure where to start, but I'm running a distribute disk image job against a machine. PC reboots, connects to PXE, boots to WinPE, loads drivers successfully, and establishes a network connection. Then it starts dagent. Dagent displays "client record updated" but that is where it stops. It shows the address for my server, it shows the address for the client, but it doesn't display computer name or MAC address.
I'd like to troubleshoot why it hangs. Are there logs I can create that can assist here? Any advice or tips would be appreciated. I'm running a trial version of GSS 3.2 trying to get a proof of concept going so we can evaluate this product.
Trying to burn a number of USB sticks with an image and getting Inconsistancy error. Internal Error 8027. At least half of these drives are getting this error. I don't have the option of getting new ones. I have been told to make these work.
Si estais trabajando con Norton Ghost desde DOS, y a la hora de realizar la operacion de Disk -> From Image, os aparece este error -> Internal Error 36000, la solucion es FORMATEAR el disco duro en NTFS previamente antes de restaurar la imagen del mismo.
Con ghost explorer, podemos visualizar la imagen sin montarla en un disco duro y tomar lo que nos interese, por ejemplo, ese documento que necesitamos y esta dentro de la imagen o esa fotografia que queremos ver sin tener que restaurar la imagen.
1- Siguen el proceso de crear la imagen aun cuando le muestre el error
2- Una vez creada la imagen, procedan con montar en la particin o disco requerido.
3- Despus de montada la imagen, el sistema no les carga, deben de insertar el disco duro del mismo sistema operativo que corresponda a la de la imagen y van hasta el apartado cmd y all aplican el comando CHKDSK C: /R
Terminado el anterior proceso, deben de ir a la bios y poner el modo de arranque UEFI.