Re: Advantage of using server-based print server/queue?
- From: "Anthony [MVP]" <anthony@xxxxxxxxxxxx>
- Date: Tue, 1 Apr 2008 10:53:41 +0100
It's a lot easier to automate connecting users to a shared printer on a
print server than installing a printer on the client. I like to publish
printers in AD so that users can just select the one they want and connect.
Anthony,
http://www.airdesk.co.uk
"Guy Pardoe" <guy@xxxxxxxxxxxxxxxx> wrote in message
news:ub0EjEakIHA.5396@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Historically, I'd always set up a printers for a LAN environment to use
Windows Server print server. I've also dealt with other print servers such
as HP JetDirect, etc. But these days it's common to acquire printers that
are already network capable.
In a recent discussion with another IT manager, he questioned me: "Why
would you use the Windows Print Server (spooler) anymore? Simply set up
each workstation to point to the printer at such-and-such IP address. You
get nothing by routing the print jobs through the Windows [Server]
Server."
On the fly, I wasn't sure how to respond.
We both exist in the small business world. That is, companies with 50 -
100 employees and, say, about 10 network printers spread around the
company for employees to use. And we both manage AD environments where
standard users do not have Admin privileges on their local machines.
So my question is, what advantages are there in using a Windows
Server-based print server? I mean, what do we gain anymore?
Guy
.
- Prev by Date: IAS IP Address
- Next by Date: Re: IAS IP Address
- Previous by thread: Re: Advantage of using server-based print server/queue?
- Next by thread: net time shows time on a workstation rather than a DC
- Index(es):
Relevant Pages
|
