Use different lease-times with Windows DHCP server

I try to configure a Windows 2003 DHCP server for a single LAN 192168.1.0/24 such that I can group reservations and say reservations from group A get different options and a different lease time(!) from greservations of group B and different again from non-reservation aliases (i.e. "unknown" MAC addresses), whihc should only be served from a specific range -

This would be very easy with a Linux dhcp server:

subnet netmask {
default-lease-time 300;
max-lease-time 600;
options ....

group {
default-lease-time 86400;
max-lease-time 172800;
options ....
host host1 {  hardware ethernet ....; fixed-address }
host host2 {  hardware ethernet ....; fixed-address  }

group {
default-lease-time 1000000;
max-lease-time 2000000;
options ...
host host3 {  hardware ethernet ....; fixed-address }
host host4 {  hardware ethernet ....; fixed-address  }

Open in new window

But I have trouble figuring out how to do this with Windows.
I could add the group specific options into the individual reservations, but that is not feasible: One would have to repeat several configurazion steps for each new reservation, one could hardly tell if one did something wrong, one would have to touch all reservations in order to change one of those options later.
But even then, I don't see how I can configure different lease-times.

Who can shed some light on this?
LVL 20
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I would add a second LAN segment and use different scopes. You can also use 802.1x port authentication to assign different VLANs to devices based upon whether or not they authenticate. Might be easier to use a Linux DHCP server.

The options can be managed using classes, but not the lease time.
You also can use reservation for your internals clients and a pool for unknow clients.

thehagmanAuthor Commented:
Thanks so far, but it seems I'll have to leave this question still open a bit.
@kevinhsieh Using different (V)LANs for this purpose is not an option unfortunately
@dan_blagut Well, having to run to all clients (as far as they are Windows clients) and perform a local configuration task somehow defeats the purpose of DHCP. And really the lease time is one of my major issues (only a few leases for temporary visitors that should not block other visitors for days and at the same time my "permanent residents" should not have to renew their leases every few minutes)
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

I suggest that if you had a short lease time of 30-60 minutes, your regular would not be adversely impacted by frequent DHCP renewals. Renewing a DHCP address is a pretty trivial task, and it won't slow down your network. The only issue I see is if your DHCP server if offline for a period longer than the half-life of your lease, then you may see clients lose their lease and be unable to get a new one. Re-reading your last post, you could maybe have a lease of 8 hours and still not have your visitors tie up addresses for days. An 8 hour lease would be fine for most production environments.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
a very short DHCP lease will cause more traffic than is ideal, so I'd recommend care before implementing that one.

The only way to have different settings on windows DNS is to use different scopes. The issue is how the server knows which scope to provide to a client in your case. how would you like the sever to classify clients into the correct group?
It's not possible to do this by MAC address in windows.

Most companies have a separate network segment/subnet for different purposes. In addition to having better separation/security between networks this would allow you to have a DHCP scope for each 'subnet' with independent settings and lease times.
A DHCP lease operation is 4 packets. Not a big deal on an Ethernet network.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.