asked on

Print Server migration tips.

What I am looking for are real world solutions in regards to a print server migration. I have found the tool that Microsoft supplies for the automated printer server migration; however, this solution does not fully fill the gap due to the fact that it will not migrate the client end.

I suppose I could retire the old server out of production all together and give the new server the same DNS A record and give it the same IP address, as a virtual IP, as the old server, but I'm really not for sure what issues this could cause down the road.

I have read lots of documentation, and I am looking for some real world solutions that you all have implemented. If anyone could please advise on what has work for you that would be great for me.

ASKER CERTIFIED SOLUTION

PlaceboC6

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security Officer

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

tigermatt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

PlaceboC6

Sam's idea to migrate the printers from the old to the new and then rename the new to the old systems's name would probably be the easiest. That won't work if you're wanting to keep both machines up and running though.

LEAD Support

ASKER

Thanks for the quick responses. Do any of you guys have an example script? I would love to view the source.

The printer server is R2, but I want to make sure that this is as seamless as possible.

LEAD Support

ASKER

VBS is the way to go I think. I'm going to test bed a few things, but thank you all for the responses.