Updated 10/29/03 The most recent issue is the Intel 865 or 875 chipset, available on PCs starting around August, 2003. This chipset is available in Dell, Compaq, and HP machines, at the very least, and has become the standard chipset for business level PCs. The current version of Ghost 7.5 does not work correctly with it. (Ghost 8.0/8.2 does work correctly with the 865/875 chipsets.) If you are still using Symantec Ghost 7.5, you must contact Symantec at 1-800-927-4017, and provide them with your Ghost licensing information. Then you can download the following updated files from Symantec (they are not available here due to licensing agreements): ghost.exe, ghstwalk.exe, and gdisk.exe. At this time (10/29/03) the instructions.txt file you download is not entirely correct. The third step tells you to delete the three files from your client machines. However, the Ghost Console will only update the ghost.exe file, and any tasks performed will fail. You will need to manually update or overwrite all three files on your client machines in the C:\Program Files\Symantec\Ghost directory.

The other issues are the DOS drivers themselves for a variety of network cards. Our experience at Big Bang Training is that 3Com NICs have provided the greatest stability using the drivers automatically available in Ghost 7.5. 

Updated 01/18/05 - If you have an Intel NIC, we suggest you update your drivers with the following files - the new e100b.dos and e1000.dos files available here. A full driver package can be downloaded from Intel, which has all the driver data and updated information about driver compatibility. 

Updated 01/18/05 - The other NICs causing problems at the moment are the Broadcom NetXtreme (b57). Ghost 7.5 did not include any drivers for the Broadcom NICs, but Ghost 8.0/8.2 does. However, some new Broadcom NetXtreme NICs are not compatible with the DOS driver versions included with Ghost (v6.34 and v6.46).  A new version has been released (v7.65), and is available here. Overwrite the b57.dos file in the Boot Wizard, or C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Templates -  b57.dos. You can also check with Broadcom for the lastest NIC DOS drivers.

3: 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.

4: Regarding Sysprep, Windows XP can use any version of the utility designed for XP. However, for Windows 2000, you need a specific version of Sysprep 1.1. There were two versions, and the current one available from Microsoft's web site will not work with Symantec Ghost. This zipped file contains the correct version of Sysprep 1.1 for Windows 2000, as well as a number of samples and explanations. Microsoft Sysprep 1.1 (sysprep.zip) for use with Symantec Ghost. As for using it, make certain that sysprep.exe and sysprep.inf are in the c:\sysprep directory on your Ghost Console machine, then from the Tools Menu, select Sysprep Configurations, and associate the directory and .inf file. Then when capturing (dumping) an image, have the Ghost Console use the Sysprep Configuration by selecting the Sysprep tab, and checking off the appropriate options.

5: 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.

6: There are several possible issues. First, Symantec Ghost 7.5 only works with domain names up to 15 characters. Any name longer than that will not work. Ghost 8.0/8.2 does work correctly with active directory 2000 domains. Next, ensure the Ghost Console is associated to the domain. Select Tools - Supported Domain Lists. If the domain is listed, there is still a possibility the Ghost ID created for the domain does not have the correct rights. Also, make certain the SID is being changed for each client. Also, with an Active Directory domain structure and Ghost 7.5, it may be necessary to remove the client PC from the domain listing (not on the client box, but in AD itself), and then proceed with the cloning task. In Ghost 8.0, the Ghost ID is not always created correctly on Server 2003. You may need to manually create the ID in Active Directory, and then make the association in the Ghost Console using the Supported Domain Lists function.

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

8: 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.

9: 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

10: 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.

11: 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.

12: 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.

13: 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.

Please note, these solutions are not directly supplied by, and may not be supported by, Symantec Corp. Symantec Ghost and Ghost are a registered trademark of Symantec Corp. Windows 98, NT, 2000, and XP are registered trademarks of Microsoft Corp.