Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with Ghost Solution Suite
Showing posts in English
JasonD | 02 Jun 2009 | 4 comments

hey everyone,

I recently asked this question in another forum but received some rather unfavorable answers so I thought that I would try posting it to the community here and see what everyone had to say. I currently have GSS 2.5 installed on a win2003R2 server and I have some how managed to mess up my PE file. To fix it I would like to completely remove GSS and start fresh, please feel free to suggest an alternative.

Anyways, I have run the uninstaller from CD and and deleted the symantec files from within the Common Files within Program Files. However, I am still finding my old modified PE when I look at the Boot Wizard after re-installation of GSS. So, how can I COMPLETELY remove GSS 2.5 and all of the modified files?

p.s. I apologize if this is the wrong place for this question, just looking for an answer and this seemed appropriate. Thanks for any help you can provide.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Jason
SysAdmin /...

Randall Newnham | 12 May 2009 | 0 comments

Error: "Incompatible clone switch on the server side" occurs when using the -sure switch in the boot media to automate an image deployment or capture.

This error occurs when using boot media to automate joining a Ghostcast Server session when neither the boot media nor the Ghostcast Server have the disk number specified. To resolve this, either add the -clone switch to the boot media, or specify the Disk number (and Partition number, if a partition operation is desired) to the Ghostcast Server in the "Client command line options" area.

bruce_in_ma | 03 May 2009 | 2 comments

Problem:    Can not finish a Full Managed Backup with Ghost 14

After running a Full Managed Backup.
I get following error on Norton Ghost 14.0. 4.30.30167:

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\) MASTER2007. Error E7D1001F: Unable to write to file. Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.
Details: 0xE7D1001F
Source: Norton Ghost

This error is consistent when writing to the external USB Rosewill R2-JBOD USB 2.0 DUAL-BAY 1.5GB box.

I get this error only when I send the file to a 1.5TB Seagate ST315003 41AS USB devise.
Another USB devise 250GB Seagate ST325082 4A USB devise does not have this problem.

I read everything you had online about this problem, but nothing helped or explained the problem. Actually I believe wrote that Symantec could not reproduce the problem.

So therefore I will attempt to...

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 | 1 comment

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 | 19 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...