reconnecting ndps manager to cluster resource volume

[Keith Larson]

I had a manager that was working fine as a cluster resource.  Someone (not me) made the mistake when prompted to move the database to a different volume, they answered yes.  This associated it with a node's sys volume not the cluster resource.

 

I moved the manager to a different server to keep it active and running and recreated a new cluster aware manager just fine.  I tested migrating printers from one manager to the other and gotten mixed results on the workstation side.  Many machines connect to the printer just fine.  Others have a registry key that connects them to the original manager.  If this key is deleted, it doesn't recreate, but that doesn't seem to be a problem and the user can print just fine.  What is this and can I just delete it on for every printer?

 

[HKEY_LOCAL_MACHINE\Software\NDPS\Installed Printers\TreeName\.NDPS printer name.ou.o]
"Net Address"=hex:01,00,00,00,06,00,00,00,0d,44,0a,28,0f,f5,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

I have tried lots of ways to correct this and nothing seems to be a thorough solution.

 

The printer context never changes.  I can keep the manager name the same by using different containers, but that doens't seem to be enough.