Ghost Recovery Disk CD-ROM/Floppy (GRD 1.4.2)   (Updated 7/6/06) (back to menu)
What is this?
  1. This is a Ghost boot disk (CD or floppy) that automatically detects and loads the proper NIC driver for your PC or laptop. If it doesn't auto-detect the NIC, you can choose to load the correct NIC drivers from the boot disk (provided they're included on the boot disk). Let me know if your NIC is not auto-detected.
  2. After detecting the NIC, MS Client for DOS is loaded and the PC automatically authenticates onto your network. You must edit a file (GRD.PRO) to include a username/password for your network.
  3. After authenticating onto your network, the boot disk runs a batch file (msnet.bat) which maps a drive letter to a share on your Ghost server. You'll need to create a network share on your Ghost server and give read permission to the username/password you created in Step #2. You will also need to modify (msnet.bat) to map a driver letter to the network share and run a batch flie on that share.
  4. Create a batch file on your network share (to be called by the boot disk) that runs Ghost.exe. An example batch file is provided in msnet.bat (at the bottom).
  5. Copy Ghost.exe to your network share.

How to modify/create GRD Floppy Boot Disk
  1. Download the GRD Floppy Image file from the link above and unzip it.
  2. Download and install WinImage. This utility is used to open the GRD.img file. Once you've open the file, extract GRD.PRO (from the ..etc\profile folder).
  3. To extract GRD.PRO, drag and drop it from the WinImage window to your desktop (show me).
  4. Edit GRD.PRO (using notepad) to include the correct username/password to access the network share on your Ghost server.
  5. Copy GRD.PRO back to the GRD image by dragging/dropping from your desktop to the ..etc\profile folder (in WinImage). Click Save.
  6. Next, we'll modify msnet.cab.
  7. In WinImage, extract msnet.cab from the level3 folder. To extract msnet.cab, drag and drop it from the WinImage window to your desktop.
  8. To uncompress msnet.cab, download and install WinRAR. Once WinRaR is installed right-click msnet.cab and click "Extract files" (show me).
  9. A dialog box appears. Set the extraction path to your desktop and click OK. A msnet folder is created on your desktop.
  10. Double-click the msnet folder on your desktop. Double-click the bin folder. Edit msnet.bat in Notepad.
  11. Recall that msnet.bat maps a drive letter to the network share you created on your Ghost server. You should also run a batch file (XP.bat) from your network share which in turn runs Ghost.exe (from your network share). The last few lines in msnet.bat provide an example of a batch file that can be used to choose to install different images. For example, you could choose to install a laptop image or a PC image. Here's the contents of the network share on my Ghost server.
  12. Download Reboot.com, Choice.com, and XP.bat
  13. The last few lines in msnet.bat will look something like this:

    14. NET.EXE USE J: \\YourGhostServer\YourNetworkShare
    J:\XP.bat
    J:
  1. Now that msnet.bat is modified, we need to compress and create msnet.cab.
  2. Download and install ZipItFast Pro to create a CAB file.
  3. Follow these steps to recompress the files in the msnet folder.
  4. Open ZipItFast Pro.
  5. Drag the msnet folder into the ZipItFast window (show me).
  6. The New Archive dialog box appears.
  7. Type msnet.cab in the "File name" field. Set the "Save as type" to CAB (show me). Click Save.
  8. The New Archive dialog box closes and the ZipItFast dialog box appears (show me).
  9. Check Include sub-directories, Cab, and Normal. (show me)
  10. Click ADD to create msnet.cab. Close ZipItFast.
  11. Drag and drop msnet.cab back into the level3 folder (in WinImage). (show me)
  12. Click Yes to inject the file. Click Yes to overwrite. Click Save to save the GRD Floppy image. That's it!
  13. You can now use WinImage to create a Ghost floppy boot disk from your image (Click Disk then Write Disk).

How to modify/create GRD CD-ROM Boot Disk
  1. Follow all the steps listed above to create a Ghost boot floppy image. Copy the image to the root of your hard drive.
  2. Download utlities that are used to create an ISO file.
  3. Extract all utilities to the root of your hard drive and run IMG_to_ISO.bat.
  4. A Ghost boot ISO should be created.
  5. Burn a GRD CD using Nero.
  6. An alternative method is to download the GRD CD-ROM Image (above) and use IsoBuster to extract the image from the ISO. Then, you can use WinImage to extract, etc..


How to Make a USB Memory Key Boot Disk:
For PCs that don't have floppy drives, download this handy utility from Dell.



Download the Latest NIC Drivers for Gateway PCs (7/6/06)
Here's a quick link to all the latest NIC drivers I'm using for Gateway PCs - they work. To use the drivers in the Ghost console, just unzip them and copy the driver folder to your Ghost server to the \\yourGhostServer\c$\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template folder. If the PC already appears in the console, you will need to delete it after you add the NIC driver folder. To verify that the NIC is detected properly, view the PC in the console and look under the DOS template column (show me). If the NIC is not properly detected, double-click the PC icon (in the console), click the Client tab, and check Heartbeat interval (show me). If the NIC is still not detected properly, then there may be another NIC driver template that uses the same Device ID as your NIC. You'll need to either delete that driver template folder or edit mcassist.cfg (in that driver template folder) to remove the Device ID of your NIC.




How to Edit an NTFS image (6/3/04) (back to menu)
Yes, it is possible to edit an NTFS image so that you do not have re-create your image from scratch the next time it needs to be updated.  Also, the image you create using this technique can most likely be deployed to most PCs in your organization. However, it's important to configure your master image correctly. Here's what you'll need:
  • A master image PC. Having an ACPI BIOS helps because this image can then be deployed to other PCs with ACPI BIOSs. Most 350MHz and above PCs have ACPI BIOSs.
  • Sysprep from Microsoft.
  • A small hard drive, preferably 3GB to 5GB. Be sure the hard drive is large enough to hold all your applications. However, the hard drive must not be larger than any hard drive (on a client computer) that will receive the image.
  1. Install the small hard drive on your master image PC (the PC that will be used to create your image).
  2. Install Windows 2000 or XP on this hard drive so that it occupies the entire hard drive. In other words, do not create multiple partitions and try to install the OS to a smaller partition. Capture an image of this drive after you've made all your changes/updates and before you run sysyprep.
  3. Install software, patches, and make the necessary configuration changes.
  4. Capture an image of this PC. We'll call it the pre-sysprep image.
  5. Run sysprep as normal and be sure to the use sysprep.inf that contains the parameter ExtendOemPartition=1. This parameter will expand the 3-5GB image when it is deployed so that it fills the entire hard drive on the PC it's deployed to.
  6. Capture your master image after you run sysprep. This image will be deployed to production PCs.

The next time you have to update your NTFS master image, just deploy your pre-sysprep image to your master PC. Then, repeat steps #3-#6. I've been doing this for a couple years now. And using a smaller drive does not negatively impact the image. A reliable image is created! Of course, the smaller hard drive sure is slow. Enjoy!




Multicasting Best Practices  (12/9/03) (back to menu)
Ghost multicasting is the process by which a single disk image is simultaneously sent to two or more PCs that have each joined a multicast session (originated by your Ghost server).  Multicasting is one of the toughest issues to tackle for many folks (including us).  But, if you can get it to work, you'll save network bandwidth and dramatically speed up your computer rebuild process.  We regularly multicast computers without having any effect on users in the same computer lab.  We're running switched 100MB to our desktops.  I spoke with our network administrators and here's a list of things we've run across that may help you out.  This list will be continually updated as new information is discovered.      

1)  Make sure all your switches are IGMP enabled.  This usually involves logging into your switch via a web browser or connecting to it through a port using a laptop.

2)  Upgrade your switch firmware to the latest version.

3)  The switch with the lowest IP address will always be a member of every IGMP multicast.  Make sure this is a fast switch (perhaps your core switch??) and attach your Ghost server to it.

4)  Only run a single Network Interface Card in your Ghost server.  If you've installed a Gigabit NIC (which is recommended), then remove your original NIC.  If you can't remove the original NIC because it's integrated, then disable it in the BIOS.  Make sure the original NIC does not appear under Device Manager.

5) Have a dedicated Ghost server that isn't running much else.  Our Ghost servers are running Windows 2000 Server.  They a really just desktop PCs with LOTS of RAM.  For example, one of our Ghost servers is a 1.8 GHz E Series PC from Gateway.  It has 1 GB RAM, a standard 40GB IDE hard drive running at 7200rpm, and a Gigabit NIC.  BTW, our Ghost servers are running Symantec Anti-virus 8.0 for Servers.  If you do this too, make sure you keep Symevent updated on your Servers (or just run Live Update from the Ghost console).     

6)  Make sure all your 10MB devices (old computers, HP LaserJet printers, etc.) are attached to IGMP switches, not dumb hubs.

7)  If possible, use the same brand of switches (either HP ProCurve, 3Com, or Cisco) across your LAN.  This will make multicasting much easier.  We continue to experience some multicast issues (leaking IGMP traffic) between our HP ProCurve and 3Com 3300 switches on our main campus.  Our second (newer) campus is composed entirely of HP ProCurve 4000N switches that performs multicasts without any problems.

8)  If you just can't get multicasting to work, try to setup and isolated network with your Ghost server, a single switch, and a couple of PCs.  Then, perform a multicast and see what happens.

9)  More to come!!


Ghost 7.5 clients don't auto-update to Ghost 8.0 correctly   (12/9/03) (back to menu)
Problem: I upgraded my Ghost servers to Ghost 8.0 while my clients continued to use the Ghost 7.5 client.  After initiating a task (from the Ghost 8.0 console), the Ghost 7.5 client files should automatically be updated to version 8.0. before disk imaging is performed.  Unfortunately,  all of the Ghost 7.5 client files on the local are not auto-updated correctly.  Most Ghost 7.5 files were updated to 8.0 versions.  However, VPartition.DLL was not updated to the 8.0 version and thus, my imaging task failed.  Sadly, this error is reproducible on every one of my 1000+ PCs running the Ghost 7.5 client. :-( 

The Task Log:

You're going to see the "Client file missing - copying from server" line every time you perform a re-imaging task on a PC.  The task is copying Ghost.exe from the console to the local PC.

Event Details of "Run Product Upgrade - WARNING":


Event Details of "To Virtual Partition - Failed":


I'm not suggesting that these errors will occur for everyone who upgrades to Ghost 8.0.  However, this is something to watch out for as you test Ghost 8.0.  I'd be interested to know if you have or have not experienced this error.  I'd be even more interested to know why this is occurring.  BTW, I asked a very kind Symantec technician about this and was told that the client auto-upgrade process was heavily tested.  However, I don't remember this feature existing when I beta-tested Ghost 8.0 just before it was release.  I specifically remember being able to use a 7.5 client to perform a disk image with an 8.0 console (who knows, I could be wrong).  Anyway, I asked and there's no way to turn off the client auto-update feature.  Do you know a way to turn it off?

Solution: It seems the best solution is to uninstall the 7.5 client and install the Ghost 8.0 client before performing a task. Ugh!


Ghost 8.0 client installation doesn't create Ghost service   (12/9/03) (back to menu)
Problem: Installation of the Ghost 8.0 client via a logon script failed about 12.5% of the time.  Using the Ghost 8.0 client .MSI file (located at C:\Program Files\Symantec\Ghost\ClientInstall\Client.msi on your Ghost server), I installed the client to a very larger number of PCs (with Local Admin permissions).  Each PC had a copy of the Ghost 7.5 client that was uninstalled before the Ghost 8.0 installation was started.  All installations were reported as "successful" in the event log of each PC.  However, on about 12.5% of the PC, the Symantec Ghost service was not created.  This is definitely something to watch out for as you test the Ghost 8.0 client installation process.  I'd be interested to know if you have experienced this error.

Solution: I think this was caused by a failed Custom Action (namely "installNtDriver") in the Ghost 8.0 MSI file that was used to create the Ghost service.  A potential solution may be to re-engineer the Ghost 8.0 client into your own MSI file.  Another solution may be to use MsiZap to remove the Ghost 7.5 client and then install the Ghost 8.0 client.  This appears to be what the Ghost 8.0 console is doing when it performs a remote 8.0 client installation.  Go to  C:\Program Files\Symantec\Ghost\ClientInstall\MsiZap.Exe on your Ghost server to get MSiZap.


Automatic Reboot or STOP Error after installing Ghost 8.0 client  
(12/9/03) (back to menu)
Problem: After installing the Ghost 8.0 client, my PC automatically reboots or displays a STOP Error (shown below) whenever I attempt to browser the contents of a Zip disk.

STOP Error:
No_More_IRP_Stack_Locations
STOP 0x00000035 (0xFFB756D0, 0X00000000, 0X00000000, 0X00000000)

Solution: This problem occurred (for me) because we had Symantec Anti-Virus 8.0 installed on every PC.  In fact, this problem will occur if you're running SAV 8.0 or lower.  This problem will not occur if you're running  SAV 8.1.  The solution provided to me by Jay Hicks at Symantec was to upgrade to the newest version of Symevent.  Symevent is Symantec's hook for getting it's products to run nicely when they're installed on the same PC.  Thanks Jay!

Download Symevent from Symantec's website
To install Symevent, run sevinst.exe -navnt -q

Go here for more info about Symevent

Symevent does not add an entry under Add/Remove Programs, so here's some VBScript for installing it via a logon script. Notice that you must reboot the PC after installing sevinst.exe in order to get the fix to work.

'Install Symevent for Ghost 8.0/SAV 8.0 Zip Disk Reboot Fix
FileName = "C:\Program Files\Common Files\Symantec Shared\SevInst.Exe"
FileVersion = FSO.GetFileVersion(FileName)
If FileVersion <> "11.3.0.22" Then
  ShellObj.Run "\\your server path\sevinst.exe -navnt -q",1, True
  ShellObj.Run "\\your server path\PowerOff.exe reboot -warn -warntime 5 -msg ""A critical application patch has been installed. Please wait while your PC is restarted. Thank you for your patience!\n \n Gainesville State College - Leading the Way!"" -force -use_nt -nocancel",1,True
  WScript.Quit
End If

Another potential solution could be to search the registry for IRPStackSize.  If an entry was found, try deleting it (after backing it up, of course).


Ghosting Freezes on DELL GX270 with Intel PRO 1000 MT NIC  
(12/9/03) (back to menu)
Special thanks to Keith B. Schevling for bringing this to my attention.  The newest Intel Pro 1000 e1000.dos driver from Intel (used by all hacks on this website) may not Ghost correctly on a Dell GX270.  Keith's solution was to download a driver from the Dell Site. This driver (e1000.dos) has an older date than the one from Intel, but is larger in size.

Download e1000.dos (date 3/9/2003, 51,264 bytes) (Alternate download directly from Dell)
Here's some tips from Keith on getting it to work.

e1000.dos from Intel Website (date 8/8/2003, 50,624 bytes) - This is driver that I built into GRD 1.2 and the Ghost console Intel Pro 1000 upgrade.

Please continue to keep me on my toes when it comes to upgrading NIC drivers - other folks will appreciate it.  We don't have any Dell PCs around here. Thanks!


Upgrading to Symantec Ghost 8.0 - Tips and Hacks   (12/9/03) (back to menu)
Our Environment: We're running Ghost 7.5 Corporate Edition on two Windows 2000 servers (one on each campus).

Upgrading Experiences: The upgrade from Ghost 7.5 to Ghost 8.0 failed in the same manner on each W2K Server. Everything seemed to go well during the installation.  The 8.0 installation seemed to automatically uninstall Ghost 7.5 then backup the Ghost database information (located at C:\Program Files\Symantec\Ghost\db) to C:\Program Files\Symantec\Ghost\Version 7.5 Database Backup.  However, towards the end of the Ghost 8.0 installation, I received the following Windows Installer pop-up error message.  This happened during the 8.0 upgrade on both servers. 

"There was an error installing Symantec Ghost configuration service."

This error meant that the Ghost 8.0 installation process could not create the following services:
Symantec Ghost Configuration Server Service
Symantec Ghost Database Service

As you know, you can't even launch the Ghost console without those services running!  I'm guessing that a custom action in the Ghost 8.0 .msi package failed to create the services because a reboot was needed (after removing those services during the Ghost 7.5 uninstall process).  I've done my fair share of application re-packaging and most .msi custom actions are set to run during the last part of the installation process.

What I Tried to Solve the Problem on Ghost Server #1:
1) I rebooted the server and performed a repair of the Ghost 8.0 installation (through Add/Remove Software). It didn't work - the two missing  Ghost services weren't created.

2) I tried to initiate a full repair using .msi command line switches and that didn't work either!

3) I uninstalled Ghost 8.0, rebooted the Server, and performed a fresh install of Ghost 8.0.  This turned out to be a VERY STUPID thing to do (if I didn't have a backup of my Ghost database).  The installation worked flawlessly and the two Ghost services were created.  However, all my Computers, Tasks, Configurations, etc. were gone.  To make matters worse, I tried to copy the database backup I had made into the C:\Program Files\Symantec\Ghost\db folder.  After doing this, the Ghost 8.0 console wouldn't even load.  Oh baby...  

4) After a quick scan of Monster.com (just kidding Rick and Brandon), I decided to export the registry entries that Ghost 8.0 made to create the services during the fresh, successful install.  I failed to mention, that I had performed a snapshot of my W2K Server prior to and after the fresh, successful installation of Ghost 8.0.  Now I knew what Ghost 8.0 was failing to do.

5) I uninstalled Ghost 8.0, rebooted, and then installed Ghost 7.5. After copying over the backup of the database files I'd made, Ghost 7.5 was happy. Everything was back to normal.

6) I performed the upgrade to Ghost 8.0 and Ghost failed to create the two services again.  I ran the registry entry and presto - Ghost 8.0 worked fine - the two services were created!  And all my computer, tasks, configurations, etc. were present.

7) As previously stated, Ghost Server #2 had failed the upgrade to 8.0.  The two services were not created. I ran the registry entry and presto - Ghost 8.0 worked fine on Server #2!

Solution:
If you have this problem, download and run (double-click) this registry entry on your Windows 2000 Server.  I'm pretty sure that the registry entry would work on Windows 2003 Server, too.  Please let me know if you've experienced this problem and if this solution worked for you.

Best Practices for upgrading to Ghost 8.0:
1) Do the upgrade when you have plenty of time to troubleshoot and solve problems.

2) Make a backup (copy & paste them to another folder on your Server) of the following folders.

C:\Documents and Settings\All Users\Application Data\Symantec\Ghost
C:\Program Files\Symantec\Ghost  (don't forget to stop the Ghost services before copying this one!)

3) If you've created new NIC templates for the Intel Pro 100 or Intel Pro 1000 in Ghost 7.5 that replaced the old broken templates in Ghost 7.5, then MOVE the folders (listed below) AFTER upgrading to Ghost 8.0 and BEFORE you open the Ghost 8.0 console.  Again, move these folders (that were created by Ghost 8.0) out of the C:\Documents and Settings area.

C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\IBM EtherExpress PRO 100
C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\IBM EtherJet 10-100 PCI
C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Intel PRO 100
C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Intel PRO 1000

If you don't move these 4 new Ghost 8.0 NIC template folders, then your Ghost clients (that have Intel Pro 100 & 1000 NICs) will auto-detect these new templates and ghosting won't work because the Intel Pro templates you added (when you were using Ghost 7.5) are still there!  I experienced this problem and had to manually set each client to use my Intel Pro templates after I opened the Ghost 8.0 console and all the PCs auto-detected the new Ghost 8.0 NIC templates.  Don't be thrown off by the dates on Ghost 8.0's E100b.dos and E1000.dos files, look at the file size when comparing them to your Intel Pro NIC files.  The bigger the file size, the newer the driver (in this case).

4) Consider copying PnP IDs from mcassist.cfg files in Ghost 8.0 for the Intel Pro NICs to your mcassist.cfg files for the Intel Pro NICs.

5) Read about my troubles and experiences with the Ghost 8.0 client before you upgrade to Ghost 8.0.


Ghost Network Boot CD-ROM   (Updated 11/21/03) (back to menu)
Problem: The Ghost 8.0 doesn't fit onto a single floppy and I don't  want to have to map drives.  I want to be able to use the Multicast features of Ghost.

Solution: Special thanks to Neil B. Riser from SAIC/Sandia National Laboratories for sending this in!  Neil modified Bart's Modboot with permission.  Thanks again Bart!

Download Neil's Ghost Network Boot CD-ROM image. (updated 11/21/03)

** Make sure you copy your version of Ghost.exe, Gdisk.exe, Ghstwalk.exe, etc. to the CD-ROM.  All edits can be performed using the same techniques described in the section entitled "High-Capacity Ghost Network Boot Disk (GRD 1.2)".   

What it does:
- It's a CD-ROM bootable version of Bart's Modboot
- It can access Ghost on a CD-ROM, rather than mapping drives. But it can map drives if you wish.
- It can perform Ghost Multicasts.
- The CD-ROM drive letter is entered into the path statement automatically.

How he made it:
- Left aspi8.cab and aspi8u2.cab for scsi drivers
- Left b44.cab, b57.cab, e1000.cab, e100b.cab, el3c574.cab, el59x.cab, el90x.cab, elpc3.cab, elpc575.cab, pcntnd.cab for network drivers.
- Auto selected everything  in the autopilot.pro. DHCP is enabled.
- Uses the autexec.net to execute the multicast to let people know that they can use "net logon" and map drives.


Ghost Tasks don't run correctly on Gateway E4100 PC   (10/7/03) (back to menu)
Problem: Run a Ghost task on a Gateway E4100 PC and the PC never reboots into the Ghost partition. The Ghost task does run and then the PC does nothing.  After rebooting the PC manually, the Ghost task fails in the Console.

Ghost Console Failure Message: "To Virtual Partition - Failed" (Details: Failed to reboot client to recovery partition).

Why did this happen?: PCs have Zip drives that share the Primary IDE cable with the hard drive. The hard drive was on the connector closest to the motherboard. The Zip drive was attached to the connector on the end. Both the hard drive and Zip drive were set to Cable Select.  As a result, the Zip drive was set as Master and the hard drive was set as Slave. Ghost cannot reboot the PC (after a task is executed) if the hard drive is set to Slave.   

Solution: Choose your favorite. 1)Re-connect IDE ribbon so hard drive is on the end connector and the Zip drive is attached to the connector closest to the motherboard. --- OR--- 2)Set jumper on hard drive to Master and remove jumper on Zip drive (removing the jumper sets it to Slave).  If you've experienced this problem, please call Gateway and let them know immediately. The more folks who call, the quicker the problem will be resolved.

This problem does not occur when tested with Symantec Ghost 8.0 beta. Gateway has been contacted about this problem and they are investigating it. See the Symantec Ghost knowledgebase article: Error: "...to virtual partition failed" or "Unable to defragment..." when running a Task.


How to Perform an Unattended Installation of Ghost 8.0 Client via a Logon Script, SMS, or Group Policy in Active Directory   (12/27/03) (back to menu)
Problem: The nice folks at Symantec did a great job of packaging the Ghost 8.0 client into a single Windows Installer package (.msi file). Unfortunately, there's no way to perform an automated, unattended installation (unless you do a push install from the console).

Solution: Download the Windows Installer Transform File (see below) and apply it to the .msi package (Client.msi) that is found on your Symantec Ghost 8.0 Console PC. You'll need to find and copy Client.msi from your Ghost server to a network share, etc. To do this, select "show all files" on your Ghost 8.0 PC and perform a search.

Download the Windows Installer Transform File (Unattended.mst)
Please note: By downloading this transform, you agree to Symantec's software licensing agreement for using Symantec Ghost 8.0.   Also, Symantec does not provide support for packages that have been modified in any form.

For a silent install of Ghost Client, Symantec will only supported the following msi command line method.
Msiexec /i "<path to msi package>\client.msi" /qw

What it does: Unattended.mst does not modify Ghost.msi - not a single byte. It is intended to promote the use and adoption of Symantec Ghost 8.0.  It hides most of the end user screens (except for the progress and installation failed dialogs) where you'd normally have to click "Next", etc.. It also leaves the name of the Ghost console server blank. So, after the client is installed, the local PC will automatically search for and locate the closest Ghost console server.  

For an Unattended Install and Automatic Reboot:
msiexec /i path_to_Client.msi Transforms=Unattended.mst REBOOTPROMPT=Suppress /qb!

Suppressing the Reboot prompt makes Client.msi automatically rebbot the PC. The /qb! switch removes the "Cancel" button during the client installation process.

For an Unattended install and No Reboot (I recommend using this one):
msiexec /i path_to_Client.msi Transforms=Unattended.mst REBOOT=ReallySuppress /qb!



How to Retain the ComputerName after Ghosting   (9/4/03) (back to menu)
I've received many emails from folks who would like to find a way to keep the same ComputerName after using Ghost to upgrade or just rebuild a computer.  I'm sure there are plenty of way to do this.  Here's step-by-step instructions  that uses the Ghost Console, a Configuration Template, and the Ghost Client to retain the ComputerName.

  1. Install the Ghost client onto a PC that you plan to rebuild or perhaps upgrade (from Win98 to XP, for example).  I'd recommend that you use the Symantec Ghost CD-ROM or create your own automated  installation package.  It will also help (in the future), if you install the Ghost client onto your master image PC before performing an image dump. This way, all your PCs will automatically have the Ghost client installed after they get imaged.
  2. Check the Ghost console (look under "Machine Groups" -> "Default") to make sure the PC (that you installed the Ghost client on) is showing up with the correct ComputerName.  On your 2000/XP client, make sure File and Printer Sharing is installed (it is installed by default). Otherwise, the ComputerName will not be displayed (only the MAC address will). If this makes you feel uneasy, then you can safely disable the Server and Computer Browser services.
  3. In the Ghost console, create a new configuration template. Do this by clicking "Configuration Resources" then "Configurations".  In the right-hand window, right-click and choose "New Configuration". Call it whatever you like.  We called ours WinXP. Be sure to check the "Allow template settings" box (so we can use this template in a task).
  4. Optional - Enter a username. If this is done, then the PC will display this username after it is ghosted.
  5. Under "Identification", do not check "Apply Computer name:" or "Apply Computer Description:". Un-checking the "Apply Computer name:" is actually what causes the ComputerName to be retained.  If you wish, check "Apply member of" and enter a value for your domain (if your users are logging into a domain). This can also allow you to use Ghost to create a computer account in Active Directory, if needed.  Although, I'd recommend using sysprep.inf to create a computer account.
  6. Under "TCP/IP Settings", check whatever you use to obtain an IP address, Most folks may use DHCP.
  7. Click "OK" to save the configuration template.
  8. Next, add the configuration template to a Ghost task.  Be sure to check "Use Default Settings" so the ComputerName is retained. That 's it!
  9. Optional - Setting the PC to Autologon. Use a Ghost Ai Package to push in a specific username, password, domain, etc. so the PC will automatically logon to the domain. The Ai package will run after the PC is imaged and after the mini-setup wizard is run (by sysprep). We used this to force an autologon to our domain so our logon scripts would run and install applications. We also used a "SITE" environment variable to identify the PC as one of "our" Windows XP PCs. Our logon scripts, etc. are configured to only run if SITE=GC.


Ghost.exe Freezes on a new PC   (7/17/03) (back to menu)
In the past, I've received many emails from folks who are having problems running Ghost.exe on new PCs.  After running Ghost.exe, the PC freezes or the screen just goes black. 

Folks have experienced this problem on PCs that have the new Intel chipset (I don't know the #) that supports Serial ATA connections (look for a serial ATA connection on your motherboard).  The Dell Optiplex 270 and Gateway E-4100 series PCs seem to both have this problem - thanks Intel!  BTW, you don't have to be using the serial ATA hard drive/connection in order to experience this problem.  The solution is to use the -fni switch when you run Ghost.exe.

Ghost.exe -fni

The -fni switch "Disables direct IDE access support." (Ghost.exe Switches: Alphabetical list of switches). This is a temporary fix but it works! You can add this switch to the Ghost console under a given task. Or, just add it to your Ghost boot disks. 

A better solution

Many thanks to Douglas Wells from Binary Research International Inc. for providing the following very useful information:

"The Intel chipsets that don't work are the Intel 865, per Symantec.  Customers can call Symantec, have their license certificate ready, and Symantec will provide them with a link/URL to download updated GHOST.EXE, GDISK.EXE, and GHSTWALK.EXE's that will work and hopefully overcome the problem with the Intel 865 chipset/Intel Pro 1000 combination."



 
 


How to Determine the PnP DeviceID for a NIC   (7/16/03) (back to menu)
Many folks have emailed to ask how they can find the DeviceID of their NIC (network interface card).  Unfortunately, it's not a very clear process. And it's hard to explain in an email. :-) Basically, it involves looking in the registry of a computer that already has the NIC installed.  Rather than go into a long explanation that will most likely be unclear, I have created a script that you can use to determine the PnP DeviceID of your NIC. Please keep in mind that this script should be run on a computer that has the NIC installed.

Download ---- WMI/VBScript for Finding PnP DeviceID - Version 1.0 -7/16/03

The script will also write out a text file (C:\Program Files\DeviceID.txt) that contains this info. It's also important to mention that a single NIC (for example, the Intel Pro 100) can and will have many different DeviceIDs.  Why?  There are two parts to the PnP DeviceID, the Vendor part and the Device part.  While the Vendor portion typically remains the same, the Device portion will change - depending on when the NIC was manufactured.  So, be sure that you run this script on a few PCs.



Add support for Intel Pro 100 NIC to Ghost 7.5 Console   (8/20/03) (back to menu)
  1. Download and uncompress the Intel Pro 100 VE NIC drivers
  2. Goto your Ghost server create a folder called "Intel Pro 100 VE" (without quotes) in the following directory: \\YourGhostServer\C$\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template.  If you had created a folder with this name in the past, move the folder out of the "Template" directory onto your desktop (or whatever).
  3. Copy the 3 files that you downloaded in Step #1 (e100b.dos, mcassist.cfg, protocol.ini) to the "Intel Pro 100 VE" folder.
  4. Delete any Ghost clients (that are not auto-detecting a NIC driver) from the Machine Group area of the Ghost console. The clients should reappear and hopefully will automatically default to the "Intel Pro 100 VE" NIC template.
  5. If they don't, then your Intel Pro 100 VE NIC may have a different DeviceID.  Use my DeviceID utility (see above) to determine the DeviceID of the NIC and add it to mcassist.cfg. And, if you let me know of any new DeviceIDs out there, I'll stick it on this site for others to benefit from.

The mcassist.cfg file that you downloaded should look like:

# This file is used by the Ghost Boot Wizard.
# You should not attempt to edit this file yourself
DRIVER-TYPE = NDIS
DRIVER-NAME = E100B.DOS
NDIS-NAME = E100B$
RECEIVE-MODE = 0
TIMESTAMP = 1020122452
PCI-TAG = 8086 1039 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1050 : Intel(R) PRO/100 VE Network Connection$

Where 8086 1050 is the DeviceID of the newest Intel Pro 100 NIC (to the best of my knowledge).

Troubleshooting:

  • After you update the Intel Pro 100 drivers and perform a Ghost task on a PC with a new Intel Pro NIC, it may fail because the drivers in the Ghost DOS partition (on the local PC) were not updated.  If this happens, perform a second Ghost task on the same PC.
  • In some situations, checking the "Heartbeat Interval" checkbox on the CLIENT tab of the computer (under Machine Groups) seems to make things work.
  • If your Ghost DOS partition on the local PC uses PCDOS, try switching it to MSDOS (and vice versa).
  • If all else fails, try another PC that has the new Intel Pro 100 NIC.

The Ghost document entitled (How to manually add a NIC to the MultiCard Template) may also help you!  Remember, once you build support for the new Intel Pro 100 NIC into the Ghost console, you can then create a Ghost Boot disk or a Ghost Network Boot disk that'll support the new NIC!!


Add support for Intel Pro 1000 NIC to Ghost 7.5 Console   (10/7/03) (back to menu)
  1. Download and uncompress the Intel Pro 1000 VE NIC drivers
  2. Goto your Ghost server create a folder called "Intel Pro 1000 (updated)" (without quotes) in the following directory: \\YourGhostServer\C$\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template.  If you had created a folder with this name in the past, move the folder out of the "Template" directory onto your desktop (or whatever).
  3. Copy the 3 files that you downloaded in Step #1 (e1000.dos, mcassist.cfg, protocol.ini) to the "Intel Pro 1000 (updated)" folder.
  4. Delete any Ghost clients (that are not auto-detecting a NIC driver) from the Machine Group area of the Ghost console. The clients should reappear and hopefully will automatically default to the "Intel Pro 1000 (updated)" NIC template.
  5. If they don't, then your Intel Pro 1000 NIC may have a different DeviceID.  Use my DeviceID utility (see above) to determine the DeviceID of the NIC and add it to mcassist.cfg. And, if you let me know of any new DeviceIDs out there, I'll stick it on this site for others to benefit from.

The mcassist.cfg file that you downloaded should look like:

# This file is used by the Ghost Boot Wizard.
# You should not attempt to edit this file yourself
DRIVER-TYPE = NDIS
DRIVER-NAME = e1000.dos
NDIS-NAME = E1000$
RECEIVE-MODE = 0
TIMESTAMP = 997607674
PCI-TAG = 8086 100E : Intel(R) PRO/1000 MT Network Connection$
PCI-TAG = 8086 1019 : Intel(R) PRO/1000 MT Network Connection$

Where 8086 1019 is the DeviceID of the newest Intel Pro 1000 NIC (to the best of my knowledge).

Troubleshooting:

  • After you update the Intel Pro 1000 drivers and perform a Ghost task on a PC with a new Intel Pro NIC, it may fail because the drivers in the Ghost DOS partition (on the local PC) were not updated.  If this happens, perform a second Ghost task on the same PC.
  • In some situations, checking the "Heartbeat Interval" checkbox on the CLIENT tab of the computer (under Machine Groups) seems to make things work.
  • If your Ghost DOS partition on the local PC uses PCDOS, try switching it to MSDOS (and vice versa).
  • If all else fails, try another PC that has the new Intel Pro 1000 NIC.

The Ghost document entitled (How to manually add a NIC to the MultiCard Template) may also help you!  Remember, once you build support for the new Intel Pro 1000 NIC into the Ghost console, you can then create a Ghost Boot disk or a Ghost Network Boot disk that'll support the new NIC!!


Add support for SMC 1211TX NIC to Ghost 7.5 Console   (12/22/02) (back to menu)
  • I simplified the process for ya!
  • Download the SMC 1211 TX files
  • Goto your Ghost server create a folder called "SMC 1211TX" (without quotes) in the following directory: \\YourGhostServer\C$\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template
  • Copy the 3 files (SMC1211.dos, mcassist.cfg, protocol.ini) to the "SMC 1211TX" folder.
  • Delete the Ghost clients (with the SMC 1211TX NICs) from the Machine Group area of the Ghost console. The clients should reappear and hopefully will automatically default to the "Intel Pro 1000 (updated)" template.
  • If they don't, then you may have to check the Heartbeat Interval checkbox on each SMC 1211TX client.
  • If this still doesn't work, then email me.  The PnP ID of your SMC 1211TX NICs may be different from the one I listed in mcassist.cfg.




FastCounter by bCentral