• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

Local printing using terminal server 2003 suddenly stopped.

Windows 2003 Terminal Server  was virtualized 60 days ago in preparation for  move to new Windows 2008 R2 Terminal Server. Virtualized server has been working great but has suddenly stopped picking up default local printers of terminal server users when they login. No local printers are showing up as available printers (as sessions) in the print queue. This terminal server has been running flawlessly for three years and every user has had a local printer connected to their remote PC which has been working with the terminal server for those three years. Suddenly today - no local printing is working through the terminal server at all. The only thing that I noticed was that the registry DWORD value "FFFFFFFF" set for "FilterQueueType"  (that I had originally modified to make printing work) was "missing"  from the registry. I have know idea how that would have happened. I added it back in but no fix. Makes me wonder what else happened to the registry. Nothing else had been changed - really. How can I get local printing going again without having to restore virtualized server?
0
ponchoindy
Asked:
ponchoindy
  • 3
  • 2
  • 2
1 Solution
 
arnoldCommented:
Could it be that a GPO restricting the attachment of external printers to terminal server is what the issue is.
http://www.vistax64.com/server-general/268667-prevent-attach-local-printers-via-remote-desktop.html
0
 
ponchoindyAuthor Commented:
We checked that and even denied GPO in total just to make sure and it is not the problem. Nothing in the event log even shows that terminal server is even attempting to try and find a local printer.
0
 
arnoldCommented:
When you say local you mean local to the RDP user's system or local to the terminal Server?

i.e. usera establishes an RDP connection to the VM terminal server. Is part of the RDP includes a local user printer? And that does not get created?
Or is there a GPO that deploys per user printers and that is not processed by the VM terminal server?
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
johnb6767Commented:
Hate to state the obvious, but after adding "FFFFFFFF" I am assuming you rebooted?

How to redirect the default printer of a Terminal Services client to a Windows Server 2003 Terminal Server session
http://support.microsoft.com/kb/911913

Might try forcing it......
0
 
ponchoindyAuthor Commented:
Virtual server continued to fall apart (MAPI failures, storage errors, etc..) Registry was somehow corrupted and could not be made to behave after numerous attempts. Had to restore TS to prior date. Still do not understand what happened and find it interesting that it appeared to all start with no local printing through terminal server. One Lesson learned: Keeping users locked down from terminal server changes (though they complain) and writing data to other servers pays off. Thanks for everyone's participation and help.
0
 
johnb6767Commented:
Glad you are back up and running...
0
 
ponchoindyAuthor Commented:
Reinstall was only solution which is what I was trying to avoid.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now