DHCP/2K3 Assign Different Scope Options

[ShoKashuki]

Better way to discribe this is:
I would like to create a scope that has reservations in it. The devices that will pickup these reserved addresses need to point to different resources than the other devices in the current scope. Is there a way to force these reserved clients into a second scope that populates TCP/IP settings with slightly different settings.
I was thinking creating a superscope and encapsulating 2 scopes w/different scope options. Will the devices on the network see the superscope as one and follow the reservations defined by one of the scopes? Or will they just pickup the first address and the heck with reservations?

Example:
Network A: 192.168.0.xxx SNM: 255.255.254.0

None reserved machines get:
Gateway: x.x.x.1
DNS: x.x.x.2
ftp: x.x.x.3

Reserved machines get:
Gateway: x.x.x.1
DNS: x.x.x.2
ftp: x.x.x.100

The reserved machines are Wyse Winterm thin clients and pointing them to a differnet ftp server assures they get the right screen for their function.

Thanks

 

[nrg2go]

Client will indeed see the superscope as one. I've never done one with different scope options, but assuming it doesn't complain when you set it up, I must believe it will work as you desire.

 

[aftertaf]

you might be able to do something with the setclassid option.

ipconfig /setclassid

although maight have to be done for all but these thin clients...

Aftertaf
We shall prevail, and they shall not

 

[ShoKashuki]

The superscope is the answer. I setup a test server to check my math and it seem to work out just fine. Saw the superscope as one, and assigned the reserved address w/different scope options to the thin client.
Now I just need to grow the "nads" to implement it into production network.
Thanks