Solved

Terminal Server trying to isntall Network Printers

Posted on 2011-02-15
5
482 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

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

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

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
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…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

756 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