How can I disable auto update in InoculateIT for traveling users? We
have 6.0 on laptops in docking stations, and autoupdate set in the
configuration. I know we can adjust timing for autoupdates in the
configuration, but when users travel with their laptops, they dial in
to get email, and autoupdate will kick off if it is past their update
time. The update takes way too long on a dialup, and it effectively
disables their connection for the time of the update. The boss wants
a way to disable their update if they are dialing in, possibly based
on allocated IP range. I am saying it can't be done because this is
not client server, and the update function is not driven by the
server/client connect, rather manually hard configured in the client.
The boss claims there must be a way, and does not want to ask the user
to manually disable it when they are traveling (my suggestion). Has
anyone tried doing this?

Thanks,

Hal


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

(E-Mail Removed) wrote:
> How can I disable auto update in InoculateIT for traveling users? We
> have 6.0 on laptops in docking stations, and autoupdate set in the
> configuration. I know we can adjust timing for autoupdates in the
> configuration, but when users travel with their laptops, they dial in
> to get email, and autoupdate will kick off if it is past their update
> time. The update takes way too long on a dialup, and it effectively
> disables their connection for the time of the update. The boss wants
> a way to disable their update if they are dialing in, possibly based
> on allocated IP range. I am saying it can't be done because this is
> not client server, and the update function is not driven by the
> server/client connect, rather manually hard configured in the client.
> The boss claims there must be a way, and does not want to ask the user
> to manually disable it when they are traveling (my suggestion). Has
> anyone tried doing this?
>



+ Please reconfigure your news reader to display
your full name in the From field.


You could stop the according service.
No Autoupdate Sevrice - no ...erm... automatic update :-)
You could set up a second hardware profile ("mobile") and then alter the
service not to be started when using the "mobile" hardware profile.

Best regards
Thomas.

indeed , make a second profile . You can change the profile in the services
window , properties of the given service


"Thomas Krug" <(E-Mail Removed)> schreef in bericht
news:bj31qc$4f5$06$(E-Mail Removed)...
> (E-Mail Removed) wrote:
> > How can I disable auto update in InoculateIT for traveling users? We
> > have 6.0 on laptops in docking stations, and autoupdate set in the
> > configuration. I know we can adjust timing for autoupdates in the
> > configuration, but when users travel with their laptops, they dial in
> > to get email, and autoupdate will kick off if it is past their update
> > time. The update takes way too long on a dialup, and it effectively
> > disables their connection for the time of the update. The boss wants
> > a way to disable their update if they are dialing in, possibly based
> > on allocated IP range. I am saying it can't be done because this is
> > not client server, and the update function is not driven by the
> > server/client connect, rather manually hard configured in the client.
> > The boss claims there must be a way, and does not want to ask the user
> > to manually disable it when they are traveling (my suggestion). Has
> > anyone tried doing this?
> >
>
>
>
> + Please reconfigure your news reader to display
> your full name in the From field.
>
>
> You could stop the according service.
> No Autoupdate Sevrice - no ...erm... automatic update :-)
> You could set up a second hardware profile ("mobile") and then alter the
> service not to be started when using the "mobile" hardware profile.
>
> Best regards
> Thomas.
>
>
>

If you are using Inoculate the way it should be used, you have a
distribution server on your LAN that gets the pattern files, and your
clients update their pattern files from the LAN distribution server.
If you are not doing this, then shame. (That's why the ftp.cai.com
server gets overloaded.)

Anyway, configure the client to update from a distribution server
ONLY.

\\yourserver

and remove the FTP download from all the clients.

I assume that \\yourserver rpc service (ports 135-139) are not
accessable from the clients when they are dialed into the internet.
If not, put in your firewall rules or router ACLs to block ports
135-139 for this \\yourserver.

This way when the clients try to update when on a dialup connection,
they will only attempt to download from \\yourserver, which will be
inaccessable.

Odd that you would do this however. I have the exact opposite config.
The internal lan stations update from the \\yoursever redistribution
server, and the laptops additionally try FTP so they update when they
are on dialup.

Should you do this, you should make it a policy to make these laptops
have to come to IS prior to being re-connected to your LAN. You
should then take a CD with the latest pattern files, load them onto
the laptop, update the pattern files, and do a full VET and
InoculateIT system scan of these PC's -- all prior to connecting to
your network.

MSBlaster2 is just around the corner.