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
Randall Newnham | 22 Apr 2010 | 0 comments

I have seen an issue with Ghosting the Dell Vostro 430 machine where it fails and (in the console) refers to the storage driver. This model does not use the more common Intel ICH9/10, but instead used the Intel Series 5 chipset. Here is a link to these drivers:

http://downloadcenter.intel.com/Detail_Desc.aspx?a...

Add them according to these directions as a Vista driver (as required by WinPE):

 
Why does Symantec Ghost need drivers for Windows Vista when imaging some other operating system?...
Randall Newnham | 19 Apr 2010 | 0 comments

I have noticed that there are issues with cloning the Toshiba A500 series laptop. The cause is that it has a different storage controller, the Intel Series 5. I expect more laptops are going to be using this in the future, and this would be a good driver to add to your Windows PE build. The driver itself is a bit hard to locate; the only download I was able to find was in a larger package containing a large number of other drivers. Here it is:


 
https://www-secure.symantec.com/connect/downloads/winpe-driver-intel-series-5-chipsetsata-controller 
 
Please note that this is a Windows Vista driver, as required by Windows PE. Make sure that when you add it, the Vista box is checked. Here are instructions:
 
 
How to add drivers to DeployAnywhere or WinPE.
...
akukalle | 07 Mar 2010 | 5 comments

Hi

I have used Ghost Solution Suite since 2006. It's great and simple tool (thank you Symantec). But i haven't never heard that somebody in Finland uses GSS. If ghost is in use they use only ghost cast server tool. Basically that is waste of money because GSS have many features. So i have made basic manual (in Finnish) how to use GSS in active directory environment. Enjoy www.ictmanuaali.net/ghost-solution-suite-gss

jmetzger2 | 28 Jan 2010 | 3 comments

Thank you to all of those who have joined the Altiris Cincinnati User Group.  Please pass the information onto your team members and anyone else in the Cincinnati/Dayton/Northern Kentucky area.  We would love to see this group grow and be able to host an event here in Cincinnati.  Look forward to meeting all of those who use this fantastic product.

Randall Newnham | 27 Jan 2010 | 0 comments

I encountered this particular error recently and I wanted to share it. I had a customer who was a creating a PXE boot image through the Ghost Boot Wizard (version 11.5.1.2266). He was previously able to create a boot image, but after adding a driver to the Windows PE build, he was no longer able to do this. The issue was that the name of the boot package overlapped with the name of the default Windows image file for our build of Windows PE (boot.wim). This is an issue because while making the boot image, we must mount and open both the default Windows Image file for Windows PE and the boot image being created, and two with the same same will conflict. This likely doesn't happen before adding drivers because of order of operations for the creation, but that is just speculation on my part.

This issue can be resolved by naming your boot image anything other than 'boot'.

Thank you,

Randy

yogeshsadhu | 06 Jan 2010 | 0 comments

Good news for you all!

GSS 2.5.1 is now avaliable for Live Update !

This update supports for two new operating systems Win7 and 2k8 R2.

In addition to Live update 5 , this release is also made available as media ship.

Go ahead and do the Live update for new Ghost Solution.

Please share your experience with win7 and 2k8 R2 imaigng.

The product version will be 11.5.1.2266.

 

Randall Newnham | 04 Jan 2010 | 1 comment
An environmental issue has been noted in a few networks when trying to deploy an image to machines across a network that utilizes switches or routers with different speed hardware (100 and 1000, for example), and the session or task fails.
 
This is an environmental issue. Though Ghost will work in most network configurations, some specific hardware setups will cause issues. This is not expected behavior, but probably motivated by other factors on the network.  Since this is motivated by the physical environment, modification of network hardware may be necessary. First try updating the firmware for all devices to see if this resolves the issue. If this fails, two solutions are possible:
 
1. Reconfigure switches so that machines are all on a switch of the same speed.
2. Run separate deployment tasks to machines on different speed hardware. This will likely mean machine groups in the console require...
Mark Downing | 16 Nov 2009 | 3 comments

I recently installed Windows XP SP 3 oin my new laptop (Dell Studio 1555) and  necxt installed Ghost 2003 after all device drivers for the OS were installed. I normally create a Ghost image DVD affter a new O/S is installed so I can always get back to a working system in short order.
This time when I went inbot Ghost it's normal menu in PC DOS came up but it is stuck in a loop and won't clone, go inot ghost or go back to Windows.
Instead, it seems to freeze up when I hit either option. It says in option 2 to go back to windows but it says returning to windowws and just never get's there.

How do I get out of this loop and get back inbto windows? I have read everything I can find and I have a hunch there is a problem with the Ghost instalation or  perhaps it hangs from a device driver  in DOS mode? I'm guessing because I've used Ghost a number of years and never seen anything like this before.

Any ideas? I need to get this fixed ASAP as...

Randall Newnham | 11 Nov 2009 | 0 comments

Preface:
Ghost was not designed to work with solid state drives. The recommendations below may or may not work in a given environment, though they have been tested and verified on at least some machines. Please not that before trying this in a production environment, you should try this in a test environment so as to not risk data loss.

Officially, Ghost does not support solid state drives. I have verified that these steps worked on Dell Latitude E4200 machines:

1. Take the image with these command line switches:

-FNI -FFX -NOIDE -NOUSB

2. Restore the image with these command line switches:

-FNI -FFX -NOIDE -NOUSB -NTEXACT

This  has been verified to work. This has only been tested with the same model of machine, so it is not expected that this would work to deploy to different models. I would expect that you could restore a solid state image to an IDE/SATA drive,but not the other way around. Assuming this is...

Randall Newnham | 26 Oct 2009 | 0 comments

There have been network latency issues observed on slower networks with Ghost. These issues can be resolved when booting to a Windows PE boot disk by exiting Ghost, and performing the Release and Renew commands for IPCONFIG, or by editing the START.BAT file at the end of the Ghost Boot Wizard by adding these commands. In the Ghost Console, it is not very clear how to do this. These steps will clarify that:

When Ghost executes a task that requires booting to Windows PE, it executes a file called START.BAT. This file automates the launch of the Ghost client executable, ngctw32.exe. Though not recommended, it is possible to add custom commands to this batch file. Please note that this batch file affects all  tasks that run in a specific build of Windows PE. By default, Ghost has two builds of Windows PE, winpe and winpe-512. It is recommended that you make a copy on the Windows PE build and that you edit the START.BAT associated with only your copy....