Ghost image and RIS

[khalillo]

Hi all,

I never used ghost with RIS before. I have a 13 GB ghost Image that I need to push to 300 PC within the network. I have created a ghost image , setup a 2003 RIS server, but when I run RISETUP, I browse to the ghost image in the network, I get error message. Am I missing something. This is a project that would make me look like a hero if I get it to work.

Thank you for the help.

[RogueSpear]

Nevermind.

Edited December 17, 2005 by RogueSpear

[InTheWayBoy]

You don't use RIS to push a Ghost image...I believe that's what GhostCast server is for. RIS is to start a remote install of windows...so it would be exactly like if you would be loading it from a CD, only by network. You can customize the install using any of the unattended methods detailed in the forums, but it's intended for fresh installs each time.

You can configure RIS to start WinPE/BartPE, which could in turn start some scripts that would automate the process of pulling a Ghost image over the network. That's not an intended use, but it's definantly viable. A lot of work getting the scripts to work I bet...

[tioaboa]

hi

you can add entries to the RIS menu to call a ghost boot image, and then image a PC. To do this requires Ghost cast server, have a look at the boot disk wizard.

i built a setup like that with W2k3 Server and norton ghost Solution Suite (http://sea.symantec.com/content/product.cfm?productid=9)

see here of a full guide

http://service1.symantec.com/SUPPORT/ghost...m_ghost_suite_1

Regards

Ian

[khalillo]

thanks Ian,

I got the client to boot to Ghost image from RIS except I am running a trial version of ghost, my boss wouldn't buy it.

My new problem is Intel Pro/100 VE: I boot to the image then i get an error that Nic drivers are not in the image.

I upgraded BIOS upgraded NIC drivers, copied .inf .sys files to i386 folder read about every web posting I could put my hands on. NO LUCK.

Any ideas?

thanks

Z

[brainstane]

Do a search on your i386 folder for *.PNF files. Delete them all and then stop/restart the BINL service. Chances are that even tho you updated to the newest pro100 drivers, the .pnf file from the old "bad" pro100 driver still resides in your i386 folder and is causing the problem of the nic not found error. Im assuming your using the latest version of the pro100 driver? Old versions had to have their .inf file edited.

[natan770]

Why bother with Ghost, GhostCast, DOS NIC drivers or BartPE to customize...

I've had the same problem, and I made it using Linux instead.

Get my PING project here => http:///ping.windowsdream.com

Natan

PS: I'm not a heroe. Not even proud. But, hey! it works

http://dvdgen.windowsdream.com -- Burn your own complete and unattended Windows installer on a DVD

http://updater.windowsdream.com -- Auto-update your PC with freeware/opensource

http://ping.windowsdream.com -- Partimage Is Not Ghost

http://www.windowsdream.com -- Corporate homepage.

[khalillo]

Thanks for all the inputs.

I got busy with SMS 2003 deployment, and dropped the RIS for few weeks. I will try Partimage not ghost solution it sounded promissing and it's free.

I will let you know if I have any success with it.

Thanks

[Sonic]

Partimage works great but when I was tried it, it was slow. Post your result.