I have having an issue on our Windows Server 2016 print server. The server has worked perfectly up until a week or two ago, but has now started behaving strangely. Nothing, to my knowledge, has changed in the server.
A small bit of important background:
These are Amazon hosted servers (EC2) running the print server, and Amazon workspaces trying to connect to the printers via the server.
I have reached out to Amazon for multiple hours of troubleshooting to find the cause, but they are now convinced it is something in Windows.
Any time a new workspace tried to connect to the device automatically, I get the error "Before you can add this printer, you need to install a driver for it. Find the driver on the web or use the disk that came with the printer, and then try again."
The inconsistency of the issue is also a factor. Two workspaces using the same image will act differently, one downloading the drivers automatically, and the other bringing up the error. That being said, it is the exception for a device to work automatically and not the norm.
we started by confirming the Workspaces involved could reach the Print Server running on an EC2 instance. This was successful, and DNS was also working as expected.
also disabled webroot to see if that would resolve the issue, but the issue still occurred.
We then attempted to manually add the printer by using the unc path \\exch16. This did show the printer that are being shared, and when selecting to connect.
*note: We were prompted for permission to install the driver. You proceeded, and the drivers installed and the printer would then connect successfully.
If anyone has any idea of what is happening, please let me know.
*Note that we are trying to have this seamless and automatic. The workaround above works, but is not the ideal setup.