Solved

Terminal Server trying to isntall Network Printers

Posted on 2011-02-15
5
483 Views
Last Modified: 2012-06-27
Our Domain users get networked printers installed via login script. When the log on to the Remote Desktop Server it also tried to install the network printers. On our 2003 Terminal Server this does not happen. So i assume it has to do with a Group Policy settings. Can anyone point me to where this is controlled in GroupPolicy for TermServer?

THanks
SJMP
0
Comment
Question by:sparkis
[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
  • 3
  • 2
5 Comments
 
LVL 10

Accepted Solution

by:
kgreeneit earned 500 total points
ID: 34897829
Hi there, from within Group Policy Management Console on the Organisation Unit (OU) that the Terminal Server is located in, select the 'No Override' (Block Inheritence) option and see if this resolves the problem.

It is most likley that you have specified the printers to be mapped using a policy for the user accounts as well as possibly the Default Domain Policy.

Here is a couple of links to look at based around Group Policy and printers:

http://www.windowsnetworking.com/articles_tutorials/Managing-Printers-Group-Policy-Part1.html

http://www.windowsnetworking.com/articles_tutorials/Managing-Printers-Group-Policy-Part2.html
0
 

Author Comment

by:sparkis
ID: 34897974
KG
Thanks I selected Block Inheritance. But I still see the Default DomPol as the first precedence. Anything I can do to push the change through, since it seems to not be happening on its own.

Not sure if this matters - but as soon as I selected Block, I got a Blue exclamation icon on the OU within GPMgmnt.
0
 
LVL 10

Assisted Solution

by:kgreeneit
kgreeneit earned 500 total points
ID: 34898322
THe Blue Exclamation icon is what you want to ensure that 'Block Inheritance' is enabled.

If this is enabled and the Default Domain Policy is still coming through, then the Default Domain Policy is more than likely configured with the 'Enforced' or 'No Override' policy setting.

This setting will need to be removed from the Default Domain Policy before the 'Block Inheritance' setting can take place.

Hope this helps!
0
 

Author Comment

by:sparkis
ID: 34898336
you are the man. Thanks
0
 
LVL 10

Expert Comment

by:kgreeneit
ID: 34898533
No problem - glad I could help!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

751 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