replacing print server question

  • Thread starter Thread starter kb
  • Start date Start date
K

kb

I will be replacing a member server in our single domain
w2k native mode ads forest this weekend.
It runs sql and is our print server and ts app server.

The replacement server has been built using a temporary
name and is a member of the domain.
Question: Can I add the 100 or so printers now (tcp/ip
ports) to the new server?
I will rename the old server to oldserver then remove it
from the domain and shut it down. Then, assign the
original name to the new server, change it's ip to the
same as the old one had and voila, printing will work????
These printers are published in active directory.

Does this work? Sure would save alot of down time if I
could do it this way.
TIA,
Karen
 
It should work. After you move all printers to another server, it will
republish them under different server. You can the manually delete those
printer objects from AD (they are visible as part of server if you enable -
View computers, users ,.. as containers), or leave it to the printer object
pruner, which should remove them automatically.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com
 
Karen,

The TCP/IP ports will remain when you rename the server. The printer
publications will not, as they correspond with the server's computer account
in the domain. When you delete the old server from the domain, the
publications go with. You should be fine if you go through and
reshare/republish all the printers.

I'd setup a simple test network to make sure, though.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com
 
Thanks very much.

-----Original Message-----
Karen,

The TCP/IP ports will remain when you rename the server. The printer
publications will not, as they correspond with the server's computer account
in the domain. When you delete the old server from the domain, the
publications go with. You should be fine if you go through and
reshare/republish all the printers.

I'd setup a simple test network to make sure, though.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com





.
Click to expand...
 
Microsoft once made a tool called MICROSOFT PRINT
MANAGER. I don't know if it's still in production
however if it is I can say it has saved my job by being
able to move printers from a downed print server at 2am
to a new servers. Drivers, ports an all no probems. you
should do a search for that prodeuct it will be life
saver!
 
Back
Top