There are various "hacks" that can be used to populate "network" printers as "local" printers on client computers (using a "Local Port", pointing the client directly at the print device, running an LPR queue on a server and pointing clients at that). I'd recommend none of those because the ongoing maintenance is a real pain.
Assuming you have an Active Directory domain you can use Group Policy to deploy printers. This gives you a nice way to make changes, down the road, when (inevitably) you have to add / move / change printers.
If you don't have an AD domain I'd consider writing a script to "connect" to the printers and putting that script into the All Users "Startup" folder of the Start Menu. The gist of a such a script would be something like:
Set objNetwork = CreateObject("WScript.Network")
... continue ad infinitum ...
You can also use such a script to remove "stale" printers later when (inevitably) you add / move / change printers.