Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Network printer becomes inaccessable randomly in 2012 R2 RDS sessions

Posted on 2016-08-30
1
Medium Priority
?
84 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

688 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