Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Ghost Solution Suite
Showing posts in English
Cobra7 | 03 Mar 2009 | 1 comment

Adding Drivers to WinPE (Ghost boot wizard or Ghost Console) .                             

Note: In order to add drivers to the Ghost Console the Ghost Boot Wizard must be used.
  1. Start Ghost Boot Wizard.
  2. Select Windows PE and click Edit.
  3. Highlight WinPE and click Edit
  4. On the right wide will be a button named “Add new driver”, click it
  5. Browse to the .inf file and select it
  6. Name it the name of the driver (i.e. Intel e1000 Pro, Broadcom 57xx)
  7. Select Vista and XP and click Ok.
  8. The driver will now appear on the left side unchecked, check the box next to it.
  9. Click Ok, Ok.
  10. If you wish to make a new boot disk or VP, continue to do so, otherwise click Cancel to leave the program.
Randall Newnham | 25 Feb 2009 | 2 comments

It is possible to run DeployAnywhere when using a PXE service to deliver the Ghost boot package. This method requires use of, and assumes familiarity with, drive mapping. Here are the steps to accompish this:

  1. Create a Ghost Boot CD with the DeployAnywhere option checked.
  2. Copy the contents of this CD to a new folder on a network share. I recommend the name DeployAnywhere.
  3. Create a new PXE boot image, making sure to fill out the Client Settings window with the drive mapping information. If using 3COM Boot Services, you can use the TCP/IP Network Boot Image option and add the settings in the Client Settings window in the Ghost Boot Wizard. If using Windows Deployment Services (WDS), you will need to add the Net Use command with these setting to your Windows Image (WIM). For assistance with this, please contact Microsoft support.
  4. When running DeployAnywhere, note that the command line will need to refer to this path for the windrivers folder....
arjain | 08 Dec 2008 | 0 comments

Editing ghost images slows down deploying image time as ghost images (gho/ghs) become fragmented.

This fragmentation is caused due to add/remove/modify of files done from Ghost Explorer.

To increase performance, open modified gho files in Ghost Explorer. Goto File > Compile.

Save As Dialog box will appear.

Tip: by default Span Image is checked, uncheck it so that gho can be managed easily, before that check you ghost version, as earlier ghost do not support gho more than 2 GB.

Write the file name and click on Save button.

Ghost Explorer will compile the image and will create a new image.

Use the new image for better performance.

arjain | 03 Dec 2008 | 2 comments

Ghost Explorer (Ghostexp.exe) allows you to view, add, delete, launch and extract files from a Ghost image (.gho) file.

Following task can be performed using Ghost Explorer:

  1. View image file contents and save a list of files within an image file.
  2. Extract files or directories from an image file.
  3. Add, move, copy, delete, and launch files from and within an image file.
  4. Drag-and-drop functionality.
  5. Span sizes can be set.
  6. Add/edit description of image.

Ghost Explorer supports different partition types from FAT 16 to NTFS and Linux Ext2/3

Jamee McDonald | 02 Dec 2008 | 0 comments

When you run Sysprep on one platform and deploy the image to another platform, you would ordinarily expect Plug-and-Play to handle any hardware differences (assuming that the machines use the same version of Ntoskrnl.exe and Hal.dll). However, mass storage drivers represent a special case. The boot loader needs to load the mass storage devices prior to initializing the operating system, so there's no opportunity to let the Plug-and-Play Manager shuffle around drivers. For this reason, it's fairly common to get a "0x0000007b bugcheck" error following the deployment of a Sysprep image to a machine from a different vendor, or different models from the same vendor, even though you're using what appears to be a generic Integrated Drive Electronics (IDE) controller in both cases.

Ghost version
Hardware: any


Jamee McDonald | 02 Dec 2008 | 0 comments

I just had a customer with an issue where after restoring an image from a machine of identical hardware, they could not get a USB storage device to install correctly. The Windows New Hardware Installation Wizard starts up but then fails to add the new device.

Software used Ghost
Hardware Dell GX280

The issue seems to stem from the fact the customer took the image off of a machine with Deep Freeze on it. He did thaw the machine before taking the image. Deep Freeze may need the file system layout to be pretty identical to the source of the image for it to work.

As far as I can tell this more than likely is an issue within Windows to detect hardware. And with the introduction of Deep Freeze the issue may be even more compounded.

Regardless of the underlining issue, this can be worked around, in some...

kewidogg | 10 Nov 2008 | 0 comments

There are two steps that have been proven to work when receiving this error. They may not be the only solutions, and may not work for every machine and situation. Only perform these solutions if you are sure you are using the correct NIC driver, and have exhausted most other troubleshooting techniques.

Solution 1:

* If you are able to still boot into Windows on the client machine, do so. Click Start > Run. Type "cmd" and hit enter. Type "chkdsk /f" and hit enter.

Boot into a ghost boot disk.

When ghost loads, exit ghost so that you are at a DOS prompt (in WinPE, it is in the background behind the Ghost client. In PCDOS we need to exit the ghost client and it will exit to a DOS prompt).

In the DOS prompt, type "chkdsk c: /f" where c: is your drive that you are deploying your image to.

Let chkdsk run...

Randall Newnham | 03 Nov 2008 | 0 comments

I have seen a few cases with the new HP Elitebook 2530P. The default Windows PE builds do not have the latest Windows Vista driver for this and it must be updated. The driver necessary is the latest from Intel, version 13.1.2 or later. Here is a link:!

I posted this as a heads-up because these machines will not boot to either PC-DOS or MS-DOS with the latest DOS drivers for the network card (version 13.1.2 as well, as of this post. Versions of the NDIS2 after 13.1.2 may work, but the latest Vista driver is necessary...

kewidogg | 31 Oct 2008 | 0 comments

Sometimes you have a self-installing executable (.exe file) that may contain drivers, and want to extract them instead of installing them locally to a machine (to use with Ghost Boot Wizard, for example).

The quickest way to extract drivers from a self installing executable file, is to use a 3rd-party zip program such as Winzip, Winrar or 7Zip.

Just open the zip program, and go to File > Open or File > Open Archive and select the self-installing executable. You may need to change Files of Type to include self extracting executables.

Jamee McDonald | 29 Oct 2008 | 3 comments

We have all seen at the end of the boot wizard, when selecting your media package, the option for 'Support for bootable cd/dvds'. This option is supposed to make it so, when it is selected you can choose your cd-burner as a destination drive for your image. What it also does, is makes the first disk of your image set; bootable.

This has been a constant frustration for me as a tech to help customer's find a resolution.

Most times, the cd-burner does not appear. Instead of messing around with GCDROM.SYS and MSCDEX.EXE. A simple way around this is to as soon as you boot up into Ghost, remove the media from the drive. Then proceed through Ghost. The cd-burner should appear as a valid destination.

I have tested the multiple times, not only for my own purposes, but also with customers. Thank you!!