For connecting the printers, the server doesn't care - as long as it can reliably connect to the printer, it will try to share it out! My personal suggestion would be to use network-based printers, as you can place them anywhere you can run Category 5/5e/6 cabling.
When you add the printer driver to the server, do not run the auto-launching setup program for your printer. Instead, add the Print Driver manually. Under the Drivers tree, you can add a driver, and browse to the CD-ROM or download of the driver's files, including some *.inf or *.cat files - make sure you know where these are. Select the folder, and it should ask you which printer driver to install. You have the option of installing for other architectures as well - I recommend this if you have a mix of ARM, x86, x64, IA-64 architectures in your environment.
When the computers connect to the server and add the printer, the server spits out the driver, and the port is routed through the server - jobs go to the server, the server renders and prints it to the printer. This is why you have a print server. No wizards should appear from the manufacturer if you install the printer from the server.