I need a script that converts the information provided (given) to a
host via a DHCP server, into "static".

I need to have all the options passed from the DHCP server (IP
address, subnet mask, default gateway, WINS servers, etc.) to be set
statically on the host.

When I initially build a new Windows host it receives all the DHCP
info. One of the build steps stipulates taking the IP address and
other DHCP options and making them static via the TCP/IP Properties
page.

I would like the script to preferrably work on Windows 2000 & 2003,
but would settle for 2003 only.

I think the better answer would be to tell your DHCP server to treat
the MAC address of the PC's NIC as static rather than telling the PC
to hold the information. Of course, that generally means that you
can't do *that* automatically, either, but at least it's a one-to-one
thing in one interface on the DHCP server rather than on a per machine
basis.

However, in most circumstances, DHCP is generally faithful to assign
the same address to the same MAC over and over (the client generally
requests the same address), unless the conditions of DHCP make the
scope near to the quantity of used IP addresses (overlap).

The other issue that needs to be addressed with your request is that
you still need to remove that IP address from being available in your
DHCP scope. This means you still have to make changes on your DHCP
server for every IP address manually assigned. In short, what is the
point of having a DHCP server if you are doing what you are doing?

This is a free comment.

Thank you for the feedback.

After the IP information is statically entered on the host, we
instruct the DHCP server to convert the lease to a reservation. This
does two things: 1) it allows the client to receive the same address
if someone were to accidentally switch the client from static to DHCP.
2) it makes the DNS entry associated with the lease/reservation
static.

Thanks again for your response.

OK, but why bother with the workstation at all? If you're going to
convert the DHCP lease to reservation, then you're done, unless
someone changes the workstation's IP manually to, say, your server's
IP address. Besides which, it'll be a lot easier on you if you happen
to have to change your Gateway Address or DNS servers for whatever
reason.

I realize that you have your reasons and specifications for doing
this, and as such I am not attempting to undermine your process. I'd
actually like to know for my own information as a system administrator
what the security or other benefits are for the changes you are
making.

The process is only applied to servers. The workstations and laptops are all DHCP.

We manage in excess of 2000 servers. Most of the applications depend
on static IP addressing and will balk at a DHCP setting. Security also
dictates that we have static entries on all servers. We don't want
other users changing the address of their workstations or personal
servers to an already reserved address.

Thanks for the feedback!