Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Ghost Solution Suite
Showing posts in English
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...

MT3 Duncan R. Green - US Navy | 25 Mar 2009 | 2 comments

A few months back (probably almost a year now, actually), my organization bought several (*cough* 90, whoops) licenses for Ghost Solution Suite 2.0. After several weeks of installing, uninstalling, reinstalling, conifugring routers, mucking with the domain, and client installs, we finally got it to work in conjunction with WINS. Because of the nature of my organization, we don't have direct control over our routers and switches - they're controlled remotely at another site several hours away. As such, we are unable to use Mutlicasting.

So, late one night when we finally had GSS running, one of my coworkers and I decided to see what we could do with it. We noticed that we could edit different computer settings - domain membership, computer names, etc.

I would also like to point out that at this point, we didn't have a console account set up for Ghost in the domain.

You can probably see where this is going.

My coworker decided to...

Randall Newnham | 19 Mar 2009 | 2 comments

This error can occur when you are trying to automate a Ghostcast session with the -sure switch. What is going on is that the the disk is not specified. In a non-automated Ghostcast session, the user specifies the source (for image cration) or destination (for image restore). When adding the -sure switch, the -clone switch either needs to be included in the boot media, or the disk number needs to be specified in the Ghostcast Server session in the "Client command line options" area. this particularly useful in a PXE deployment environment when the switches -ja=<sessionname> -sure are typically added.

Randall Newnham | 19 Mar 2009 | 0 comments

Due to limited memory, installing a Ghost client on these devices will fail. 1-click virtual partition boot media tends to fail, as well. Here is a method to backup and restore to an iGel Thin Client:

1. Create a Standard Ghost Boot Package using PC-DOS on a USB flash drive.

2. Boot to that device; the boot order will need to be changed to allow booting to that device.

3. Choose Local > Disk > To Image to backup, or choose Local > Disk > From Image to restore.

Note: The USB flash drive used will need to be large enough to accomodate the Ghost boot package and the image.

Randall Newnham | 06 Mar 2009 | 0 comments

Ghost Console Clients will not be able to connect to the Ghost Console if the PIX firewall is blocking access to the multicast group ID address of 229.55.150.208.

Configuring the PIX firewall to allow the clients to multicast to the multicast group address 229.55.150.208, and configuring the firewall to allow the Ghost Console to send unicast UDP traffic to the clients will resolve this.

Alternatively, using the Ghostcast method with either the switch -JADDR=<serveripaddress>, or by entering the server's IP address after entering the session name will work. This bypasses the need for a multicast communication for client identification.

Cobra7 | 05 Mar 2009 | 0 comments

Symantec User Migration (SUM) is a great tool to pull a users files, icons, registry settings and Windows settings and put them in a nice and neat little file. They can either then be saved as a backup or installed onto another PC.

The Following back files are what I use to capture and restore a users settings. I keep them out on the network for easy access. Also please note I have SUM installed on the network server and a custom SCMMigrationOptions.xml is being used.

To Capture I use:

@echo off
echo "This will use SUM Wizard to capture a users data for Desktops"
echo "Enter name "
set /p UserName=

echo "Saving to \\Server\share\User_Migration\%UserName%.ump
pause
"
\\Server\share\SUM\User Migration Wizard\SUMWizard.exe" /action:create...

Cobra7 | 03 Mar 2009 | 9 comments

This is for the Windows (and WinPE) drivers for any PC that uses Intel network drivers 825XX (Such as 82567LM for example) and how to put them into WinPE.

First you will need to download the drivers from Intel, NOT Dell or HP or whatever brand you have.

You can find the site http://downloadcenter.intel.com/

On the search, type in the network card type (example, 82567LM). Follow the instructions, make sure you get the Vista drivers and not the ones for Windows 64.

The file you should be downloaded should be called "PROVISTA32_v13_5.exe"

Next, you can either use WinZip or WinRAR to extract the files by following this Blog: https://www-secure.symantec....