Ghost Solution Suite

 View Only
  • 1.  Symantec Ghost PXE boot

    Posted Nov 20, 2009 09:40 AM
    So I have been working on this issue for multiple hours and still can't get the PXE to work for me.

    I checked out these 3 sites
    service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/e5f5c337ab1999ba882573910082b731
    service1.symantec.com/SUPPORT/on-technology.nsf/docid/2006121815121225
    service1.symantec.com/SUPPORT/on-technology.nsf/docid/2000011211551725



    My protocol.ini has this:
    [protman]
    drivername=PROTMAN$
    [pktdrv]
    drivername=PKTDRV$
    bindings=nic
    intvec=0x60
    chainvec=0x66
    [nic]
    drivername = e100b$
    drivername = TLNK3$
    drivername = TLPN2$
    drivername = ELNK3$
    drivername = EL556$
    drivername = ELPC575$
    drivername = EL59X$
    drivername = TLPC3$
    drivername = EL90X$
    drivername = EL3C574$
    drivername = MHZLAN$
    drivername = EL99X$
    drivername = ACC1200$
    drivername = ethpci$
    drivername = ETHVL$
    drivername = ETHPCI$
    drivername = accnd$
    drivername = EN5251$
    drivername = EN1208$
    drivername = ETHNE$
    drivername = ethne$
    drivername = B44$
    drivername = B57$
    drivername = Elndis.sys$
    drivername = n100$
    drivername = PCIFAT$
    drivername = DEPCA$
    drivername = EWRK3$
    drivername = DC21X4$
    drivername = DE450$
    drivername = DE500$
    drivername = DC21X4$
    drivername = DE305$
    drivername = DE500$
    drivername = DE100$
    drivername = DE150$
    drivername = DE22X$
    drivername = DE400$
    drivername = DE528$
    drivername = DE660$
    drivername = De660p$
    drivername = DFE660$
    drivername = DLKPCI$
    drivername = DLKFET$
    drivername = DLKRTS$
    drivername = DLH5X$
    drivername = DFE650$
    drivername = LMNDIS$
    drivername = DT620$
    drivername = DLKTOK16$
    drivername = HPND2$
    drivername = IMBTRP$
    drivername = ibmfe$
    drivername = epro$
    drivername = e10p$
    drivername = e1000$
    drivername = TE16$
    drivername = tpro$
    drivername = KTC100$
    drivername = KTC110$
    drivername = ktc100$
    drivername = KTC120$
    drivername = LD100AL$
    drivername = LDCDT$
    drivername = kdpcil$
    drivername = Lpc3at$
    drivername = Lpc398$
    drivername = FA31x$
    drivername = FA511$
    drivername = oce1xnd2$
    drivername = EXP16$
    drivername = FL32$
    drivername = oce20nd2$
    drivername = oce4xnd2$
    drivername = oce20nd2$
    drivername = O100$
    drivername = oce4xnd2$
    drivername = oce3xnd2$
    drivername = OLITOK32$
    drivername = olitok$
    drivername = OCT3XND2$
    drivername = FI32$
    drivername = OLITOKP$
    drivername = oce5xnd2$
    drivername = olitok16$
    drivername = oct3xnd2$
    drivername = PNPNDIS$
    drivername = PNPND$
    drivername = PCNTND$
    drivername = PCIND$
    drivername = E9501F$
    drivername = F9702T$
    drivername = FASTNIC$
    drivername = FETND$
    drivername = itsnd$
    drivername = pcind$
    drivername = itsnd$
    drivername = sn2000$
    drivername = PNPND$
    drivername = Smc9000$
    drivername = Nds91c95$
    drivername = CPQREND$
    drivername = Tcctok$
    drivername = TCE32PCW$
    drivername = Cbendis.exe$
    drivername = CBENDIS.exe$
    drivername = Xpsndis.exe$
    drivername = smartnd$
    drivername = Pe3ndis$
    drivername = CE3NDIS.exe$



    -----------------------------------------------------------------------------------------

    This is what my config.sys says

    DEVICE=\net\protman.dos /I:\net
    DEVICE=\net\dis_pkt.dos
    DEVICE=\net\e100b.dos
    DEVICE=\net\TLNK3.dos
    DEVICE=\net\TLPN2.dos
    DEVICE=\net\ELNK3.dos
    DEVICE=\net\EL556.dos
    DEVICE=\net\ELPC575.dos
    DEVICE=\net\EL59X.dos
    DEVICE=\net\TLPC3.dos
    DEVICE=\net\EL90X.dos
    DEVICE=\net\EL3C574.dos
    DEVICE=\net\MHZLAN.dos
    DEVICE=\net\EL99X.dos
    DEVICE=\net\ACC1200.dos
    DEVICE=\net\ethpci.dos
    DEVICE=\net\ETHVL.dos
    DEVICE=\net\ETHPCI.dos
    DEVICE=\net\accnd.dos
    DEVICE=\net\EN5251.dos
    DEVICE=\net\EN1208.dos
    DEVICE=\net\ETHNE.dos
    DEVICE=\net\ethne.dos
    DEVICE=\net\B44.dos
    DEVICE=\net\B57.dos
    DEVICE=\net\Elndis.sys
    DEVICE=\net\n100.dos
    DEVICE=\net\PCIFAT.dos
    DEVICE=\net\DEPCA.dos
    DEVICE=\net\EWRK3.dos
    DEVICE=\net\DC21X4.dos
    DEVICE=\net\DE450.dos
    DEVICE=\net\DE500.dos
    DEVICE=\net\DC21X4.dos
    DEVICE=\net\DE305.dos
    DEVICE=\net\DE500.dos
    DEVICE=\net\DE100.dos
    DEVICE=\net\DE150.dos
    DEVICE=\net\DE22X.dos
    DEVICE=\net\DE400.dos
    DEVICE=\net\DE528.dos
    DEVICE=\net\DE660.dos
    DEVICE=\net\De660p.dos
    DEVICE=\net\DFE660.dos
    DEVICE=\net\DLKPCI.dos
    DEVICE=\net\DLKFET.dos
    DEVICE=\net\DLKRTS.dos
    DEVICE=\net\DLH5X.dos
    DEVICE=\net\DFE650.dos
    DEVICE=\net\LMNDIS.dos
    DEVICE=\net\DT620.dos
    DEVICE=\net\DLKTOK16.dos
    DEVICE=\net\HPND2.dos
    DEVICE=\net\IMBTRP.dos
    DEVICE=\net\ibmfe.dos
    DEVICE=\net\epro.dos
    DEVICE=\net\e10p.dos
    DEVICE=\net\e1000.dos
    DEVICE=\net\TE16.dos
    DEVICE=\net\tpro.dos
    DEVICE=\net\KTC100.dos
    DEVICE=\net\KTC110.dos
    DEVICE=\net\ktc100.dos
    DEVICE=\net\KTC120.dos
    DEVICE=\net\LD100AL.dos
    DEVICE=\net\LDCDT.dos
    DEVICE=\net\kdpcil.dos
    DEVICE=\net\Lpc3at.dos
    DEVICE=\net\Lpc398.dos
    DEVICE=\net\FA31x.dos
    DEVICE=\net\FA511.dos
    DEVICE=\net\oce1xnd2.dos
    DEVICE=\net\EXP16.dos
    DEVICE=\net\FL32.dos
    DEVICE=\net\oce20nd2.dos
    DEVICE=\net\oce4xnd2.dos
    DEVICE=\net\oce20nd2.dos
    DEVICE=\net\O100.dos
    DEVICE=\net\oce4xnd2.dos
    DEVICE=\net\oce3xnd2.dos
    DEVICE=\net\OLITOK32.dos
    DEVICE=\net\olitok.dos
    DEVICE=\net\OCT3XND2.dos
    DEVICE=\net\FI32.dos
    DEVICE=\net\OLITOKP.dos
    DEVICE=\net\oce5xnd2.dos
    DEVICE=\net\olitok16.dos
    DEVICE=\net\oct3xnd2.dos
    DEVICE=\net\PNPNDIS.dos
    DEVICE=\net\PNPND.dos
    DEVICE=\net\PCNTND.dos
    DEVICE=\net\PCIND.dos
    DEVICE=\net\E9501F.dos
    DEVICE=\net\F9702T.dos
    DEVICE=\net\FASTNIC.dos
    DEVICE=\net\FETND.dos
    DEVICE=\net\itsnd.dos
    DEVICE=\net\pcind.dos
    DEVICE=\net\itsnd.dos
    DEVICE=\net\sn2000.dos
    DEVICE=\net\PNPND.dos
    DEVICE=\net\Smc9000.dos
    DEVICE=\net\Nds91c95.dos
    DEVICE=\net\CPQREND.dos
    DEVICE=\net\Tcctok.dos
    DEVICE=\net\TCE32PCW.dos
    DEVICE=\net\Cbendis.exe
    DEVICE=\net\CBENDIS.exe
    DEVICE=\net\Xpsndis.exe
    DEVICE=\net\smartnd.dos
    DEVICE=\net\Pe3ndis.dos
    DEVICE=\net\CE3NDIS.exe
    LASTDRIVE = Z


    ----------------------------------------------------------------------------------------------------------

    I have a VFDboot which contains the following

    autoexec.bat
    command.com
    config.sys
    dis_pkt.dos
    ghost.exe
    himem.sys
    ibmbio.com
    ibmdos.com
    mouse.com
    netbind.com
    pqdotask.bat
    protman.dos
    protman.exe
    protocol.ini
    restrmbr.exe



    I have started the ghostcast server with a image of a computer I took yesterday and I was trying to test by pushing it over the network back to that computer-no success.
    Any ideas on what I am doing incorrectly?




  • 2.  RE: Symantec Ghost PXE boot

    Posted Nov 20, 2009 02:57 PM
    gamingdexter,

    What version of Ghost are you using? Is it Ghost Solution Suite 2.5? If not, you should be entitled to a free upgrade if you have a support contract. The reason I am asking is because I recommend a different PXE setup that is far less complicated and far more reliable utilizing the new version. Here is documentation:

    How to use the 3Com Boot Services (and SolarWinds TFTP) with Symantec Ghost Solution Suite 2.5 using WinPE
    http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2009060307534660

    The reason I am recommending against the Symantec/DeployCenter PXE is that it is only able to deliver DOS-based boot images. Many newer machines have storage controllers too advanced for DOS.

    Thank you,

    Randy