AACCosmos
asked on
Microsoft Print Cluster: Multiple Print Groups how to block sharenames
Hi guys,
I've setup a print cluster with multiple nodes and multiple print resource groups to devide the load.
Now I have problem with the shared printer names that show up in eachothers Cluster Network Name.
For example:
I have 6 printer groups with networks names pserver1 till pserver 6.
If resource group pserver1 and pserver2 are hosted on Node1, and I access sharename \\pserver1\, I will also see the printers that are installed on pserver2.
This causes a lot of confusion for the administrator who need to maintain and configure these printers within our enviroment.
Is there any way possible to block visibility from other print groups when u access a specific network name?
Thank you so much!
I've setup a print cluster with multiple nodes and multiple print resource groups to devide the load.
Now I have problem with the shared printer names that show up in eachothers Cluster Network Name.
For example:
I have 6 printer groups with networks names pserver1 till pserver 6.
If resource group pserver1 and pserver2 are hosted on Node1, and I access sharename \\pserver1\, I will also see the printers that are installed on pserver2.
This causes a lot of confusion for the administrator who need to maintain and configure these printers within our enviroment.
Is there any way possible to block visibility from other print groups when u access a specific network name?
Thank you so much!
ASKER
Hi there,
The issue is we currently have more print groups then nodes. Does this mean this problem is unsolvable?
The issue is we currently have more print groups then nodes. Does this mean this problem is unsolvable?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The only way to do this host one pserver on one node and the other one on the second node.
Use the preferred node feature to keep the groups on their respective nodes and failback to move them back if they happen to be on the same node, say after an outage.