First off, I have been familiarizing myself with the various Xerox Global Driver deployment/preconfiguration options (Preconfiguring V3 Product Specific Xerox Print Drivers for Windows & XML Configuration Editor for Print Drivers). Both come close to what I want to do, but do not support editing the feature in the way we want. Is is possible to set Bidirectional Communication to Manual and prepopulate a TCP/IP address during printer deployments?
To clarify our circumstances, we are using prnt server software in a Windows Failover Cluster. This prevents normal Bidirectional Communication from working correctly. This is a 3rd party software limitation currently with no workaround. If I can pass a manual TCP/IP address into that setting, it would allow the driver to configure to the cirrect device and add alll the correct installable options automatically. Attempts to add these, manually have only been partially effective.
This is a bit out of my depth admittedly. But this has resolved some similar issues on the Failover cluster side. It might be enough to get you running.
Running a 2008 R2 cluster,. In that scenario, you have to remote into the cluster using the “mstsc.exe /admin” argument to log in without bringing local printers with you, then open the Failover Cluster Manager. Then, highlight the print service, and on the far right, choose “Manage Printers” and you’ll see the Print Management functionality you expect to see. If you open the Print Management console directly on the host, you won’t see devices that were set up on the cluster.
With that information, I was able to set up a “test printer” on the print server that points to the printer, and successfully imported the 32 and 64 bit drivers.
This was the method used in one case to modify the Xerox Global driver on a failover cluster where while the 32bit clients all worked as expected, the x64 bit had no finishing options (Bi-Di)
While logged into the server there was nothing in the “print Management Console”, no ports or printers at all, Nothing in “Devices and Printers” at all, and from the server Start/run \\127.0.0.1 showed absolutely nothing shared, yet from any client PC there were about 30 printers and hundreds of shares.
Thanks for the response on how to manage printers on a failover cluster resource. As stated earlier, there is a third party limitation causing BiDi communication to fail. It's not that I'm trying to log locally to the host node to manage the printers. So normal BIDi communication is not an option for us unfortunately. What I was asking was whether or not there is a connand line argument or a tool out there that can configure BiDi on the local workstation to the print device directly.
For example, there is a Global Driver XML configuration tool that is able to configure driver settings on the workstation, which allows me to enable or disable BiDI as a default. If there was another argument in the XML I could add manually that would enable, set to manual mode and add an IP, that would be ideal.