Using spyware in a workgroup with tcp/ip printing

  • Thread starter Thread starter Jasee
  • Start date Start date
J

Jasee

AFAICT you need to set up each individual user on each
machine in a workgroup if you are printing to a networked
printer using tcp/ip? (which is highly inconvenient) It
doesn't seem to be possible to set global options for any
particular user group (for instance) on a particular machine.
 
I'm not sure I understand your query.

Yes, Microsoft Antispyware needs to be set up on each machine in a
workgroup.

Yes, it does not function well in multi-user situations on the same machine.
The development team is aware of this, but we don't know what will come of
that--a version with fixes around that issue hasn't been released.

How do the above relate to the use of TCP/IP for printing in a workgroup?
 
-----Original Message-----
I'm not sure I understand your query.

Yes, Microsoft Antispyware needs to be set up on each machine in a
workgroup.
Click to expand...

Yes I realise that
Yes, it does not function well in multi-user situations on
Click to expand...
the same machine.

This is my situation

The development team is aware of this, but we don't know what will come of
that--a version with fixes around that issue hasn't been released.

How do the above relate to the use of TCP/IP for printing
Click to expand...
in a workgroup?

Well, calls to the printer are intercepted by antispy when
the other users log on the same machine (power users in
W2k) as spyware calling out, even though I've configured
antispy to ignore these calls as an administrator.
 
-----Original Message-----
printing
in a workgroup?

Well, calls to the printer are intercepted by antispy when
the other users log on the same machine (power users in
W2k) as spyware calling out, even though I've configured
antispy to ignore these calls as an administrator.
Click to expand...

Ahh--that makes sense. I believe that the only fix for
this in the current state of the beta would be to turn
off the particular checkpoint responsible for the
alerts. I can't give you a clear pointer to the
checkpoint, I'm afraid--I haven't seen this myself--you
can do a binary search through the checkpoints to find
the right one, or read the descriptions and try to get it
right first! The downside of this, of course, is that
you lose the protection afforded by that particular
checkpoint. I don't know how to weigh that for you at
this point. You can also turn off all real-time
protection, but that's pretty drastic--to do that, you
need to follow the "workaround" paragraph in this KB
article:
http://support.microsoft.com/kb/892375 End users may be
prompted to allow or
block administrative actions that originate from a
central management tool
after they install Windows AntiSpyware (Beta) on a
computer that is managed
by Systems Management Server 2003
 
Back
Top