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

The...

Randall Newnham | 26 Oct 2009 | 4 comments

This is either due to a lack of network drivers, or due to the drive mapping command, net use, executing too early in the boot sequence.

First, you must verify that you have networking capabilities in the boot environment. To do this, boot with your existing Windows PE boot disk , then choose Quit to exit Ghost. At the command prompt, type the following, then click Enter:

ipconfig/all

If an IP address is present, and is not 169.xxx.xxx.xxx, then you have networking capabilities. If this is not the case, you will need to add the appropriate network driver according to these instructions:

How to add drivers to DeployAnywhere or WinPE.

http://service1.symantec.com/support/on-technology.nsf/docid/2008050916132860

If you have networking capabilities but still cannot map a drive, it is likely that the net use command is executing too quickly. To resolve...

4G | 14 Oct 2009 | 4 comments

I am experiencing this problem during imaging on our computer. Any solution?

Date   : Thu Oct 15 12:12:28 2009
Error Number: (29004)
Message: Read sector failure, result = 1, drive = 128, sectors 44919505 to 44919569
Version: 7.00 (Mar 22 2001, Build=245)
License: XQ199905
Command line arguments:
Active Switches :
       Spanning
ProgMode            : PROG_LOCAL
PathName            : \GHOSTERR.TXT
DumpFile            : G:\712N049.GHO
DumpPos             : 1157874587
FlagImplode         : 2
FlagExplode         : 0

Mouse IRQ Status    : Not...

Steven Grove | 29 Sep 2009 | 2 comments

I have just started a new job in a new place with new people. We have a 16 blade HP server to migrate all services to in the neat future. As of now, multiple services are running on the same servers with no (nada, zip, zero) redundancy. They know it, and they have been trying to get it up but DIACAP has taken all their time. I will chronicle my trials and tribulations on my journey to migrate the Console services and images to a new blade.

Marcello D'Angelone | 25 Aug 2009 | 5 comments

The official release of Deployment Solution 6.9 sp3 has now been released.

 
The product is available to download from:
 
 
Release Notes:
 
 Cheers
adtlink | 23 Jun 2009 | 1 comment

We are pleased to announce the release of Deployment Server 6.9 SP3 into the beta cycle. We anticipate the beta cycle to last approximately 5 weeks.

Outlined below are some of the new features for this release:

DAgent

  • Use customdata.ini – The user has the ability to have DAgent report only those NICS which they want. It will filter the NICS depending upon its description and MAC Address.
  • Right-click uninstall - In the Console when user right-clicks on the computer, under Advanced tab and clicks on the “uninstall agent” Dagent will be uninstalled from the client computer. This facility is only provided from the console side.

New OS Support

  • Windows Vista SP2 (x86, x64)
  • Windows 2008 Server SP2 (x86, x64, ia64)
  • Windows 7 (x86, x64)
  • Windows 2008 Server R2 (x64, ia64)
  • VMWare 4.0

We now ship GhostWalker which is part...

Screenbert | 23 Jun 2009 | 1 comment

When working with our core image for Windows 7 I found that restoring an image that has not been syspreped results in a boot error. You can go through the windows repair and let it try to "fix" the issue. Or you can simply use bcdedit to "reset" to boot information. I never had this problem with Windows Vista Images, so it seems to be the new boot manager with Windows 7 that cause this issue. It's probably a good thing to keep unauthorized (and un-sysprepped) images off of your network.

1   ) Restore the Windows 7 image onto the computer
2   ) Boot with the latest version of your Altiris bootdisk.
3   ) Run these commands:
3a ) bcdedit /set {default} device partition=c:
3b ) bcdedit /set {default} osdevice partition=c:
3c ) bcdedit /set {bootmgr} device partition=c: