Print Servers - Unable to publish in AD
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?
Node 1:
AD:
Node 2:
- Hi ukDavidC,
I don't think an SP1 upgrade will resolve this. Neither will changing LanMan attributes.
Your printQueue object is published under the physical node container in AD and therefore this is a permissions issue on the second node where the printshare was NOT created. The computer account for the "passive" node does not have permissions to the printQueue object which was created under the "active" node's container.
I assume you are using Windows 2003 as I believe the behaviour has changed in Windows 2008 to publish printQueue objects under the virtual name container in AD but for Windows 2003, print shares are published in AD under the container of the physical node where the share was created.
You could add both physical node computer accounts to the built-in "Print Operators" group to resolve this. Otherwise, please work through support to request a change to the behaviour of the PrintShare wizard on Windows 2003.
Dave
