Print Problems

[GRitchie]

Hello,

I'm configuring our new printer server on Server 2012.

One major problem so far, when adding the printer on a client, it asks to install the driver (as normal - which ideally I would like to get rid of, as this requires administrative rights)

However, it gives me the error below, and then stops the spooler?

If I restart the spooler and try again, it usually adds the printer, but this isn't a sensible fix really!

 

 

Any ideas?

[6Foot2]

It seems that others have had the same problem:

 

Link 1: error code 0x000006be windows cannot connect to printer when trying to - Microsoft Community

 

http://i.snag.gy/pbdgR.jpg

 

Link 2: Error message when you try to connect to a print queue in Windows Vista or in Windows Server 2008: "Windows cannot connect to the printer. Operation could not be completed (error 0x000006be)"

 

http://i.snag.gy/PrgrJ.jpg

 

While this talks about Vista, Server 2008, Server 2003 and XP and you are working with Server 2012 the error seems similar enough to have a look at this solution?

[beancole]

Not a solution for the problem but point to note you can allow users to install print drivers without admin rights there is a GPO for it cant remember it off the top of my head but it is possible. Im following the thread so when I fix my latest meltdown I will have a look into it.

[Davit2005]

Not a solution for the problem but point to note you can allow users to install print drivers without admin rights there is a GPO for it cant remember it off the top of my head but it is possible. Im following the thread so when I fix my latest meltdown I will have a look into it.

 

The policy is under Computer Policy > Administrative Templates > System/Driver Installation > Allow non-administrators to install drivers for these device setup classes. Enable the policy and add the driver class {4d36e97d-e325-11ce-bfc1-08002be10318} .

[beancole]

The policy is under Computer Policy > Administrative Templates > System/Driver Installation > Allow non-administrators to install drivers for these device setup classes. Enable the policy and add the driver class {4d36e97d-e325-11ce-bfc1-08002be10318} .

 

that's the badger