Discussion Locked

Remote Installation Errors

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have set up my DHCP, DNS and installed and configured my Remote Installation Server. Everytime I go to the client machine and try to boot to the network, I get the DHCP to assign my IP, I get to the point where the program is formatting the client harddrive and I get an error for not enough memory or the installation files are corrupt. I have tried 4 different copies of Windows 2000 Professional and I haven't gotten it to work. Same error, different install. Please help, Thanks, Jeremy

7 replies

by netuser

When you configured RIS, did you authorize the DHCP server through the Active Directory? This is to make the RIS server to respond to client requests and to ensure the DHCP server do not assign client IP addresses.

To authorize, select start/programs/administrative tools/DHCP. In the left pane of the DHCP window, right-click your DHCP server. Then select Authorize from the pop-up menu.

by jeremy the it guy

It's been authorized and the problem is not with the DHCP. I get past the DHCP part and actually start the installation. I have chosen which image to install from, created with RISETUP and once it get's to the formatting of the client drive, I getthe memory error. It says that the computer doesn't have enough memory or the installaion files are corrupt. I know that both of these are wrong. The server has 512 MB and the client has 128 MB. I have tried files from 4 different Win2KPros CDs and I know that isn't the problem either. Thanks for the help but that isn't it. J

by homer simpson instructor at large

are you using oem version or a purchased copy of windows 2000? I had the same problem when we were evaluating the RIS process, and it was all because we were trying to use MSDN copies. this may apply to promo copies from Microsoft..and who knows what all else. I was so ticked, we never bothered to look at it again.

Homer

by jeremy the it guy

Homer,
Nice name by the way. I have used an OEM version and an MSDN version and gotten the same error on both of them. Does this mean that I need a retail version? Please email me at: jwhitlock@starprecision.com with any information you have. That would be a logical reason for the error but it sure is stupid that Microsoft would do something like that. Thanks for the help and if you leave anymore answers. I'm leaving it open for now.

This discussion is closed to new replies.