Ghost reinstalling windows is a fast and convenient way to reinstall windows for the computer, often used for it technicians to reinstall the computer, create ghost versions to quickly reinstall Windows, skip the setup steps. when installing win.
After downloading you need 1 usb hiren's boot to enter the norton ghost program, then select the ghost file in the drive and start ghost windows into the computer, ghost time depends on the speed of the computer and the recording speed of the drive. .
Windows Xp Ghost Image
Regarding SIDs, Microsoft does not support images that are preparedusing NewSID, we only support images that are prepared using SysPrep.Microsoft has not tested NewSID for all deployment cloning options.
Many organizations use disk image cloning to perform mass rollouts ofWindows. This technique involves copying the disks of a fully installedand configured Windows computer onto the disk drives of other computers.These other computers effectively appear to have been through the sameinstall process, and are immediately available for use.
Another popular way of rolling out is by using the Microsoft sysdiffutility (part of the Windows Resource Kit). This tool requires that thesystem administrator perform a full install (usually a scriptedunattended installation) on each computer, and then sysdiff automatesthe application of add-on software install images.
If you have a ghost image created on a PCU50.5-C with Base Software version 1.4 hf02 or later, the ghost image from the PCU50.5-C with XP (hardware 6FC5210-0DF52-2AA0) can be loaded on the hardware platform 5210-0DF52-3AA0 (which is delivered with Win7). This is possible because the drivers that support the newer hardware platform are included in the PCU50.5-C Base System Software 1.4 hf02. This is the only way I know of to make the conversion to the new hardware platform with Windows XP.
Command or Switch Description Z:\Ghost\Ghost32.exe The path and name of the Ghost program being used. -clone, MODE=create,SRC=1, Create an image of drive 1. DST=Z: COMPNAME%.gho Create the image on the Z: drive. The variable of %COMPNAME% will be replaced with the name of the computer being imaged. The path used to store the image cannot be the same partition that is being captured.
(Important: Configure the task to run in the production environment using the Security Context of either Specific user or Run script in console user session. The account used, must have rights to create the image on the destination server.)
mbro I tried my level best to get the dump file, but no success. Windows is unable to create a dump file. As for other forums if there is a major hardware failure then windows cannot create the dump file, but where in VM the hardware is coming up.Flashing the BIOS will only help this issue is persisting a single hardware, but it is showing up whichever hardware i am deploying the image.One thing can help here if I can know which files and registries are getting affected by this bug.
Is this a ghost image of XP Pro or XP Pro Corporate? Also is it just a ghost image of a drive or a drive clone. Did you create it or was it supplied by Dell or Microsoft? The 3-in-1 VLK has a utility to view/change the product key for Windows XP, as well as Microsoft Office, Publisher, etc. if that's all you need to do. Note: XP Corporate uses the same key for all installs up to the Corporate license limit.
Yes, that's possible. The main offender is the HAL type used by the Windows installation - if you create a Sysprep image on a single core processor and try to deploy it on multi core, you'll geht the BSOD.
Personally, when I did this a few years ago and needed many different images, I had many unattend files (made with the deployment tool kit), and put them on different floppy disks, used a USB floppy drive. I had one disk for every configuration and simply used the original cd along with the correct disk and they built fine. Not the best modern way (I think even with SP3, it still only supports floppy drives for unattend), but it worked well.
Ok let me rephrase his question: when creating an image using Norton Ghost you have the option to protect the created image with a password. So the only way you can put that image back on the hard drive is if you know the password.
(3) However, after using Symantec Ghost 11.5 to make an image of the system and deploying it to a real physical machine, the Windows XP sysprepped system fails to boot. Specifically, the system keep restarting even before the Windows logo shows up.
I am a windows experimenter. I recently learnt about audit mode in windows vista+. I started creating my custom editions of windows with all compatible apps/programs installed (NOT for commercial use, just for me). I would install a fresh copy of windows on a VM, press Ctrl+Shift+F3 to boot into audit mode, install programs/updates/hotfixes, run generalized sysprep, and would reboot into a PE to capture the image. Then I'd copy over the wim (or esd) file to my host, drop it in the official iso, and reseal the bootable iso file. I know how to use DISM and ImageX for capturing images. When I came to Windows XP though (i know it is out of support, but still), it apparently had no audit mode. And then when i looked up on the web, I found a few useful articles. Everything went fine until that sysprep shutdown. But I don't remember any windows XP pe out there. I tried Vista PE, but it made a .wim file. I'm pretty familiar with Wim files, but I don't know about windows XP's setup structure. Some articles say I have to somehow reboot into something called WDS, but that feels a little too complicated. Moreover, i think it needs an older WDS version.
But sysprep itself was designed for this type of use.Where I worked we had a department license to install our own modified windows versions on the workstations. If this tutorial is illegal, so is offlinesysprep developed by Galapo: =19397Warez would be distributing the finished copies to the public, I think Jaclaz/Wonko was over-zealous.
The first versions of Ghost supported only the cloning of entire disks. However, version 3.1, released in 1997 supports cloning individual partitions. Ghost could clone a disk or partition to another disk or partition or to an image file. Ghost allows for writing a clone or image to a second disk in the same machine, another machine linked by a parallel or network cable, a network drive, or to a tape drive.
Version 4.0 of Ghost added multicast technology, following the lead of a competitor, ImageCast. Multicasting supports sending a single backup image simultaneously to other machines without putting greater stress on the network than by sending an image to a single machine. This version also introduced Ghost Explorer, a Windows program which supports browsing the contents of an image file and extract individual files from it. Explorer was subsequently enhanced to support adding and deleting files in an image with FAT, and later with ext2, ext3 and NTFS file systems. Until 2007, Ghost Explorer could not edit NTFS images. Ghost Explorer could work with images from older versions but only slowly; version 4 images contain indexes to find files rapidly. Version 4.0 also moved from real-mode DOS to 286 protected mode. The additional memory available allows Ghost to provide several levels of compression for images, and to provide the file browser. In 1998, Ghost 4.1 supports password-protected images.
Released December 14, 2001, Ghost 7.5 creates a virtual partition, a DOS partition which actually exists as a file within a normal Windows file system. This significantly eased systems management because the user no longer had to set up their own partition tables. Ghost 7.5 can write images to CD-R discs. Later versions can write DVDs.
Disk imaging competitors to Ghost have dealt with the decline of DOS by moving to other recovery environments such as FreeBSD, Linux or Windows PE, where they can draw on current driver development to be able to image newer models of disk controllers. Nevertheless, the DOS version of Ghost on compatible hardware configurations works much faster than most of the *nix based image and backup tools[citation needed].
Ghost Solution Suite 1.1 is a bundle of an updated version of Ghost, Symantec Client Migration (a user data and settings migration tool) and the former PowerQuest equivalent, DeployCenter (using PQI images). Ghost Solution Suite 1.1 was released in December 2005. It can create an image file that is larger than 2 GB. (In Ghost 8.2 or earlier, such image files are automatically split into two or more segments, so that each segment has a maximum size of 2 GB.) Other new features include more comprehensive manufacturing tools, and the ability to create a "universal boot disk".[further explanation needed]
The limitations of Ghost 9 compared to Ghost 2003 were not well-communicated by Symantec, and resulted in many dissatisfied customers who purchased Ghost 9 expecting the previous version's features (like making images from the bootable Ghost environment, no installation required, and no product activation).
Supports creating images on CDs, DVDs, Iomega Zip and Jaz disks as well as IEEE 1394 (FireWire) and USB mass storage devices. Supports encrypting images and Maxtor external hard disk drives with Maxtor OneTouch buttons. Ghost 10.0 is compatible with previous versions, but not with future versions.
Ghost Solution Suite 2.0 was released in November 2006. This version provides significant improvements in performance, as well as the ability to edit NTFS images. This version also adds support for Windows Vista, x64 versions of Windows, and GUID Partition Table (GPT) disks. However, the software does not fully support systems with Extensible Firmware Interface (EFI) firmware.
This version provides a "LightsOut Restore" feature, which restores a system from an on-disk software recovery environment similar to Windows RE, thereby allowing recovery without a bootable CD. Upon system startup, a menu asks whether start the operating system or the LightsOut recovery environment. LightsOut restore would augment the ISO image, which comes with Ghost. The latter contains a recovery environment that can recover a system without a working operating system. 2ff7e9595c
Comments