Migrating from single print server to clustered print server

Migration of a single Windows 2000 print server to a Windows 2000 clustered print server.

'printserver1' is the name of the old print server.

 

I ran the Print Migrator wizard to get the printers on the cluster.  My plan:  on the night of the conversion, I would shutdown printserver1 and add a "network name" resource in the cluster configuration for printserver1 so that any clients that didn't run the vbs logon script(see my migration blog article) to change the connections would still be able to print without any noticeable effects.  That was my plan at least.  The following was the Murphy's law version of what happened:

 

After the shutdown of printserver1, tried to bring online the printserver1 'network name' resource.  But, I couldn't bring the printserver1 'network name' resource online.  I kept saying 'failed'.  The following events were posted to the system eventlog.

NOTE: make sure the advanced property, 'affect the group', is turned off, otherwise if you do have problems with the resource coming online, it won't cause the group to fail.  You can always turn that option on once the resource is stable and working. 

 

Event Type: Error
Event Source: ClusSvc
Event Category: Services
Event ID: 1069
Date:  11/23/2005
Time:  2:00:24 AM
User:  N/A
Computer: NODE1
Description:
Cluster resource 'printserver1' failed.

 

*************************************
*************************************

 

Event Type: Error
Event Source: ClusSvc
Event Category: (2053)
Event ID: 1052
Date:  11/23/2005
Time:  2:00:24 AM
User:  N/A
Computer: NODE1
Description:
Cluster Network Name resource 'printserver1' cannot be brought online because the name could not be added to the system.
Data:
0000: 0e 50 00 80               .P.€   

 

 

 

Cluster Network Name May Not Come Online with Event ID 1052 - http://support.microsoft.com/kb/257903

 

Solution (for me anyway):

delete all dns A and PTR records for printserver1
delete all wins records for printserver1

 

run nbtstat -RR on each node in cluster
then brought printserver1 network name online