I'm running ISA 2006 fully patched on a windows 2003 SP2 fully patched system. The steps i followed came from the 2004 book as they are identical for 2006 ad match the steps outlined in the link you posted.
The DHCP auto discovery works when the clients attach to the network where the DHCP server resides. My issue is that clients that are on another subnet that get there ip's from the same DHCP server but through the DHCP relay agent installed on the ISA are failing. These clients get there base IP but never get the configureation info.
By sniffing the network I can see the ISA recieves the DHCP info requests but never forwards it on to the the backend DHCP server.
At the moment the network hosting the DHCP server is sitting on the Internal network of the ISA, i'll try and test the setup by moving that subnet to a seporate interface / subnet network rule and see what happens but seeing as the normal ip DHCP stuff forwards fine and only the DHCPinform messages disapear in thin air i'm guessing it will not make a big difference but it's better than doing nothing ;-)
Regarding the other link I had already read the info and the issue i'm having is 99% the same as state here execpt ofcourse my clients are not VPN clients but users sitting on a different ip network off the isa server
"VPN Clients Cannot Retrieve Configuration Information When the DHCP Relay Agent Is Running on the ISA Server Computer " => my clients are not VPN clients"
A WPAD entry in DHCP cannot be retrieved by virtual private network (VPN) clients.
This can occur when all the following conditions are true:
The DHCP client and the DHCP server belong to different subnets. "=> yes this is the case"
The DHCP relay agent is configured on a computer running Windows Server® 2003. "=> yes this is the case"
ISA Server 2004 and the DHCP relay agent are installed on the same computer. "=> yes this is the case"
VPN client support is not enabled in ISA Server. "=> my clients are not vpn client, i'm not using vpn but i did enable this just to see if it would help"
This behavior occurs because ISA Server controls the Routing and Remote Access service, which is not started if VPN client access is not enabled.
Solution: To resolve this behavior, do any of the following:
Use a DHCP relay agent on the default gateway for the subnet, or on a computer not running ISA Server. Then remove the DHCP relay agent from the computer running ISA Server. "=> can't do that as ISA is my default gateway and only server on that network, all the rest are client pc's"
If you must run the DHCP relay agent and ISA Server on the same computer, enable the Enable VPN Client Access option in ISA Server Management to ensure that the Routing and Remote Access service is running. For more information, see the Microsoft Knowledge Base article 911072, "The DHCP clients may not obtain the configuration script when you use DHCP Option 252 to automatically configure Internet Explorer." "=> enabled vpn client,but did not help"
Just for the record, here is a dump of the DHCP relay agent settings on my ISA server, i set them up to match the MS example in the article:
# ---------------------------------- # DHCP Relay Agent configuration # ---------------------------------- pushd routing ip relay uninstall install set global loglevel=ERROR add dhcpserver server=192.168.6.200 add dhcpserver server=192.168.6.209