That does make a difference.  I know when I installed network printers,
those that used their own network card or a jet direct, I had to do the
installs as users were not able to install printers.  Once on the machine
they showed up in every profile on that machine.  Since a switched to a 2003
print/web server with Vista I can deploy them from the print server and they
work like a charm.  Those features I enable on the print server are all the
users get and they don't have to do anything but select which printer.  XP
does not work as smoothly but it does work,  The users if they know where
the printer exist can search and install themselves.  I can look at the
print server and it tells me the name of the file printed and who printed it
but only the user name.

I still think Jim is right one summer to get it up and then just a week or 2
each year to modify and the individual user accounts would make monitoring
so much easier.

Jon

On Wed, May 7, 2008 at 3:48 PM, John Hornbuckle <
[EMAIL PROTECTED]> wrote:

>  I can say with certainty that when we login as ourselves and connect to a
> shared printer, that printer is NOT listed when we login with a different
> account (e.g., a student account) on that same machine.
>
>
>
> If it makes a difference, the shared printers aren't connected directly to
> the network. They're connected to a workstation and shared from there.
>
>
>
>
>
>
>
>
>
> John
>
>
>
>
>
> *From:* Jon Harris [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, May 07, 2008 2:07 PM
> *To:* NT System Admin Issues
> *Subject:* Re: Who printed this?
>
>
>
> Nope, they will be still be there.  You can check the system log on all
> the systems to see who did it but I would think only one time would make
> individual accounts easier to manage than searching all the local desktops
> for a print job.  I was looking on my print server.  It is so much easier to
> monitor rather than a bunch of desktops and deployment is a lot easier as
> well.
>
>
>
> Jon
>
> On Wed, May 7, 2008 at 2:01 PM, John Hornbuckle <
> [EMAIL PROTECTED]> wrote:
>
> But these are network printers that we're connecting to, and connected
> network printers are on a per-user basis rather than a per-machine
> basis. So if the Media Specialist connects to the shared printer under
> her account, that printer won't be there when the student logs in,
> right?
>
>
> John
>
>
>
>
> -----Original Message-----
> From: Kennedy, Jim [mailto:[EMAIL PROTECTED]
>
> Sent: Wednesday, May 07, 2008 1:45 PM
> To: NT System Admin Issues
> Subject: RE: Who printed this?
>
> I can't answer your specific questions, but some things to think about
> related to this.
>
>
> GPO to only allow your meida specialists and IT staff install printers.
> So room 222 gets the printer near it and no others. That narrows down
> the attack footprint so to speak.
>
> Get away from the generic accounts as much as possible.  7 thru 12 here
> have to use their own account. There is a generic account for
> emergencies, only the media specialist have that password and we change
> it very often.
>
> 1-6 each building has a generic account that is changed each year.
> Otherwise the 6th graders use the account in the jr highs......
>
>
>  > -----Original Message-----
> > From: John Hornbuckle [mailto:[EMAIL PROTECTED]
>
> > Sent: Wednesday, May 07, 2008 1:38 PM
> > To: NT System Admin Issues
>
> > Subject: Who printed this?
> >
> > Some of our students have just figured out that they can print to any
> > shared printer in their school (the printers are shared with the
> > default
> > permissions that allow everyone to print). We can stop this by
> > adjusting
> > permissions, which we did for one printer this morning--which just
> > caused the students to find another one.
> >
> > Students share a common account, so knowing the account that's sending
> > the job won't help. I really need to know the name of the machine
> > sending the job.
> >
> > Is there a way to do this? Does that get logged?
> >
> >
> >
> >
> > John Hornbuckle
> > MIS Department
> > Taylor County School District
> > 318 North Clark Street
> > Perry, FL 32347
> >
> > www.taylor.k12.fl.us
> >
> >
> > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
>
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
>
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
>
>
>
>

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to