- #Parallels client printer problems how to
- #Parallels client printer problems drivers
- #Parallels client printer problems driver
- #Parallels client printer problems code
- #Parallels client printer problems windows 7
This is fine for us because these are all identical VMs.
#Parallels client printer problems driver
To stop this behavior we adjusted a registry setting that made Windows stop looking for driver updates.
#Parallels client printer problems drivers
Our timing was imprecise because we saw users who remained logged in through the month change as well as the first falling on a weekend or low print volume day.įix: (I wouldn't call it a resolution) Microsoft was able to determine that the issue was that Windows was checking for new drivers for printers for each login after the first of the month. If you were logged in when the month turns - your printers will be fine until you log off and return. It does not matter if you use the Easy Print driver or if the server uses a driver to match the client. Every month, on the first of the month - any users who login will no longer see client created printers. UPDATE: After further investigation and work with Microsoft we have found that his issue occurs on or around the first of the month (time variance possibly tied to UTC if the server has timezone redirection enabled). We have experienced all of this and have applied all updates to clients and servers and we're still experiencing issues with redirected printers disappearing on occasion. " Which claims to be resolved by KB4517389
#Parallels client printer problems code
KB4524147 comes with its own known issues including "The printer spooler service (spoolsv.exe) might close or error in jscript.dll with exception code 0xc0000005 causing the print jobs to stop processing. Only part of the print job might print and the rest might be canceled or error. " and a Workaround of "This issue is resolved in KB4524147. Some apps may close or generate errors when the print spooler fails and you may receive a remote procedure call error (RPC error) from some printing utility or printing apps. There were a number of printing related problems caused by client and server updates in September that started with: kb4517211 - which has the known issue of "The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing. Thank you for your reply! Please give me hope! When did it resolve itself? Recently? Are you on 2016 or 2019? I do recall a very similar issue with 2008R2 RDS Servers that generated an eventlog Error 7011 "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the _ service." from Netman, UxSms and umRDPService, but as I said, I see no such errors in the event logs.Īlso (I don't know if this is significant or not), from time to time (when redirected printers are working) the printers do not show up in the Devices and Printers but they are visible if you launch (or create a shortcut to) C:\Windows\explorer.exe :: and they are visible from within applications' print dialog box.Īny advice or tracing or additional logging that I can dig into? Has anyone else experienced this with 2019 RDS Servers?
#Parallels client printer problems windows 7
*Most of our clients are on various Windows 10, but we see the same thing with Windows 7 and 8.1 clients *When it happens, it happens to admins and users alike *We've tried to prefer the easy print driver (by GPO) and we've tried it with drivers that exactly match the client with no change *Restarting the spooler does not help
*After rebooting the RD Server the issue clears and clients can print again for an inconsistent period of time (days or weeks)
*The log TerminalServices-Printers is completely empty (This is where we see mismatch drivers and such on Server 2016) *I see nothing suspicious in any of the logs indicating that there is any issue with client printer creation / redirection The only thing that resolves this is a reboot of the RDS server. From this time forward all clients who logon will not have their local (redirected) printers available to their session, but clients who have logged on before this time will continue to work.
#Parallels client printer problems how to
I am hoping to get some input from anyone here who may have some insight into the most annoying issue involving "redirected printers." If anyone has any insight about how to fix these issues or any additional logging options that I may be missing out on, I would appreciate any information.įrom time to time (I have not recognized any pattern yet, but about once a week per server) client created (redirected) printers cease to be connected when a client logs on. For the most part they are performing on par with the Server 2016 RDS servers (updates are MUCH faster) but we have encountered a number of minor issues (things that just don't seem finished or polished) and a few bigger issues and inconsistencies that are causing some headaches. Over the last several months we have deployed a dozen or more Server 2019 Remote Desktop Servers.
0 kommentar(er)
