Thanks Joe, this looks like a resolution to the problem installing a signed, package aware, print driver. What about the problem installing a non signed, package aware print driver? Is this still with Microsoft or is this now for Xerox to issue up to date drivers?
At this point it would be both have an issue.
Is Xerox willing to stand by the products that are not under development any more (not making them money) and make a driver and pay to have it signed, or is MS willing to allow the installation of unsigned drivers to help out their customers.
I personally don't see either one happening, but I am pretty low on the totem pole (And I post here in an un-official capacity, I don't get paid to do so). Only time will tell I guess.
If Xerox makes an official statement in some way I will post it in this thread, my guess, if they do, is that they will say you can use the Global Print Driver with most machines in those cases. It does officially support a lot of devices, and un-officially supports even more ala Basic Prit mode (No finishing) or Workcentre color and BW (Does have limited finishing)
We are experiencing this on 2008R2 servers, do you have any recommendations for a hotfix for 2008r2 Servers?
I haven't seen any reports of it, I just searched and found no reports of it so if you have the exact issue you may be the first reporting it, or I just don't have the ability to find other reports.
I do work for Xerox in 2nd level, but there are many 2nd level teams, and many locations, and I am far removed from Engineering, so it is entirely possible this has been reported and I just can't find references.
I made this post originally because I am a co-worker of the author of the listed documents (he worked the issue on our side until it was handed off to MS), no such work is being done by him now.
We're having the same issue on Server 2008 R2. Been told to install the MS hotfix- except there isn't one.
Since it is an MS issue, you need to tell them, Xerox has no ability to make a Hotfix for their OS.
You know its all well and good to say its microsofts fault and xerox has nothing to do with it but meanwhile its the end users and admins that screwed over waiting for a more permanent solution. As someone affected by it across 18 sites with all sorts of different models of xerox devices it seems to be a never ending problem. We pulled 3170455 when we discovered it to be what caused our nightmare affecting hundreds of users and now it seems to have popped straight back up again with another recent patch microsoft has released. Now all our users are getting error 0x80070bcb and we again have to pull back patches yet our other devies in the fleet from HP and Canon seem to chug along without a problem. Maybe this will help some people when they google the error to know they are not alone