I'm curious if anyone has experienced problems with UNC path connectivity after moving over 500 printers from Windows Server 2016 to Server 2022. Specifically, when users attempt to connect to printers via UNC paths, the installation fails, but using TCP/IP seems to work just fine. Any insights would be appreciated!
6 Answers
When we did our migration, we found that using the FQDN in the GPO made a big difference. Instead of just using \\server, we used \\server.domain.local.
You might want to consider switching to V4 printer drivers for better compatibility.
What error messages are popping up for the users? Don't forget to check the event viewer on both the server and client sides. Consider using package-aware printer drivers, and look into the point and print setup too.
From my experience, I encountered similar issues. For example, the Printer Migration Events log showed errors during the restoration of print queues. Double-checking event viewer logs on both ends is essential; error messages could point to driver issues.
What kind of troubleshooting steps have you tried so far? Checking your endpoint error logs could reveal some insights. Also, what do you see for the print server display lookup?
Did you upgrade an existing Server 2016 machine to Server 2022, or did you set up a new server and use the migration tool? If it's a new setup, make sure there's not a 'point and print' policy that needs updating with the new server's name so the clients can install the printer drivers correctly.
This is a new server, and the point and print policy is enabled.
Also, it's a good idea to use both the hostname and FQDN since users often forget to input the full address.