Windows – Anything to share a printer from 32-bit to 64-bit Windows

There is no built-in mechanism to disable printer redirection for only specific printers.

I'd consider doing the following (it's convoluted as all get out, but it should give you what you want):

• "Share" the printers on each client computer that should be available to the Terminal Server.

• Add the "TCP/IP Print Server" service to each client computer (marking the service for automatic startup and opening port 515 in the local Windows Firewall on each client computer, if applicable).

• Create local printers on the Terminal Server (or other server computer) corresponding to each printer attached to client computers. These printers should use "Standard TCP/IP" ports configured for LPR, with the "Queue Name" set to the share name specified on the client comptuer for each given printer, and with the "LPR Byte Counting Enabled" check-box checked.

You have control of the print queue name using this method such that you can make the name appear as you'd like. You can set permissions on the queues to prevent users from sending jobs to the wrong printers if you so desire. You can completely disable client printer redirection, as well.

(I do the whole "TCP/IP Print Server" dance, as described above, rather than using "Local Ports" naming UNCs. Some people do the "Local Ports" but I've found throughout the years that I have severe reliability problems doing it that way. My method basically makes the PC act like a really expensive "JetDirect" box...)

Just to map a network share directory you would use this command:

net use \\Server\ShareName\Directory

This mapping would:

• not be persistent
• would have to be established and authenticated at user login
• you would access the share using the UNC path, and not a local drive letter

If you want to access the network share through a location on your local C: drive, you'll want to set up a symbolic link:

mklink /d  C:\Folder\ShareName \\Server\ShareName\Directory

Now when you navigate to C:\Folder\Share you'll see the contents of \\\Server\Sharename\Directory. You'll still need to provide authentication for the resource with something like net use (or just be logged into a domain account on a domain system that has access) otherwise the link will probably error out angrily.