I don't know if windows updates or server updates fixed it, but the issue went away on it's own.
Was there ever a solution?
It seems the issue occurs due to pushing the printers out via Group Policy. They work for a few days, then "something" happens to corrupt the driver. Oddly enough it only happens to a select few users. Sometimes it happens once and deleting/reconnecting fixes it. Other users, one comes to mind in particular, it happens ALL the time. I don't get it.
We used to push out printers via user scripts and it worked fine. However it's tougher to manage that way.
not sure this counts as help.. but I have just done an instalation and config on my environment... Please take a look a the video.
Well this occurs on every model - 4250, 5755 and now the D110. The weird thing is the D110 doesn't even use the GPD.
Could this be a server 2008 issue? This is the first time we've decided to distribute printers via group policy vs simple scripts. The scripts were always a bit of an issue and GP just made sense, but this issue is causing us a lot of grief.
Judging by your image I would say the driver is not even picking up the printer settings... even when pointing the printer model.
I have also noticed that the printer you are working with is D110. To be honest I am not familiar with this model, as I work with european models, nevertheless running a quick search on Xerox global I can not find the GPD reference on this printer.
I base my argument on the fact that:
Obviously it is recognized by the GPD because its part of the listed printers, but I just wonder if this will provide full functionality..
If you install the dedicated driver do you have the same problems?
This is what it looks like btw
yes sure, here it is
Thanks - do you have the x64 link to that version as well? We use both