You could create a Cname and point it to the server you want the users to do the printing on. In the event you need to change them over to the other server, change the cname to reflect that.. and all the clients seamlessly start printing to the other server. It requires that the printers are installed and setup and named the same on both servers though.
I have done this before and it works fairly good. It simply requires you to change the cname in the dns. I'm sure you could write a script or program that would check the status of the server and change the dns on command.
-Eric
Main Topics
Browse All Topics





by: flood_landPosted on 2006-01-17 at 14:51:01ID: 15724268
You could probably get away with configuring network load balancing on the two servers. You'd probably have to change the config on all your client machines to point to the NLB cluster though.
indowsserv er2003/tec hnologies/ print/defa ult.mspx
Here is some stuff on printing in 2003 but most of it wants you to set up a stateful cluster using 2k3 enterprise or datacenter though.
http://www.microsoft.com/w