I've posted this previously, but I still haven't found a resolution. I'm looking at a way to migrate my Windows 2000 Server (print server) to a Windows Server 2003 (print server) with affecting the users. This won't be an upgrade. I'm looking at running the 2003 system on completly new hardware. Here is what I've attempted with no luck. Names/Aliases -w2k box name = Apollo -w2k box alias = Zues -w2k3 box name = Hermes Old Setup -installed TCP/IP printers on w2k -share the printers -install printers on clients from Zues share New Setup -installed same TCP/IP printers on w2k3 -share the printers -remove Zues DNS alias from w2k (Apollo) -add Zues DNS alias to w2k3 (Hermes) -force replication As I've stated, this didn't work. What is the recomended approach for migrating a print server? Keep in mind that I'm in an environment that I'd like to make this as painless as possible for the users and that this is not an upgrade. Thanks

I'm a little muddled on your domain/network/client setup so I'd suggest you start a new post with a little more info. Like how do your clients connect to the print queues? Do you map them manually or via a login script? Are you on a single domain? Are these stand alone print servers? Are they shared in the directory (if you're using Active Directory)? I think you're over complicating things somehow. Have you tried unsharing the old print queue, create the new print queue and publish it in AD with the same shared name? Maybe just map the new printer via a login script? You could have the script delete the old printer and map the new one without any user interaction needed...