Sign in
Microsoft.com
 
Forefront Edge Security TechCenter
 
 
 
Forefront Edge Security TechCenter > Forefront Edge Security Forums > Forefront Edge Security - Monitoring, Logging, Reporting > WPAD and 2000+ Clients
Ask a questionAsk a question
Search Forums:
 

AnswerWPAD and 2000+ Clients

  • Friday, October 30, 2009 2:20 PMvkit Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    We have a small issue where we have multiple sites all using their own ISA server for internet access.  This year we are replacing all the ISA servers with new servers.  WPAD is configured in DHCP and working very well.  The problem we are running into is when we switch the name in DHCP to the new server the clients do not get the new WPAD setting with the new server.  The workstations are caching the servername.  We can see it in the registry.....  I've looked up on the internet and this seems to be a major issue with people.  The manual process that is well documented work great but is a no go to expect our end users to do the task. 

    What I'm wondering if anyone has an automated way to doing this or even a different way?

    Thanks

     

Answers

  • Friday, October 30, 2009 3:26 PMJim Harrison IsaDewd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Unfortunately, the problem is client-based and as such requries a client-targeted solution.
    If you're operating a domain environment, you can add the following command to a logon script:
        del \wpad[*.dat /s
    ..otherwise, your users have to do this themselves.

    WPAD is a "pull" model - it's impossible for you to trigger the clients to refresh the information they already have.
    Jim Harrison Forefront Edge CS
     

All Replies

  • Friday, October 30, 2009 3:26 PMJim Harrison IsaDewd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Unfortunately, the problem is client-based and as such requries a client-targeted solution.
    If you're operating a domain environment, you can add the following command to a logon script:
        del \wpad[*.dat /s
    ..otherwise, your users have to do this themselves.

    WPAD is a "pull" model - it's impossible for you to trigger the clients to refresh the information they already have.
    Jim Harrison Forefront Edge CS