Ghostcast Server

[clarky2k3]

I have created a ghost boot disk with the dos drivers for the network card, i then use pc-dos and then burned the iso. I started the ghostcast server to create an image and boot the computer using a the newly created cd. However after booting into the ghost console both peer-to-peer and ghostcasting are greyed out? Any ideas anyone?

[djm968]

The NIC drivers have not loaded becuase Ghost is looking for them on the A: drive?

 

Have you thought about installing RIS and PXE booting the image?

[sahmeepee]

It shouldn't be looking at A: if the paths are relative.. here is one of our config.sys files:

 

DEVICE=\net\protman.dos /I:\net

DEVICE=\net\dis_pkt.dos

DEVICE=\net\E100B.dos

 

Either the NDIS driver you have isn't compatible or it's not being found correctly. Try REMing out ghost.exe from your autoexec.bat so you can see any error messages which appear on screen during bootup.

[clarky2k3]

I would consider using RIS but I have never used RIS before. All our servers are 2003 SP2 and I have installed WDS to give it a go but I just dont know where too start! :oops:

[Sirbendy]

I use ghost 8 and ghostcast...but I do it a different way to the boot disk you describe...

 

http://netbootdisk.com/

 

I used that disk to make a bootable CD that would autodetect/install the networking and whatnot, then copied Ghost to a network share and had the disk connect to that share using a NET USE, and run the ghost.exe.

 

Damn good disk..spots all of our network cards with no hassle at all, and ghostcasts a treat.

 

Bring on the new academy building...we may be able to go RIS/PXE then..

[clarky2k3]

Do you have a sample logon.bat script for connecting to the ghost.exe?

[Sirbendy]

offhand, it's basically:

 

Net use x: \\ghostsrv\user

 

x:

 

ghost

 

"ghostsrv" is a P2 box running "SME Server Linux" (or E-Smith, as I know it). I couldn't connect to a Server2003 box with it, as the boot disk doesn't support server03.

[clarky2k3]

This is my logon.bat dunno if i am doing anything wrong?

@echo off

echo SAMPLE LOGON SCRIPT

echo.

echo *** You'll have to modify this script to suit your network. ***

 

if not %NTFS%==1 goto N

SHOWMENU Loading Read-Only NTFS Support...

REM *** NTFSDOS - EDIT BELOW TO SUIT YOUR LAN, ETC ***

net use x: \\chs-admin-001\Ghost

x:

ghost.exe -rb

REM *** NTFSDOS - EDIT END

:N

 

REM --- EXAMPLE --- Automatically run Ghost from a network share ---

net use x: \\chs-admin-001\Ghost

x:

ghost.exe -rb

REM

REM Note: the -rb = reboot when done

[DMcCoy]

Why map a drive? You can't use multicast then! You should be using the ghostcast server to send your images out.

[Oakie]

If you created a ghost boot disk, maybe go back and make sure you created the one for multicasting ?

 

In the image below, you would need to be sure to choose the SECOND one "Network Boot Package" ....with support for multicasting.

 

http://www.oakdome.com/lab/wp-content/ghost-getting-started-standard-boot-package.jpg

[K.C.Leblanc]

I use ghost 8 and ghostcast...but I do it a different way to the boot disk you describe...

 

http://netbootdisk.com/

 

I used that disk to make a bootable CD that would autodetect/install the networking and whatnot, then copied Ghost to a network share and had the disk connect to that share using a NET USE, and run the ghost.exe.

 

I do the same except I put Ghost on the CD rom. Works really well for me. Although I would use PXE if I was able to use DHCP.