|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by jdroger2 in Miscellaneous Software, Remote Desktop/Terminal Services
One of our terminal servers no longer removes user's printers reliably when they logout. printers stay listed under printers and faxes, and often cannot be manually deleted because of a message that the printer could not be found. The biggest problem this causes is that it eventually begins preventing users from bringing their printers into their session with them. The only way to clear out the bad printers is to reboot the server.
We need to know what's causing this and how to stop it. It is likely related to a secondary issue where some user's printers have begun showing up as Terminal Services Fallback printers - previously these printers simply would not have been brought into the session. We did not enable the TS Fallback Printers in the GPO, and have added a GPO to disable them that does not seem to be working, though the GPO modeling wizard indicates that the GPO is applying properly. Is loopback processing required to do this?
There is no Citrix involved, just straight Windows 2003 Terminal Services
20090824-EE-VQP-74 - Hierarchy / EE_QW_3_20080625