updating definitions from behind proxy

  • Thread starter Thread starter Guest
  • Start date Start date
There doesn't appear to be a way of
setting your proxy, so I can't update
my definitions.
Click to expand...

And that's just a part of the problem, if
you use ISA Server you may as well
install the FirewallClient to allow the
automatic update.. but to do so, in case
the ISA is configured to only allow
authenticated users you'll need to go
through the process of using the ISA
"credtool" to set the appropriate
credentials for the various users

It should be easy enough to let the
MSAS pick the proxy settings from
IE and using such settings

What else.. uh, yes, I wonder why the
MSAS updater doesn't use the BITS
to transfer the data, that would make
the update process "lighter" on both
system and bandwidth especially on
not-so-powerful systems sitting on a
not-so-fast connection

Regards
 
ObiWan said:
And that's just a part of the problem, if
you use ISA Server you may as well
install the FirewallClient to allow the
automatic update.. but to do so, in case
the ISA is configured to only allow
authenticated users you'll need to go
through the process of using the ISA
"credtool" to set the appropriate
credentials for the various users

It should be easy enough to let the
MSAS pick the proxy settings from
IE and using such settings
Click to expand...

This is how the product is supposed to be functioning, but there appear to
be some bugs : (

What else.. uh, yes, I wonder why the
MSAS updater doesn't use the BITS
to transfer the data, that would make
the update process "lighter" on both
system and bandwidth especially on
not-so-powerful systems sitting on a
not-so-fast connection
Click to expand...

Probably because the Giant coders didn't go for this originally. I don't
know what they'll do in beta2, but I am sure it will be different. Beta1
changes from the original code are being kept to a minimum in favor of work
on Bets2.
 
It should be easy enough to let the
This is how the product is supposed to be
functioning, but there appear to be some bugs
: (
Click to expand...

Well, using "proxycfg -u" solves the issue, but
then if you have an ISA which requires authentication
you'll also need to use the "credtool" to configure
the correct credentials for the MSAS.. what's really
*bad* imho is that if you forget (or don't know how)
to setup things correctly (proxycfg/credtool) and try
to run an update, the MSAS won't complain at all, it
will just say "no available update" (well, something
like that) even if there *ARE* updates !

Ok, I know, it's a beta... but...
Probably because the Giant coders didn't go for this originally.
I don't know what they'll do in beta2, but I am sure it will be different.
Beta1 changes from the original code are being kept to a minimum
in favor of work on Beta2.
Click to expand...

Yes, hope Beta 2 will have some improvements on the
networking side too (amongst others btw).. heh, Microsoft
has a whole lot of technology which is already working well
for other things (e.g. BITS and the update engine), so I can't
see why they don't add such a technology to the MSAS; all
in all it may help creating a better product
 
I have ISA configured with multiple S+C rules for specific
Security Groups. The unrestricted group of users can
update MSAS fine, but the resticted group (which has a
DENY S+C rule except for "Whitelist" Client set), cannot.
The DENY is oviously stopping MSAS getting through, is
there an url/IP/domain that a can define in my whitelist
client set that will allow access behine a DENY S+C rule?

Cheers!

Karl Sandland
 
Karl Sandland said:
I have ISA configured with multiple S+C rules for specific
Security Groups. The unrestricted group of users can
update MSAS fine, but the resticted group (which has a
DENY S+C rule except for "Whitelist" Client set), cannot.
The DENY is oviously stopping MSAS getting through, is
there an url/IP/domain that a can define in my whitelist
client set that will allow access behine a DENY S+C rule?
Click to expand...

You will need to allow all of these:

www.spynet.com
service.spynet.com
download.spynet.com

The latter two are currently aliases for:
ad.spynet.microsoft.akadns.net

The IP addresses returned from these DNS addresses might be variable.
 
ObiWan said:
Well, using "proxycfg -u" solves the issue, but
then if you have an ISA which requires authentication
you'll also need to use the "credtool" to configure
the correct credentials for the MSAS.. what's really
*bad* imho is that if you forget (or don't know how)
to setup things correctly (proxycfg/credtool) and try
to run an update, the MSAS won't complain at all, it
will just say "no available update" (well, something
like that) even if there *ARE* updates !

Ok, I know, it's a beta... but...



Yes, hope Beta 2 will have some improvements on the
networking side too (amongst others btw).. heh, Microsoft
has a whole lot of technology which is already working well
for other things (e.g. BITS and the update engine), so I can't
see why they don't add such a technology to the MSAS; all
in all it may help creating a better product
Click to expand...

I think you will find that beta2 looks quite different from beta1, and not
just in appearance. I too dislike the way the updater cavalierly states
that no updates are available, when all that has happened is that it has
failed to contact the update server for any of a thousand reasons.
 
Back
Top