We have this problem since 3 weeks ago, every time we try to deploy the printer from windows Server 2012 to Windows 7 gives ther error : "a policy is in effect on your computer which prevents you from connecting to this print queue. Please contact the administrator".
We remove both the KB3170455 and KB3197868 from the windows 7 Client, ther Server 2012 doesn't have any group policy running, also changed the driver from the proprietary to the global print driver and have the same behavior. I've checked the local gepedit.msc of the client has some people sugest in some websites and change as they sugest.
Its dificult to understand because all the computers with windows 10 add the printer without any problem. Our client is a big company spred thrue europe and is migrating the servers. We ara concerned because is this happens in all they migrate we have to install hundreds of computers localy.
Can anyone help us.
Thank you for using the Support Forum. The error you are getting is from the server side of the environment. You would need to check the setup on the network side for a restriction. Make sure you are using the latest driver available. Without knowing which printers you have it is difficult to be more specific but also make sure the machines are on the latest firmware version. Please consider contacting your support centre for further assistance.
The key question is what driver are you using, because the Class driver (Server 2012 default) and the V4 driver (Xerox recommended for 2012) cannot be used in Windows 7 and will display that message because v4 and class drivers are Windows 8 or higher and not backward compatible.
I have the same issue and the issue seems to be caused with some windows updates. Originally there was a windows update KB3170455 and removing this update on the windows 7 fixed the issue. But then other updates keep released since and couple of others that have caused the issue are KB3192403 and KB3197868
I did open a case with Xerox support and I must say I was very disappointed with the help and knowledge received. I was told to contact Microsoft to resolve the issue.
This issue seems to only effect Xerox printers. We have lots of HP and Brother printers and these printers are not affected, so this should be something that needs resolving by Xerox.
And just to confirm, we're using Type 3 drivers and printers are shared from Windows Server 2012 R2. We have Xerox 6600DN and 7100N.
This issue is still ongoing and causing lots of headache for us now so would be nice if someone can provide a resolution to this.