No.
You don't do that anyway.
The whole point of DHCP is that it doesn't matter what IP# they get.
If it matters what IP# they get,..then don't use DHCP for those particular
machines.
You have to start out with the DHCP Scope using only IP#s that aren't
already assinged. The Scope will encompass the whole subnet range, but will
be limited by Exclusions to only "give out" the currently "unused"
addresses.
Then let's say you have 20 unused addresses. Go and switch the TCP/IP
config of 20 machines to use DHCP. When they get a new address from the
DHCP that will "free up" 20 more addresses that they are no longer using.
Now adjust the Exclusions to "add in" those additional 20 address to what
the Scope is allowed to "give out". Rinse & Repeat the process untill all
the machines you want switched over are done. Of course the larger the
number of addresses you can do at one time, the faster you will get done.
You may be forced to move some "static" machines & devices to a different
static IP# if they are "scattered" around too much. You want your
statically assigned devices grouped so that they fit within a certain range
of addresses to keep it managable,..typically it would be the lower
addresses. If you don't do that it may be nearly impossble to create any
Exclusions that make sense. This all has to be done neatly and
orderly,...if it isn't,...then you need to make it neat and orderly.
Exclusions
Be very careful how you create them. Your Servers and Network Devices
should always be static and never use DHCP. You want a *dedicated*
Exclusion to that range of addesses that probably will never be changed.
Then you need additonal Exclusions that are temporary and constantly being
edited to perform the process I mentioned above. When you are finsihed the
temporary Exclusions will be deleted and only the "dedicated" Exclusions
will remain.
Reservations
These are address for machines where you want the machine to use DHCP, yet
at the same time you want to be sure it always gets the same address. There
should be very *FEW* of these,...they should only be for special
situations,...anything else beyond that you just use Static Addresses and
not use DHCP at all.
Multiple Subnets
Obviously with 3000 machine you will have multiple subnets,..especially
considering that with Ethernet a subnet should never have more than 250-300
hosts (like a /24 subnet) due to the loss effieciency caused by broadcasts.
If you do this project with a single DHCP Server, do not create a
Superscope!
Create distinct separate scopes for each subnet.
Configure your LAN Routers to forward DHCP Queries to the DHCP Server.
That's it.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Jason Williams" <(E-Mail Removed)> wrote in message
news:54f8c4c8-471b-441c-958b-(E-Mail Removed)...
> We are finally going to DHCP setup at my company! This has been
> something that is long overdue.
> However, it will be a daunting task.
>
> We have almost 3000 clients all statically assigned. I know, crazy.
>
> My question is, is it possible to import a list of IP addresses into a
> DHCP server that will be setup in Active Directory?
> Its a long story as to why we need to do this, but it is a temporary
> solution as we move forward. But I do need the ability to importat
> addresses.
>
> I've googled around, but have not found anything, so i was hoping to
> get some help here.
>
> Appreciate it.
>
> JW
Similar Threads
Linear Mode
