Hi guys,
I have had this issue with a client of mine for a few months. The client is using a locally installed USB printer but using ThinPrint to redirect it to their RDS session.
The original issue was that she could not send anything to her printer. The only way to fix this was to re-boot and then all of the spooled jobs would come out.
I have tried the following:
-re-install the printer
-update the firmware
-changed from USB to network printer
-re-install thin print
-re-install windows
-replace printer
-re-create RDS profile
Nothing worked except for the profile re-creation on the Terminal Server. But this was only a fix for a few days and now it does not work at all. It will not even spit out the spooled documents after a re-boot.
I have also brought this to he sr. tech and he has no idea whats going on.
Can anyone proved any more advice other than replacing her physical tower?
Thanks all!!
I have had this issue with a client of mine for a few months. The client is using a locally installed USB printer but using ThinPrint to redirect it to their RDS session.
The original issue was that she could not send anything to her printer. The only way to fix this was to re-boot and then all of the spooled jobs would come out.
I have tried the following:
-re-install the printer
-update the firmware
-changed from USB to network printer
-re-install thin print
-re-install windows
-replace printer
-re-create RDS profile
Nothing worked except for the profile re-creation on the Terminal Server. But this was only a fix for a few days and now it does not work at all. It will not even spit out the spooled documents after a re-boot.
I have also brought this to he sr. tech and he has no idea whats going on.
Can anyone proved any more advice other than replacing her physical tower?
Thanks all!!
Facebook
Twitter
Instagram