There are approximately 200 users in my organization, who connect to 38 network printers. The old print server is being de-commitioned & a new one put in its place. I used Microsoft Print Migrator 3.1 to backup the print configuration from the old server, and restored it to the new server without any issues. All printers have been tested & are working properly from the new server. I'm wondering if there is a way to automatically have all of the users keep their existing printers installed, but have them point to the new server, instead of having to go to each machine & reconnect each user's printers. It would be much easier if something like that were possible. Otherwise we'd have to go to each individual PC & reconnect their printers because the users don't all use the same printers. FYI - The new server has a different name, but has been setup the same as the one its replacing. Due to other functions of this new server, changing it's name is not an option. Any help would be appreciated, Thanks!

Anytime I moved printers to another machine or server I had to go to each machine. I never looked for another way because the network is much smaller than yours. The only way might be through profiles or group policies. Try the forum at: www.minasi.com They would know for sure.

We don't use roaming profiles here, and I am quite comfortable with group policy, however I am unsure of how to configure something like this through a gpo. Thanks for the feedback, any other ideas anyone???

I believe most printer config info on WinXP is stored under the registry branch HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Since you said people use different printers, you could use the free scripting language AutoIt to enumerate the registry keys and only apply the relevant updates. You could compile the AutoIt script and add it to users' logon scripts. Here are three different threads from the AutoIt support forums that contain sample code other great tips and links to other utilities: one, two, three (Even if you don't use AutoIt, you could adapt much of the info to vbscript or simple batch files.)