Re: Renaming Clustered Print Server "network name" resource

Yes, that is the way I have done this. If you publish printers to AD do not
do this until after you rename the old server and bring that servername
online on the cluster since you will end up getting connections to the
temporary server name which will cause someone confusion later.

You should be able to use printmig if you install the drivers using cab
files to the clustered resource before restoring. Also make sure the
temporary name does not have "spool" as part of the name or this confuses
printmig.

If you have Vista SP1 around you can backup the old machine remotely and
restore to the Server 2003 cluster.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"peejay" <> wrote in message
news...
>
> I'm looking to migrate an aging print server to an existing (2003)
> cluster.
>
> I'd like to initially be able to test it obviously, but ideally I'd
> also like the new print server to take on the identity of the existing
> one.
>
> Unfortunately I can't use the old Print Migrator tool as some of the
> drivers seem to use .cab files.
>
> I'm happy simply re-creating queues manually, but is it possible to
> create the Network name resource with one Netbios name, add a bunch of
> drivers/queues, then later stop the resource, shut down the old print
> server, then rename the resource to the old print server name and
> restart the resource?
>
> I know it's easy to logically do, I just want to ensure it's not going
> to mess anything up with the queues having been created under a
> different virtual server name.
>
> Regards,
>
> Paul
>
>
> --
> peejay
> ------------------------------------------------------------------------
> peejay's Profile: http://forums.techarena.in/members/137243.htm
> View this thread: http://forums.techarena.in/server-cluster/1249268.htm
>
> http://forums.techarena.in
>