Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts tagged with Ghost Solution Suite
Showing posts in English
Mohammad Bamya | 30 Apr 2009 | 0 comments

When trying to run Ghost32 on Windows 2003 server to create an image from the C drive to another drive even if the other drive is internal or external (such like USB HDD), you will get the following error message:

Error: A source volume could not be locked (640)

That's because Ghost is not designed to create a hot images from server OS.

References:
Tips for Hot Imaging with Ghost Solution Suite 2.5
http://service1.symantec.com/support/on-technology.nsf/docid/2008121215010060

Randall Newnham | 28 Apr 2009 | 0 comments

There are some hardware setups that require using a different version of WIndows PE than WIndows PE 2.0, which is what the Ghost Boot Wizard in Ghost Solution Suite 2.5 uses. The disadvantage to using custom Windows PE boot disks is that some options that are available in the boot wizard are either not available, or it is not intuitive to include. One of these features is DeployAnywhere, the Ghost utility for injecting drivers into a machine after an image is deployed. This method will allow you to use that feature even if you have to use a different PE environment.

How to add DeployAnywhere:

1. Add this file to the PE environemnt:

C:\Program Files\Symantec\Ghost\GhDplyAw32.exe

2. Add this folder to the PE environment:

C:\Documents & Settings\All Users\Application Data\Symantec\Ghost\Template\common\windrivers

This provides the executable and the drivers necessary for evaluating and retargeting. Here is the...

Mohammad Bamya | 20 Apr 2009 | 0 comments

Once the client machine boots up into the PreOS it will need an IP address to communicate with the Ghost Cast Server, and by default that IP address will come from the DHCP. When there is no DHCP server, the client machine will not get any IP address, hence, the machine will not be able to communicate with the Ghost Cast Server.

To force the PreOS WinPE or WinPE-512 to use a static IP address:

  1. Go to "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe\ghost" for WinPE and "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe-512\ghost" for WinPE-512
  2. Remove the read only from start.bat
  3. Edit start.bat using the notepad and add the following line between x: and cd \ghost

    netsh int ip set address local static 192.168.0.100 255.255.255.0 192.168.0.1

    (IP address of 192.168.0.100 with a Subnet Mask of 255.255.255.0 and a Default Gateway of 192.168.0.1 would be set on...

Mohammad Bamya | 20 Apr 2009 | 0 comments

To avoid settting a password to run a Schedule task or Backup Regime, use NT AUTHORITY\SYSTEM in the run as box.

Peter_007 | 19 Apr 2009 | 1 comment

I just wanted to know how to install dell notification server

Mohammad Bamya | 16 Apr 2009 | 0 comments

Trying to restore an image to Lenovo M57, the NIC driver related to Intel 82566DM-2 has been added into the WinPE, Ghost finished restoring the image, and when DA starts processing the NIC driver, it return back asking for:
prounstl.exe file from c:\swtools\drivers\ethernet\a2etn00us17\pro1000\

DeployAnywhere only works with drivers that can be installed from their associated INF file, and on the same time it seems that there is another driver availabe under the OS on that image.

As a workaround for that specific NIC, try to delete the oem.inf file related to the NIC under "\Windows\inf\" from the image

kewidogg | 02 Apr 2009 | 0 comments

There are two ways you can get the client to report to the correct console.

These solutions assume you have a remote client installed, and that it is targeting a console other than the closest one:

Stop the Ghost Service

  • Click Start > Control Panel > Administrative Services > Services
  • Scroll down to any Symantec products. Click the Symantec product and click "Stop the service".

Delete pubkey.crt and dnscache.txt

  • Browse to C:\Program Files\Symantec\Ghost and delete the pubkey.crt and dnscache.txt files.

Start the Ghost Service

  • Click Start > Control Panel > Administrative Services > Services
  • Scroll down to any Symantec products. Click the Symantec product and click "Start the service".

You can reset the client:

Once the service is restarted, the client will search for the nearest console.

Copy the pubkey from the new...

kewidogg | 02 Apr 2009 | 5 comments

This can occur when you do not have enough space on the C:\ drive. Even though the ISO might be created to a external or shared network device, the boot wizard still creates files temporarily to the C:\ drive.

Simple Solution:

Remove files to clear up space on the C:\ drive, and try to create the ISO again.

Advanced Solution:

NOTE: Symantec does not provide support for modifying the registry. Please modify at your own risk.

First, back up your registry. Open the registry, and go to File > Export... and save the registry to a safe location.

To solve the issue, you can direct all temporary files to another location (such as a mapped drive, or external USB device).

Browse to the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

And modify the key:

TEMP (the default location it is set to is %SystemRoom%\Temp)

Modify this key to point to your external or shared...

Randall Newnham | 27 Mar 2009 | 0 comments

I have seen some issues with hot imaging with McAfee installed and wanted to share the resolution I have found. the primary error I have seen is the "Application Error 503. Connection timed out with Ghost code 19945" in the Ghost Console task logs.Here is how to get around this:

1. Open the Image Create Task, click on the Advanced button in the lower right of the General tab add type this in the "Additional options for Ghost command line" box:

-forcevolumesnapshot

2. On the client and server machines, open McAfee and open the Access Protection feature. edit the Prevent IRC Communication feature (there may be an incoming and an outgoing rule; if so, edit both) and add these exceptions:

Ghost32.exe
NGCTW32.exe
GhostSrve.exe

Note: The ePolicy Orchestrator is a utility that is often used along with this version of McAfee to make sure that settings are consistent acros a network; the above exceptions will need to be...

Randall Newnham | 27 Mar 2009 | 1 comment

I have had issues with the HP Elitebook 8530P machines and I wanted to share the resolution I found:

To resolve this issue, you will need to use Windows PE as the PreOS, add the latest driver for the Intel card and add some disk access command line switches.

1. Go to Intel's website and download the Windows Vista driver for the Intel 82567LM-3 network card:

http://downloadcenter.intel.com/filter_results.asp...

2. Extract that driver via these instructions:

How to extract 32-bit Network Interface Card (NIC) drivers without installing them to the local...