- This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
Hi all – we are trying to configure our DHCP server to configure specfic options based on Vendor Class/Code.
The Wyse S10/1200LE’s send wyse-1000 as their vendor code and I have set that up accordingly in Windows 2003 DHCP server, along with the relevant options.
It seems that the DHCP server ignores the vendor code and does not send the options to the client. I have confirmed this by configuring a VoIP phone the same way – which sends a different vendor code and needs different options. Options configured ‘normally’ work as expected.
Does anyone know how (done this before?) to kick this DHCP service into action?
Thanks!
Aaron
Hi Aaron,
what do you mean? DHCP vendor ID is no working at all or only with WTOS?
CG
Its not working at all!
I tried the two angles to see if it was specific to the terminals.
Hi Aaron,
there is a MS article that explains nearly all.
http://support.microsoft.com/kb/240247/en-us
One thing is missing in this article. After creating the vendor class you have to add option tags to that class. Do this by right clicking the server object and select “Set predefined….”. Select your new vendor class on top and add all option tags you want to deploy.
Then continue in the MS KB article.
HTH
CG
Yep – thats exactly what I did – except that article does not mention adding specific options for the new Vendor.
If/when you create a new vendor, you need to create the options for it – otherwise there aren’t any there.
That’s what I have written above 😉
he he – great minds think alike? 😳
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |