Foreman » Smart Proxy

Sorry this one should go under smart-proxy. Maybe one of the admins can move it? :)

hmm.. in your dhcp server (e.g. via mmc) can you see the ability to add vendor options? we never tried it with WinXP only with 2000+ servers.

Hi Ohad,

the DHCP is running on windows server 2008 r2 and yes it supports Vendor Options. I just installed the smart-proxy under windows XP as we should not install any additional software on our Domain Controllers. The smart-proxy controlls the DHCP via the netsh commands. This works fine as long as I don't use the latest (development) version of smart-proxy.

Regards,
Oliver

Hi Oliver,

try adding the english Language pack.

Switch over to english as default display language and this error is gone.

While this is old, I figured I'd update it with a little FYI. I ran into this due to entering the DHCP server in settings.yml without the usual Windows souble-backslashes.
Changing it to ":dhcp_server: \\dhcp.mynetwork.com" fixed this right away. This can be seen in the original report as well, where the netsh-command being executed refers to the server by it's IP sans the double backslashes.

Perhaps this could be clarified in the comments in the settings.yml example file?

I ran into what seems like the same issue. In my logs, I saw entries like:

[2015-04-20T11:07:25.140098 #2344] ERROR -- : Failed to enumerate the scopes on 192.168.199.5Vendor class not found

I tried make the change suggested above, which just changed the error entries to:

[2015-04-20T11:35:25.454356 #2904] ERROR -- : Failed to enumerate the scopes on \\192.168.199.5Vendor class not found

After digging through the code an adding some gratuitous print statements, I discovered Proxy::SETTINGS.x86_64 being used in Proxy::DHCP::NativeMS#execute to choose between 'c:\windows\sysnative\cmd.exe' and 'c:\windows\system32\cmd.exe'. I haven't figured out why yet, but it somehow Proxy::SETTINGS.x86_64 was being set to true despite 'c:\windows\sysnative' not existing. When I add ':x86_64: false' to settings.yml and restart the smart proxy, it suddenly uses the correct interpreter path and functions as desired.