I've read the Help article on how to do this, as well as https://repost.aws/knowledge-center/workspaces-configure-windows-printer.
I've followed the troubleshooting steps here: https://repost.aws/knowledge-center/workspaces-troubleshoot-windows-printing, and all of them seem to pass (except there's no directory at the spot where printer_host.dll is supposed to show up; I assume the layout changed). When I print a test page, it gets sent to the queue (which is ready) and rapidly disappears, and then nothing happens on the (physical) printer. I can of course print fine from the host machine.
The printer shows up fine in the list of printers when I choose to print a document. (If I open the Windows settings and remove it, it is not in the list until I try to use it from an application and select "more options" or whatever, I forget the exact sequence.) When I ran the (Windows) troubleshooter on it, it suggested making it the default printer, so I allowed it to do that, but it did not have any effect on my ability to print.
Several resources suggest that PCoIP printing "might" require local driver installation. I did have this working with a previous macOS machine (albeit on a lower version of macOS), and did not install a local driver (or else it would still be there, as the Workspace is the same one I was using).
I tried installing the local drivers from Canon on the Windows Workspace just as an experiment but it wanted to find the "device" (the printer, apparently) on the network and of course it's not "really" there.
I'm not sure what to try next.
AWS OFICIALAtualizada há 2 anos