Jump to content

Recommended Posts

Posted

Morning All,

 

I hope that someone might be able to help me with a really annoying issue. To cut a long story short, one of the techs often performs Windows Updates on non-domain computers using the school's internet connection (for exam computers, test machines, etc). When using the ISA server as the proxy on the client machine, it can take up to 10 minutes for updates to be detected. If using the upstream proxy server on the client machine the updates are detected almost straight away.

 

Tried the following but still no joy:

---------------------------------------------------------------------------

Tested updates from dc, removed dns forwarders and tested same result.

Added opendns public dns server has forwarder and tested same result.

Disabled AV on test server, same result.

Added new update url to isa url set called "New Windows updates", created access rule from local host to the 2 update url sets and the one update domain set.

 

Retested same result, deleted update IE object from browser and retested same result.

---------------------------------------------------------------------------

I just cant work out why it takes soo long on non-domain computers. Has anyone encountered similar issue or know a resolution?

 

Thanks guys.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...