We'll be honest with you. Our preference would be for you to attend one of our Symantec Ghost training courses or have us come to you. However, we realize that time may be a factor and you may need a more immediate answer. Aside from the technical FAQ below, the Symantec Knowledge Base is an excellent source, or you can email us your questions at info@ghosttraining.com.

Open the Ghost Boot Wizard, select the Network Boot Disk, find your NIC in the list, select Modify, and Browse to the new .DOS file. That's generally all there is to it. You can also copy the .DOS file directly to the Templates folder listed above.

Open the Ghost Boot Wizard, select Win PE, browse to the new driver file and select.

If you have not applyed the Live Update for GSS 2.5, do so by going to Console Help then Click on Live Update Menu Item. There were missing drivers that were fixed as a part of the Live Update package. Also, Microsoft Tools msxml6 is required, if you have applied the Live Update but don't have msxml6, Ghost Boot Wizard will let you know to install it

Open the Ghost Boot Wizard, select WinPE, and then click Edit. This will open the WinPE Editor. Highlight the WinPE that you wish to change and select Edit (It is a good idea to make a COPY of the two default WinPEs that are provided to you then edit the copy) Once the WinPE is open, select the Add New Driver... option, name your driver and browse to the location of the driver. Once completed, make sure to Refresh the WinPE image using the option on the WinPE Editor box.

This often happens when canceling an imaging task. If the DOS system is still communicating with the Ghost Console, just send a new task. If there is a valid Windows operating system on the client machine, and you just need to get out of DOS, use the following commands: CTRL-C to stop the DOS client from communicating with the console. Then at the C:\GHOST prompt type in NGCTDOS.EXE -HIDE. The NGCTDOS.EXE file is the Ghost client in DOS which talks to the Console. The -HIDE switch will delete the virtual partition or hide the boot partition, and then reactivate your Windows partition.

The UNDI driver makes use of the networking code contained in the PXE ROM on the NIC to do the date transfer, so if the implementation of the PXE ROM is buggy, then you might experience problems when using UNDI. Also, some machines (BIOS) may not enable the PXI/UNDI ROM unless the computer is booting to PXE, hence the ROM may not be available when the UNDI driver attempts to use it. In the cases where this applies you may need to make a boot device that contains the NIC driver for the NIC that is in the machine as opposed to using the Universal Network Device Interface driver.

Officially, no. It can clone most versions of Microsoft Windows from 95 through XP, as well as many forms of Linux. It is not certified for Server software, although it may work. RAID mirroring may need to be broken first, which defeats the purpose, although hardware RAID systems may fool Symantec Ghost into seeing one physical hard drive. Additionally, some server level software may have trouble because it is associated to the server's Security ID (SID), and when that SID is changed, the application may no longer work.

There could be a number of reasons, but first check your network switches. Ensure that they do not block or limit multicasting, as the Ghost Console uses multicasting just like the DOS functions. Also make certain the speed and duplex settings match on the switches, the Ghost Console machine in Windows, and the client PCs in DOS. All settings must be AutoDetect, for example. Or all must be set to 100/Full. Using a combination will generally result in 10/Half speed. Some 3Com NICs must be hard set on the NIC using a 3Com utility.

Yes, selecting the correct rules for the when creating a Data Template is key. Two rules are necessary. First, Select the $UsersProfile$ variable, then $User Hive$. The order of the rules is important. Also, make certain not to include the $My Documents$ variable with these options, as that is included in the $User Profile$. Using these two rules will migrate a user from one version of Windows to another (Windows 98 as well if User Profiles are setup on 98), and properly convert standard profiles and settings. Other specific data files and folder should be selected after these two rules, or as separate Data Templates

There is not a direct option to include network printers, like the Mapped Network Drive option. However, adding a rule with the $User Hive$ variable to a data template will include network printers. Check that the printer drivers are available in the new operating system. You can also specify the exact registry setting that you want to capture.

Most are fairly direct - $MyDocuments$, for example, will capture the standard My Documents folder from any Windows OS. The $Users$ variable captures just the users - no data and no settings. The $UserProfile$ variable will capture standard user data and settings like My Documents, desktop backgrounds, favorites, etc. The $UserHive$ variable includes mapped network drives, mapped printers, and the like.

Local machine passwords will not be migrated through a Move-the-User task. A local user will have a blank password the first time they login, and be asked to provide a new password before being allowed to continue. Domain users will not have this problem as their password verification comes from the domain, not the client PC itself.

There are a number of issues which can crop up regarding laptops, from multiple NICs due to docking stations, to the standby partition, to Socket Services not being available in DOS if you use a PCMCIA card. Integrated NICs are more likely to work correctly than PCMCIA cards. If Symantec Ghost locks up after the laptop gets its network settings in DOS, try using the '-fni' switch in your ghost.exe command line.