Solved

Network printer becomes inaccessable randomly in 2012 R2 RDS sessions

Posted on 2016-08-30
1
44 Views
Last Modified: 2016-09-12
I've recently moved about 40 users onto some new Windows 2012 R2 RDS infrastructure. They are all logging onto their RDS sessions from thin clients with no local resources attached (printers, drives). The network printer connections were rolled out via GPO. The printer shares are from another 2012 R2 file and print server. Roaming profiles and also folder redirection are in the mix if it matters.

The issue we are running into is that every morning I'll have one or two people call me about their broken network printer. The way the printer becomes broken is particularly confusing to me. I've never seen this type of issue before. The user is unable to print to the printer but the properties are still accessible. In the windows "devices and printers" control panel it looses its mini icon denoting it as the default printer. Setting any other printer to default results in no change. In powershell, listing the printers does not show the failed printer. Trying to add a printer via powershell will also result in no change. You can not remove the printer with powershell either as it isn't able to be found in its failed state.

How I have been fixing the issue so far is to remove the printer via the control panel UI. This causes another printer to be selected as the default printer and the mini icon shows up again. Finally, I issue the command in powershell to re-add the failed printer. The UI can be used as well, I just prefer powershell.

Here is a screenshot of the printer in its failed state.
Failed printer screenshot
Does anyone know what could cause an issue like this or how to diagnose it further?
0
Comment
Question by:DonovanV
1 Comment
 

Accepted Solution

by:
DonovanV earned 0 total points
ID: 41794650
Here is the solution I've come to on this issue. I've removed the single printer deployment setting from the group policy governing the users in question. Its been a week without incident and it directly corresponds with that change. I can not explain how that helped though. The printer setting was a "create" entry. From my reading of how the different printer deployment options work, that entry should never have taken action as the printer was already present for each user. That said, here I am, problem free.

If anyone has any insight it would be appreciated. Dealing with this issue is making me think twice about group policy. I may be looking to powershell for printer deployment in the future.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now