Discussion Locked

Network Client Software

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is something I have been wondering about: I have a workstation that I would like to connect to an NT 4.0 server to begin a remote installation of Win2k Pro. I want to take this workstation with no OS at all (of course the HD will be partitioned) and have it go across the network to get the files. Where do I get the Client network Software? What protocol would I use? And what command? This is for testing and practice purposes.
Thanks, Brad

16 replies

by o/siris

You should check out the TechRepublic article on W2K and Remote Installation Services. It's built into Windows 2000. You can read about it at the following URL: https://www.techrepublic.com/article.jhtml?id=r00220001121jim02.htm

Since you mention it's for practice and testing, are you *sure* that it needs to be a Windows NT 4.0 Server? There's 3rd party software to do this, but no included utilities in NT of which I'm aware.

by bradsayers

Sorry, I wasn't as clear as I could have been. I have the syntax for initiating a remote install. The windows 2000 professional files are already shared on the NT 4 server. I need to know about the *network client software* that would let me takea dead workstation with a partitioned drive across the network to get those files. Once I am able to connect to the share point (with net use I think) I will run the script. Where can I get this network client software to do this? What about a protocol? Or...do I need an actual OS on the workstation to do this? There is a nic in the workstation. Thanks, Brad

by o/siris

I'm afraid I only have generic answers for you. but it's at least worth giving you a place to look. Have you checked out the Windows NT server resource kit? I believe that it includes a Network Client Administrator application that lets you create boot disks that can logon to a Windows NT Domain. It's a fairly simple step from there to map the drive, and run the setup executable.

You can get information on this from a variety of sources within the Microsoft web site, like this one about using non-included drivers for the Administrator application:

http://support.microsoft.com/support/kb/articles/Q142/8/57.asp .

Maybe you can look into the Zero Administration Kit from Microsoft? Check out http://www.microsoft.com/windows/zak for more information.

I don't think that answers your questions, but maybe it points you to where you can find an answer.

by sarsone

You will need to create a dos client boot disk that will connect your PC to the server in dos. The protocol depends on what is loaded on your server and the three options are IP, NWLINK and NETBUEI.

To create a dos boot disk, you can use the client setup software on your NT server @start>programs>admin tools>network client administrator>make network install disk or you can make 2 disks that will help you make a boot disk via the NT 4.0 server cd under clients...disk1 and 2.

However....ifyou let me know the type of net card you have in the PC,....i might have boot disks that i could send you for your NIC. Have a nice collection going!

Dan

by bradsayers

Thanks Dan, Still need some help. I moved the clients folder from the NT CD onto the server and shared it. In clients, I made a Win2k\netlogon share in which I placed the win2k pro source files. Now when I go to net client admin to make the installation startup disk, I only see network client v3.0 for ms dos and windows. Is this enouph? My nic is not listed, but I have the original diskette. How also do I integrate those drivers onto the startup disk I am making?

Hope you can help

by o/siris

To help you out a bit on your last question to Dan, here's an article in the MS Knowledge Base on their support web site.

http://support.microsoft.com/support/kb/articles/Q142/8/57.asp

It tells you how to add drivers to the network boot disk.Should suit your needs.

BTW, the version information in the Client Administrator your using is sufficient(or should be) to let you map the W2K setup share, and to get going with the setup. If you're trying to initiate the setup automatically on startup and login, you can create a user with login script you appear to have placed into the NETLOGON share.

Hope that helps.

R??

by sarsone

even though your card is not listed, you still can pick any card with the same manufacturer and card that is close in comparison to yours and then edit the disk later with the new drivers that you have for your NIC.

But once again, if you would supply me with the make, model and MFG of your NIC in question and the protocol you wish to use....I might already have the boot disk you need and will be glad to email you one!

Dan

by lhollister

Brad, I do this all the time!

First, your client with no OS needs a NIC with a Boot ROM. If your NIC does not have a Boot ROM you can use the Remote Boot Floppy Generator (rbfg.exe) that comes with Win2K. Next, I install 3Com's DynamicAccess Boot Services software (TFTP, BOOTP, PXE, Bootptab file, Boot Image Editor) on the server (Win9x, NT4 or Win2K.)

In a nutshell here's how the process works.
Depending on your network configuration, you select a protocol. BOOTP for static IP, PXE/DHCP for dynamic IP. I'll use PXE as the example. At the server, use the Boot Image Editor to create an image that will contain all the necessary drivers and drive mappings to the Win2K pro Cab files.

Configure your client's Boot ROM to Boot PXE. The client connects to the network, looks for the PXE server, PXE server gets client's IP address from DHCP Server and it looks for an entry in the Bootptab database and to find the image that has been assigned to the client. TFTP then downloads the image to the client and Win2K pro gets installed locally on the client machine.

I have a step by step tech paper describing the entire process using Win98. I can email it to you if you'd like.

For more info on Boot Services software see www.3com.com/managedpc

Lee

This discussion is closed to new replies.