Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 986
  • Last Modified:

New Print Server Windows 2003 old Print server Windows 2000

I’m in the process of decommissioning a windows 2000 server with printing services and move the printing services to a windows 2003 server.

We need the least amount of distruption for our 120 Windows XP users.

I have used to print migrator 3.1 to backup the server this seems fine but configuring the clients to point to the new server is an issue. Having tested the “chgprint.exe” within a logon script to change the print server NetBIOS name it has not worked. Below;

Translateprinter.txt;
\\newserver\"New Systems Printer"      \\oldserver\"New Systems Printer"
\\newserver\Sales \\oldserver\Sales

Bat file;
@echo off
set LOGDIR=\\server\c$\temp\chgprint\test\logs
set LOG=%LOGDIR%\ChgPrint.Txt
set TOOLDIR=\\server\c$\temp\chgprint\test
start /wait %TOOLDIR%\ChgPrint.Exe /nodialogs
if errorlevel == 3 if not errorlevel == 4 echo %COMPUTERNAME%\%USERNAME% nothing to do, no printer connections installed >> %LOG%
if errorlevel == 2 if not errorlevel == 3 echo ChgPrint executed from desktop not running Windows NT >> %LOG%

if errorlevel == 1 if not errorlevel == 2 echo %COMPUTERNAME%\%USERNAME% could not locate TranslatePrinter.Txt file >> %LOG%
if errorlevel == 0 if not errorlevel == 1 echo %COMPUTERNAME%\%USERNAME% executed ChgPrint without error. >> %LOG%


To reiterate - the problem is the client printers not changing to the new server, the only thing I can think of is the print share names - some have spaces.

Any
Help will be appreciated.
0
nickymo
Asked:
nickymo
1 Solution
 
akarwatowiczCommented:
Why dont you create identical printer shares / mappings on the new server, decomission the old server, and lite up the new server with the same servername.  Users won't know the difference.
0
 
nickymoAuthor Commented:
Thanks akarwatowicz,

I can't change the new server name because the naming convention has changed.

That would have been too easy!!

;)
0
 
bbaoIT ConsultantCommented:
hehe. but that does not mean we can not make it simple in other approaches:

1. by static name mapping: if you have a WINS or DNS server for internal naming resolution, just add a static item on the name server, either WINS or DNS, to manually map the name of old W2K server to the IP of new W2K3 server. this will allow all the existing clients use their old UNC to access the printer server without doing any labor on them.

2. by host file: if you do not have a WINS or DNS available on the net, just cut your above script to a one-line version:

ECHO 1.2.3.4 W2KSVR >> c:\windows\system32\drivers\etc\hosts  /* or LMHOSTS for NETBIOS conventions */

where 1.2.3.4 is your W2K3 server's IP and W2KSVR is the name of that old W2K server.

hope it helps,
bbao
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now