Server aliases in AD?

[joe]

Suppose we have two servers: Printserver1 and Printserver2 in our AD
domain. Printserver1 hosts Printer1, and Printserver2 hosts Printer2.

Further suppose that we want to get rid of Printserver1 and have all
printer sharing done by Printserver2. We configure and share Printer1
on Printserver2, so that it's now sharing out both printers.

The problem, however, is that the number of installed machines
currently configured to print to \\Printserver1\Printer1 is large
enough such that changing each machine by hand (to print to
\\Printserver2\Printer1) is a non-starter.

What's really needed here, is a way to have Printserver2 *answer* to
the name of Printserver1 in *addition* to answering to it's regular
Printserver2 name.

Can this be done? If not, how does Microsoft propose that situations
like this be handled?

- Joe

 

[Tomasz Onyszko [MVP]]

Suppose we have two servers: Printserver1 and Printserver2 in our AD
domain. Printserver1 hosts Printer1, and Printserver2 hosts Printer2.

Further suppose that we want to get rid of Printserver1 and have all
printer sharing done by Printserver2. We configure and share Printer1
on Printserver2, so that it's now sharing out both printers.

The problem, however, is that the number of installed machines
currently configured to print to \\Printserver1\Printer1 is large
enough such that changing each machine by hand (to print to
\\Printserver2\Printer1) is a non-starter.

What's really needed here, is a way to have Printserver2 *answer* to
the name of Printserver1 in *addition* to answering to it's regular
Printserver2 name.

Can this be done? If not, how does Microsoft propose that situations
like this be handled?

This is domain environment? If yes, just add DNS entry to point
Printserver2 IP with the name of Printserver1 - but for me it is not a
solution, IMO the best way will be to write a little script and put it
as user logon script which will delete old printers for the users and
create new one with proper mapping to printer on the PrintServer2.