I'm in the process of migrating from a ISA Server 2004 Standard server to a ISA Server 2006 Standard server. My question deals with the ISA Client settings in relation to the new server.
The clients are currently pointed to a ISA Server called serverA. This process is done by publishing the name of the server using the DHCP WPAD 252 process and port 80 on the ISA Server. I need point these clients to the new ISA Server. I figured the process would be as easy as changing the DHCP option to reflect the name of the new server.
However, this does not work. The clients continue to pick up the old server name even when DHCP is changed to reflect the new server. I can connect to a client and run the IPCONFIG /RELEASE and /RENEW commands. This and only this process (a reboot does not work) seems to cause the ISA client to reconfigure using the new server. Another piece of information that may be helpful is the fact that we use DHCP reservations to assign addresses.
Does anyone have experience with this scenario? Am I missing something in the process? Do DHCP reservations cause this issue? I'm sure I can write a script to run the IPCONFIG commands on startup but it would be interesting to find out why this happens.
Thanks for the response. As I stated in the question above, I would also expect that the clients would pick up the new ISA server settings after rebooting because of the DHCP refresh. However, this doesn't happen, it also doesn't happen after 6 hours. The only way to make the clients in this location automatically detect the new ISA server is to go through the ipconfig /release - ipconfig /renew process. This seems to be the only way that the clients will automatically detect the new server within a managable timeframe. Any other help that you have would be great.