Ghost Solution Suite

 View Only
  • 1.  additional network cards for Ghost Cast Server 8.2

    Posted Jun 11, 2007 04:15 PM
    Are there additional network card configurations available for Ghost Cast Server 8.2 beyond those included with the original program installation?
     
    I have some servers that have onboard gigabit NICs that are not being recognized by GCS.  I would rather not have to open the servers to install a PCI network card to create images with GCS.  When I boot my server with a ghost boot disk set with the NIC driver I get a message about no PCI NIC available. 
     
    Regards,
    Todd


  • 2.  RE: additional network cards for Ghost Cast Server 8.2

    Posted Jun 12, 2007 02:14 PM
    Sounds like you don't have the right NIC drivers on your Boot disk. See if you can download a Packet or NDIS2 driver from the NICs manufactors website and add that to the list of network drivers in the Ghost Boot Wizard.


  • 3.  RE: additional network cards for Ghost Cast Server 8.2

    Posted Jun 12, 2007 03:24 PM
    This is where the templates are for ghost console 8.2 and gss 2.0:
     
    C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template
     
    Grab a folder in there, say the first one 3com3c59x and copy the whole thing so you end up with a new folder "Copy of .....".
    Rename the folder to whatever nic adapter you are trying to add.  remove the protocol.ini and .DOS file in there and put in the ones that you download for the new NIC you are adding.  Look in that protocol.ini you added and make sure you have these parameters:
     
    [protman]
    drivername=PROTMAN$
    [pktdrv]
    drivername=PKTDRV$
    bindings=nic
    intvec=0x60
    chainvec=0x66
     
    there can be extranious information in those categories just make sure the above is there.  In other words, if there is already a [pktdrv] heading just make sure what is above is reflected in the file.
     
    Finally open the mcassist.cfg. 
     
    In the

    "NDIS-NAME =  "replace what is there with what you find in the protocol.ini "drivername = ..." section of the protocol.ini.

    "DRIVER-NAME = " is your .DOS file name

     

    The PCI-TAG section is what is most important.  Clear out all the values that are there except one so you can copy it (be sure to get rid of the one you save when you are done editting).

    Now you need the PCI-IDENTIFIER string of your nic.  An easy way to get it is to go to your Computer Manger then Device Manager.  Look for your Network card under Network Adapters and double click on it.  Next click on the details tab and the value box contains the PCI Identifier string. 

    For example:  PCI\VEN1022&DEV_2000&SUBSYS........"  All you need is that first part.  the number after VEN is your manufacturer code and the number after DEV is your model basically.


    So we take the below and modify it:

    PCI-TAG = 10B7 5900 : 3Com Etherlink III Bus-Master PCI Ethernet Adapter$

    modified:

    PCI-TAG = 1022 2000 : AMD PCNET Family PCI Ethernet Adapter

    You can add all the PCI identifiers you know of for that model. 
     
    Once you have made those mods, you can use that template in the console boot wizard.
     
    ALTERNATIVELY... if you just want to update a NIC driver because your new computer won't use the old driver ghost sent you... then just add the correct PCI-Identifier string per the directions above and update the .DOS file in your template folder.
     
    I have noted when I add a PCI- Identifier string or new nic that the first computer to join the console with that adapter I have to manually set to that template.  Every subsequent client that joins of that type is detected automatically.

    Message Edited by David.Poprik on 06-12-200712:26 PM