Good to know! Thanks for sharing this. Dave
From: [email protected] [mailto:[email protected]] On Behalf Of Graeme Carstairs Sent: Tuesday, August 04, 2015 2:45 AM To: [email protected] Subject: Re: [NTSysADM] Server 2012 DHCP policy for Winodws and MAC Clients Problem Solved. DHCP policies are so simple. In our solution, created a policy, With Conditions "Vendor Class = Microsoft Options" set the router to match, and all Microsoft Clients get a different router address from all other clients. Way easier than V-Lans. Thought I would let you all know. cheers graeme On 30 July 2015 at 14:31, Miller Bonnie L. <[email protected]<mailto:[email protected]>> wrote: If nobody ever replied, then we might not have any answer. You can't be expected to know EVERYTHING, unless it's your child doing the asking =) I know it's tomorrow for us, but Friday has already started in New Zealand. Happy Sysadmin day to all! http://sysadminday.com/ -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kurt Buff Sent: Wednesday, July 29, 2015 8:47 AM To: ntsysadm <[email protected]<mailto:[email protected]>> Subject: Re: [NTSysADM] Server 2012 DHCP policy for Winodws and MAC Clients Yes, and you can do it on earlier versions too. I hadn't fiddled with DCHP in a long time, so shot my mouth off without checking. Silly me. Kurt On Wed, Jul 29, 2015 at 7:02 AM, Miller Bonnie L. <[email protected]<mailto:[email protected]>> wrote: > You can override options at the reservation/client level (we have some on our > 2012 DHCP, non-r2), but it's a lot of work if you have a lot of reservations. > I like the policy based option that Graeme sent as well--that looks really > cool. > > -----Original Message----- > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Kurt Buff > Sent: Tuesday, July 28, 2015 5:51 PM > To: ntsysadm > <[email protected]<mailto:[email protected]>> > Subject: Re: [NTSysADM] Server 2012 DHCP policy for Winodws and MAC > Clients > > I don't believe so. > > All a reservation does is give you a specific IP address out of a scope > (based on the requesting MAC address), and it's the scope (or the global) > settings that determine what settings the machine receives. > > I don't believe there's a way to specify that two sets of machines in > a single scope get different settings for the same configuration item > - i.e., I don't think a single scope can hand out two different default > gateway (aka router) settings based on some different criteria. > > > Kurt > > On Tue, Jul 28, 2015 at 5:39 PM, Jon Harris > <[email protected]<mailto:[email protected]>> wrote: >> It has been a while but can this be done by using reservations? I >> never had to worry about phones or tablets the last time I actually had to >> do DHCP. >> >> Jon >> >> ________________________________ >> Date: Tue, 28 Jul 2015 10:43:40 +0100 >> Subject: [NTSysADM] Server 2012 DHCP policy for Winodws and MAC >> Clients >> From: [email protected]<mailto:[email protected]> >> To: [email protected]<mailto:[email protected]> >> >> HI There, >> >> I was looking into using Windows Server 2012 DHCP policies to assign >> a different default gateway to all client PC's (a mixture of MACs and >> Windows >> 7 and 8 and soon to be 10. >> >> Does anyone have any recommendations. >> >> Basically I want everything the same for all DHCP clients apart from >> the default gateway. >> >> I would like one default gateway for IP phones, printers and other >> devices, and a different one for Client Windows PC's, Macs, iPhones, iPads >> etc. >> >> This is to route all client internet browsable devices to our web >> filter, and the the rest to the normal unfiltered gateway. >> >> Thanks in advance >> >> Graeme >> >> >> -- >> Good news everyone, you have just received an e-mail from me! > > -- Good news everyone, you have just received an e-mail from me! Attention: Information contained in this message and or attachments is intended only for the recipient(s) named above and may contain confidential and or privileged material that is protected under State or Federal law. If you are not the intended recipient, any disclosure, copying, distribution or action taken on it is prohibited. If you believe you have received this email in error, please contact the sender, delete this email and destroy all copies.
