Windows 10: Printer install error windows 10 / windows server 2016

I am getting problems with printers on windows 10.

I have a DC windows server 2016. I installed all printers. Shared them. Add them in GPO ...
Everything is working fine ..... monthly updates ....


I use HP universal printer drivers as the HP9040dn printer does not have specific drivers anymore.

At one point somebody wanted a change in a printer. Add a Sticker from a specific Tray, with the good options.
It worked for a while. Somehow it's not working anymore. I wanted to update the driver but it gave a printer error.
I wanted to return to the old printer it gave an printer error.

Error:
Printer settings could not be saved
This operation is not supported.


I wanted to return to the old dirver ..... same error?

I can only go back to the OLD OLD printer driver specific for the 9040. But than you can only print. You can't create printing shortcuts etc.

I updated the servers, I updated the computers ..... no way I can reinstall the universal drivers.
When I add printer ... select IP adres it can't find anything, it does not recognize the printer.
Not on the server, not on a windows 10 client.


I want to go to properties. advanced, select old driver with printing shortcuts ..... but it does not allow me to.

Server has been updated as well.

:)

 

Windows 2016 Server Error 0x00000003 when connecting printer to workstation

Windows server 2016 has two printers installed VIA TCP/IP.

Workstations include Windows 7 and Windows 10 machines all x64 bit.

1st printer is a Xerox Work Centre 7830 with a Work Centre 7830 PostScript Driver installed.

The printer is installed on the Windows server and prints from the server. I have shared the printer on the server and have listed it in the directory. There are additional drivers that should allow the printer to connect to a x64 device. When I try and connect
to the printer through the directory it finds the printer,

starts to look for a driver and then fails with error code 0x00000003. This happens on all x64 bit machines both Windows 7 and Windows 10.

The 2nd printer, is a SHARP MX-C300P that is installed on the 2016 server, and shared over the directory. It has a generic Microsoft PCL 6 driver. When I try and connect the printer to a windows 7 machine,I get the same 0x00000003 error. When I try to connect
the printer to a Windows 10 machine the printer connects just fine. I have looked over all of the settings and everything seems to be working.

I have Googled this error and nothing has worked to fix it. I can provide more information but really need this fixed.

Thanks

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

Windows 10 GPO Printer Add issues

A total shot in the dark since this is a very specific issue to our environment, but here it goes...

A little background on this issue, my school district is moving to windows 10. We partially deployed Windows 10 LTSB to some of the labs in the district. We are seeing sporadic issues with our Group Policies deploying printers. We have below 50% success rate with printers actually installing on the Windows 10 client machines.

Thinking it was an issue with LTSB, we downloaded and installed Windows 10 Education version 1709 on a test VM and joined it to the domain. I then applied GPO’s from 4 different servers. 3 Physical Server 2012 R2 servers and the original problem Server 2012 R2 VM Server.

What I found was the same inconsistency after rebooting the Win 10 Edu Test VM. I am getting the same Event 513. See below:





I am 100% sure the naming is right because I can manually add the same printer using the \\SERVER\FerLib path. All printers that fail to add have the Event 513. I am also going to post this on other forums.

We are only seeing this on student accounts which are domain guest accounts, meaning their profiles are non-permanent. We do not have the option to turn them into regular users per district policy. If you need more info that I omitted please let me know. We are getting desperate.

Thanks!