• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Install Windows XP thru network, is it possible?

C

Charles

Platinum Member
Do I need a network bootable machine to do this?

FYI, I have a home LAN server with no monitor and CD-ROM.
 
The best (and possibly only) way of installing XP off a network is to use Remote Installation Services (RIS) which is built into windows 2000 server. This allows PXE compliant computers to boot off the network and install an OS.

You need a PXE compliant client (most 3-com and Intel cards will boot if asked nicely enough although some might need a floppy with the drivers on) and a server running DHCP and ADS to have a chance of making it work. It's a bitch to set up but great once running.

Apologies for the acronyms and good luck.

That said, I've just rembered that the latest version of Imagecast (and possibly ghost as well) will run a PXE server allowing clients to network boot. The only thing there is that you'd have to create an image first, and I'm not sure if Sysprep (prepares windows 2000 for image rollout) supports XP....
 
You don't need to install RIS. Infact, I would recommend you dont. It requires a lengthy setup and native DHCP DNS and AD (as stated above).
What I would consider doing, is copying the i386 directory to a share on your network, build a network boot disk ( this can be tricky if you've never done it before, but it's not impossible) Check here for some downloadable ones. You will have to modify them of course.

Once you have the bootdisk set-up properly, it is possible to boot the client, have it connect to the i386 share, and then run set-up. In a small scale situation, this is the scenario I recommend. RIS is rarely useful save for large scale operations, due to the requirements and time required. Also, it's NIC driver support is very limited, and adding in your own drivers is difficult enough to annoy a mortal.
 


<< What I would consider doing, is copying the i386 directory to a share on your network, build a network boot disk ( this can be tricky if you've never done it before, but it's not impossible) Check here for some downloadable ones. You will have to modify them of course. Once you have the bootdisk set-up properly, it is possible to boot the client, have it connect to the i386 share, and then run set-up. >>

This is actually what I've been thinking to do. thanks for the tips man. I'm browsing bootdisk.com.
 
Bootdisk.com is awesome. That's how I install now. Only downside is that I only have one NIC (intel) that works with it correctly. The other ones are Realtek crap and never could get them to work. So, wehenver I reinstall a machine, I just use my network Boot NIC. Works Great, and it's fast.

PS.

MAKE SURE YOU RUN SMARTDRV.EXE if you're going to install over a network drive. Makes a big big difference in performance.
 
If you can get a copy of the OPK or oem preinstallation kit it should be easy. Of course getting the kit is another thing. In fact if you can find one please lmk where you got it as I only have a RC version.


But yes it can be done.
 
I must admit I'm speaking as a guy who already had 2K Server, ADS, DHCP and DNS running the last time I wanted to remotely install a PC, so RIS was fairly easy to get going.

I hadn't considered installing off a network share, I'll have to give it a go at some point.

RIS is useful because you can make installations completely automatic, so everything from installed printers to desktop resolution can be pre-configured. Which is very useful in an enterprise environment. But as Saltin says, overkill for the home. Which has never stopped me before 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top