Windows 2003 Server manage print queues that print to print server

[Steven E. Protter]

I work with 1, soon to be two Windows 2003 Server boxes.

Currently the server is sitting out next to the printer, which is connected via parallel port. It manages the print queue directly.

For security reasons, I want to move the server into a locked, room and deny the users access to it.

I wish to change the print queue settings to work with a simple print server device which I will leave next to the printer and put on the network.

I'm not certain how to search microsoft support for a procedure.

I also need to know if it really matters what kind of print server I have.

SEP

[Will Niccolls · Accepted solution]

I would simply attach the printer to the network, and add it to the printer directly, not through another print server device.

Windows Server 2003 can manage the printing just fine. Once the printer is on the network, you can go to the server: Printers and Faxes menu. Then Add a printer, local, (don't autodetect) manually configure a port of type IP, configure it with the IP address. If the server has the driver installed (which it should, since it is currently connected to a local port) then it will simply find the printer and work fine. You can share it with whatever permissions you wish.

[Steven E. Protter]

Thanks.

As you can see I am windows impaired.

I will try it in two weeks.

Shmuel

[Court Campbell]

SEP,

I would suggest buying an external jetdirect. You can find them pretty cheap on ebay.

[Steven E. Protter]

Already have a print server that works well in a Linux environment with laserjet printers.

I just needed help understanding how to configure the print queue to manage push jobs there. I want to move the server to a secure area so the unauthorized staff that keep touching the box stop doing so.

The reason I want to have windows server manage the printing is so the user desktops need not be touched.

SEP

[Will Niccolls]

"change the print queue settings"

Well, if the printer is served by a jetdirect or other dedicated print server there won't be any print queue settings on the Windows host. Simply detach the printer from it, delete it from the Windows server print menu and client machines print menu, connect it to the dedicated print server, add it back to the clients and you're done.

I wouldn't bother though. Another print server device is just another point of maintenance, power, heat, and failure. Windows serves just fine as a print server. You can control security access using Windows users and groups and push out drivers automatically. If you have Server 2003 R2 and Active Directory, you can automate the deployment with group policy based on computer or user group membership.

[Steven E. Protter]

I will respectfully disagree with the last recommendation.

For Windows server to be sitting in a common area exposes it to cleaning people. Once I caught one trying to log on and presumably look at email. Based on what I saw in the browser photo cache of an unprotected machine in another office at the same complex, If he wanted to email his relatives, they need to wear more clothing.

The risk of a print server failing is definitely something I'm willing to live with.

That being said, I appreciate the input and will let you all know how it turns out.

SEP

[Will Niccolls]

Steven, you misunderstand. If the printer is on the network, then the server can still be the print server yet be locked in a room or even halfway around the country I suppose.

Windows Server 2003 can server network print jobs quite nicely. Go ahead and lock it in the closet.

Perhaps the printer doesn't have a network interface. In that case, then yes, you'll either have to buy a network adapter for the particular printer model, or a jetdirect adapter, but it can still be served and security settings controlled by the server, wherever it is.

Best regards,

Will