File: symantec_deploymentsolution_8_5_ru4_x64.msiMD5: 3d87af8c4d86d0dfa0401aad92abf8b9SHA-1: 11248a0cc878ddc2f9b5ce5d64dbd380ab754d44SHA-256: 2cf3bb5455547a0e7f0b592fc110c83acd56379e260725953c51db49551ffa8b
I am an intern and I have been tasked with imaging both windows and Linux workstations from a central server. I have a .GHO of my Linux workstation, but I cannot get it to boot. I did notice that when I was making the image it said....
symantec ghost boot cd iso 38
where do I go to add the switch. I am imaging the machine through the linux ghost boot cd. the prompts do not ask for any commands. Would it be in the options or can you give me an example of the full line to clone a machine (ie ghost ????? ?? ? -ignorelvm)
1. In the boot disk creation wizard if I select USB the add additional files dialog shows file size, however, the file is not included when USB is built. I was following a article that showed how to create GhStart.bat for testing purposes. One of the steps has one add it as an additional folder to the destination "Ghost". I have tried to add other files and I have never got this to work.
2. Part of that procedure as well as this one involves editing start.bat by using the "Start Editing" button. I cannot seem to get this to save the changes. I am seeing that if I rem out the existing statements and build the USB boot disk that the start.bat file shows the modification. However, if I try and add the contents of either articles, when built, the start.bat file is blank. Without these modifications two problems occur. First, GhStart.bat is not copied to X: when run and thus I cannot automate the clone. Second, I cannot detect the drive letter where my image is stored since the working environment is X:. This means no automating. I am trying to create a plug and load environment as the USB boot is light years faster than CD and I store more images on a 32GB thumb drive.
Thanks for the reply. I had just sorted that out and was going to post the same. To solve my problem I completed the USB wizard accepting the defaults. The mounted the resulting boot.wim on the thumb drive in write mode selecting 2 with the /check switch. Edited start.bat so that it would parse drive letters C thru K looking for GhStart.bat. Then I unmounted and copied my GhStart.bat to the ghost directory along with the 9 GB image. Everything worked as GhStart.bat also parsed the directories for the image and put the drive letter in my ghost command line. Pretty much the same code as found in the article that shows the use of GhStart.bat.
The one thing that I should note is that I was able to copy the file from the drive to another, do the edits and copy it back over the existing. However, attemptin gthe process using the boot.wim found under all users profile in the templates common directory did not work. After looking at the info on that image vs the one that was built to the thumb drive using imagex there are considerable differences. Since I made that noob mistake I figured I would share.
Because of the problems that I have I had to modify the boot.wim again. However, the same code that checked each available drive letter for the image doesn't work from a Dual Layer DVD. I tried may start.bat modifications to use diskpart to assign the drive letter. In some cases it would work as I could see GhStart.bat copied to X:. However, the command line to automate the restore would open ghost32 and then fail because ghost32 couldn't see the file. Once that window closed if you attempted to access the CD/DVD-ROM by that drive letter is cannot be seen.
You can use Hirens Boot CD. Newer versions have a free alternative to Norton Ghost, older versions have the real Norton Ghost (though it is shareware). Directions on their site how to make the "boot cd" a bootable usb stick. Very simple, only takes a few clicks with the right software (all explained in the link).
I recently bought an ASUS Eee PC 1000H. Lacking an optical drive I wanted to be able to boot my Norton Ghost 9.0 recovery environment from a USB stick. I assume the recent flood of these ultra mobile PC's will cause a renewed interest in this topic.
Format the stick using the HP USB Disk Storage Format Tool (Google will easily locate this free utility for you). No need to use the "Create a DOS startup disk" functionality in this case, the partition on the memory stick will be marked active for boot anyway.
As a side note, except for the formatting part, the same procedure can be used to boot Ghost9 from an external harddrive containing an NTFS partition. That allowed me to put the Ghost9 restore environment together with the actual backup itself onto a single 2.5'' drive in a USB enclosure. Now that is what I call a portable backup solution! In contrast to memory sticks, the normal Windows Local storage disk management console (under Administrative Tools) allows to mark partitions on external harddisks as active. So no need for the HP format utility in this case.
Warning: Follow the procedure below will erase all previous data on your USB flash drive. Please makes sure to back up any important data or settings before continuing.To create a bootable USB for flashing BIOS, re-imaging a drive or capturing an image, you will need to follow the directions below.First place Ghost64.exe and the Ghost image file provided onto your desktop. Insert a USB flash drive to your computer then open Ghost64.exe.Once Ghost64.exe is opened, click OK, on the splash screen, to continue.
Easy2Boot (E2B) is popular multiboot USB solution that also contains agFM and Ventoy. It supports both Legacy and UEFI.Simply copy on your bootable ISO files to the E2B USB drive and boot! Boot to DOS, Linux, Windows Install ISOs (XP>Win11),automate Windows installs, WIM files, VHD files, images of flash drives, Linux ISO+persistence, etc.
I realized that I haven't given you enough information to solve my problem. I am trying to set up a VM of the Win 2003 Server R2 that I currently have running... That is running the VMware... I have a ghost image of it... and want to restore that into a new VM and run the converter on it...
In the 'real world' when I boot from the ghost floppy it recognizes the USB hard drive and I can restore the images from it... I mistakenly thought the new VM would do the same... Same floppy same behavior... but not the case... So I need to figure out how to get the image some place that I can access it...
Yes but when I boot with the floppy, it's like it doesn't go through part of the VM activation for some reason.... and never sees the drive... Could it be because there was never an OS so the vm was never 'real'?
4) In the VMWare Server (or Workstation) console, you pull down the VM menu, select Removable Devices, USB devices and click on your USB hard drive. This will connect the USB hard drive to the VM. If the Ghost boot floppy does recognize USB hard drives, then it should show up in the VM.
If you don't want to reinstall Windows and have a brand new start, the best idea is to ghost hard drive to SSD, which means migrating OS and data directly. Thus you can use the new SSD just as using the old hard drive, but with faster startup and operation speed.
If you simply want to ghost hard drive as a backup, then you can use a built-in or 3rd party backup software. But to ghost hard drive to SSD or another HDD, the most efficient way is to use disk clone software.
To ghost hard drive to SSD on laptop or desktop, the easiest solution is using the best ghost clone software like AOMEI Backupper Standard. Its powerful disk clone feature allows you to ghost larger HDD to smaller SSD, or SSD to larger SSD. And you still can further improve the performance of the target SSD and prolong its life span.
And in premium version, you can enjoy more advanced features, such as, clone and resize hard drive with Edit Partition feature, create portable version of this software and ghost hard drive on unlimited PCs or servers, ghost image to computer with dissimilar hardware restore, etc.
In addition to cloning, you can use the backup features of AOMEI Backupper to image partition, OS or the entire disk. With it, you can transfer system image to new hard drive or even another computer with secure boot.
1. Remember to boot from the network the client must have a PXE capable network card and it must be set in the BIOS to be higher in the Boot order that the system drive, most machines now give you a key to press on boot, to boot from the network (Usually F12).
5. Give it the session name you set up in phase 5, > Either let ghost find the ghost cast server or enter its IP address. > OK > Select the Disk you wish to Image > OK > When asked about compression Select High > Click OK > Imaging will start.
Coming from Windows, I expect that there is some "disk image" utility that I can run to make a snapshot of my Linux install (and of the boot partition!!) before I meddle with stuff. Then, after I've foobar'ed my machine, I would somehow restore my machine back to that working snapshot.
Obviously, a partition cannot be copied while in use: it needs to be unmounted so it doesn't suffer changes during copying (that is self-evident). Therefore, in order to back up your system partition you have to boot in a usb live system - or, as seen in the above image, in a separate (multi-boot) system. The system partition is the one marked with a star. If you try to copy the system partition you get an error soon enough:
Also, one has to take notice that the back-up and the restoration of bootable partitions are both risky procedures and that a back-up of valuable/sensitive data should be first done in a different way (by copying the data instead of the entire partition, etc). - From my experience, this works with Ubuntu system partitions but not with Windows ones.
Restoring a drive imageTo restore a drive image, one will want to boot into a live environment. Restoration is quite simple, and really just involves reversing the if and of values. This will tell dd to overwrite the drive with the data that is stored in the file. Ensure the image file isn't stored on the drive you're restoring to. If you do this, eventually during the operation dd will overwrite the image file, corrupting it and your drive. 2ff7e9595c
Comentarios