For example, if you have a Okidata driver installed To be clear, if you disable RD Easy Print via group policy on the server, RD Easy Print will still be used to auto-create client printers unless there is a matching driver installed on the server. Is it not showing up with redirected after it, or is it not showing in your screenshot for some reason?
In your screenshot it does not have (redirected x) after Okidata ML 320. TSxxx CLIENTPCNAME: PRNxx:# x Printername (redirected x) Normally you should see something similar to this: The correct dynamic TS port will be assigned automatically. You should not have to manually pick the port for the redirected printer. I have disabled the RD Easy Print policy and forced a policy refresh. Neither is the brother printer but it IS printing. The 320 is NOT being auto-created on the server. Yes, i got the printer installed by using the windows update buttonĢ. So the M元20 Turbo is plugged into the client pc with USB cable.ġ. Usually means the name of the server driver does not exactly match the name of the client driver and you need to create a print driver mapping file. Did you verify on the server that the correct driver is being used for the auto-created printers? You do this by right-clicking on a auto-created printer and choosing Printer Properties, Advanced tab. Did you try the three different versions of the driver?ģ. Did you install the latest Okidata M元20 driver that is available via windows update? When you Add printer or Add driver on your server there is a windows update button on the driver selection window that will download the latest.Ģ.
0 kommentar(er)
