02-08-2010 03:00 AM
We recently create a VCS Print Server and generally it works OK except for publishing in AD. The basic creation process was build VCS, create a cluster, use the print server wizard, add and share some printers, then in windows go to the printer and tick 'Publish in the directory'. This WORKS for the first node and in AD I can browse to the node and see the printers underneath. The problem comes when switching to any other nodes - the printers all come online OK but publishing doesnt work, reporting many events in the event log saying that the print queues couldn't be updated. Tech support suggested this might be a permissions issue in our AD environment so I created a test setup with a completely default AD domain controller plus two default VCS nodes and the issue still occurs.
The windows error is 'Failed to publish property xyz at LDAP://container-for-node-1/ Error 80070005
My thinking is that the printers should be published under the virtual print server name rather than the actual nodes but this doesn't seem to be the case. The first node always works (when it creates the published objects) but any subsequent nodes fail (when they try to update). Any ideas please?
Solved! Go to Solution.
02-10-2010 04:29 AM
02-08-2010 06:23 AM
02-08-2010 08:32 AM
02-08-2010 10:55 AM
02-08-2010 01:29 PM
02-10-2010 01:04 AM
02-10-2010 04:29 AM
02-10-2010 12:34 PM
OK to I've updated to the latest version on the test cluster and confirmed that the problem still occurs. Then taking your advice Dave, I added both physical nodes to the Printer Operators AD group and the errors no longer appear, so definate progress. I think there is still a problem though, just on the fact that a physical node holds the print queue object rather than the virtual - what happens if that node goes down and the queues dont work properly, or if the queues are on the "passive" node for an extended length of time might the queues go stale and get pruned? AD policy defaults to not do this but it seems less than ideal?
Appreciate you thoughts on that if you could spare a few mins. Thanks hugely for your help so far! I have a case active with support so I'll let you know any updates from that too.