• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Server 2003 RIS

A

AMD_Gamer

Fully [H]
Joined
Jan 20, 2002
Messages
18,287
i am trying to setup Remote installation services on my server2k3 box but it will not authenticate the DHCP server? i assume that the DHCP server needs to be on a server 2003 machine also not just any old DHCP server on the network?

i really don't want to use server 2003 as my DHCP server as ipcop works fine, any way around this?
 
You'll probably find that this is the way it is because RIS passes certain DHCP parameters to Windows 2003 Server's own DHCP server role, when it's installed. You've currently not got it installed, and so it's unable to pass those parameters that remote clients would use to boot up into the RIS environment using PXE. The easy option would be to install the DHCP Server role in your 2003 server.

Having said that, have a google around and see if you can find what you might need to change\implement in dhcpd on your IPCop firewall box. I'd be surprised if you found that no one has discovered a workaround yet.
 
I'm not that familiar with IPCop's DHCP server, but you'll need some place in the DHCP settings to pass the server ip/boot location of your RIS com file back to the comp you're PXE booting. I think these are 067 and 068 (or something around there, this is off the top of my head), in the Windows DHCP options.

On a side-note, RIS is a dying tech, being phased out by WDS/MDT. If you're going to go through the whole effort of getting a imaging solution up and running, you might want to consider going that route.
 
ok i got it working and deployed an XP machine over the network but i have a few questions,

i made an answer file with setupmgr.exe you can find on the installation cd for the image but it did not have all the networking questions or options you can get with something like nlite,

for example i did not have the option to have it already setup for a certain domain instead of a workgroup? how would i do this?


and how does this RIS stuff work with cd keys needed for each image? do you need to create a unique answer file for each image, there must be a way to do this better?
 
AMD_Gamer said:
and how does this RIS stuff work with cd keys needed for each image? do you need to create a unique answer file for each image, there must be a way to do this better?
Click to expand...

Typically you would deploy with enterprise keys that don't activate..., no?
 
dx2 said:
Typically you would deploy with enterprise keys that don't activate..., no?
Click to expand...

depends on which image he's using to install...

if using an image that requires activation you could always use a generic key that will always let it install, then change it after the fact with jellybean (link)... then activate... otherwise i think you can just leave it out of the answers file and put it in yourself at that step... kind of annoying though when the point is to not have to put in any input until its done
 
AMD_Gamer said:
and how does this RIS stuff work with cd keys needed for each image? do you need to create a unique answer file for each image, there must be a way to do this better?
Click to expand...

It doesn't, you would need a seperate image for each different product key. The Microsoft way of doing it is to get a a single VLK for the OS. The re-imaging rights in the license allows you to do this.
 
Couldn't you use a UDF (uniqueness database file) to specify the key? I'm not sure if you can use UDF files with RIS, but if it you can pass parameters to the setup, you should be able to force it.
 
Keiichi said:
It doesn't, you would need a seperate image for each different product key. The Microsoft way of doing it is to get a a single VLK for the OS. The re-imaging rights in the license allows you to do this.
Click to expand...

i see so you would get a cd key for your company that would be good for certain number machines?


now back to the answer file thing, i take it the setup program is just the basic stuff and if you wanted to do something like have it join a domain from the start you would need to find the answer file and edit it?
 
There are many way to accomplish this in an imaged based (sysprep) install.

If RIS(which doesn't exist anymore post SP2. replaced by WDS) PXE boots to a PE invironment you can write a script to edit the sysprep.inf or you can do it post install. just leave out the domain join in the sysprep.inf

In an imaged based install I would write a vbs script and put it in the startup folder on my image. Once the system comes up and auto logon it would kick the script off. It would connect to a database or read from a csv file on a file share. using the hardware serial number as a lookup i'd have it rename the machine and join the domain.
 
ok i made an image with eh RIPrep program from over the network, it worked great but did some weird stuff i don't get,

after it was done sending the image to the RIS server it does a shutdown, then when i started back up that client it went through some configuration menus like i was installing a new version of windows, it changed the computer name , time zone and all that stuff,

also makes me type in the cd-key?

is that normal? i figured the reference machine would not change, i am just wondering what happened here?
 
You must log in or register to reply here.
Back
Top