2008 Terminal Server and Print Manager
I have just recently upgraded both of my DCs to 2008 Enterprise and also introduced a 2008 Terminal Server. One of my DC's is holding the role as Print Server and has Print Manager fully configured. All of my users desktops are pulling the proper deployed printers on their local machines but when they log into the 2008 TS it just pulls every printer that is installed on the print server. It is not pulling redirects from client logins, just every printer that is installed on my print server regardless if it is deployed or not to that users OU.
Any help?
Any help?
ASKER
yes but it still installs every printer on my print server, every time someone logs in as well as uses rediredted printers. Any other ideas?
If you have the printers on the clients then the printers will come up.
ASKER
Yes I know the printers will come up. They come up as redirects as well as the printers installed on my print server. Here is the issue, redirects and local installs work but the TS will not pull what is deployed through print manager. All it pulls through is everything that is installed on the print server.
If you have a GPO deploying these printers this would cause the problem. Printers do not automatically get installed you must install them manually, terminal server redirects, or through a GPO
ASKER
Understand that as well that is why I am posting this. I have created a new OU, new GPO, and new user with nothing deployed to it and it still shows print server printers. I have even gone into TS Configuration Properties and disabled client printer connections. Another thing is that the printers that are being pulled up are not even the printers that I have locally installed on my client workstation. They are the ones that are on my print server.
User is under new OU? I would disable all GPOs on that OU with the terminal server there.
Understand printers do not just appear unless they are deployed or redirected so something is deploying the printers
Understand printers do not just appear unless they are deployed or redirected so something is deploying the printers
ASKER
Understand printers do not just appear unless they are deployed or redirected so something is deploying the printers
I do understand that something has to be deploying them some way. That is why I am asking everyone, I have made all the proper adjustments even those mentioned and recommended by yourself and this server is responding the same. I just dont get it.
I do understand that something has to be deploying them some way. That is why I am asking everyone, I have made all the proper adjustments even those mentioned and recommended by yourself and this server is responding the same. I just dont get it.
So, you have user and terminal server in new OU with Block Inheritance applied on the OU level with no gpos being deployed, right?
How about login scripts any being deployed?
How about login scripts any being deployed?
ASKER
That is correct block inheritance is applied on both and there is a logon script but nothing that applies to printers.
If you delete them do they come back?
ASKER
No I can not delete them it is saying that access is denied.
ASKER
even going to the console and logging as Administrator brings all printers from a domain Print Server. There is nothing in local group policy from what I can see either. Any help?
ASKER
Sorry also meant to mention that I was logging in as local administrator on previous comment.
Once printers are installed then you should see them for local admin as well.
So, if you login with domain admin you still can't delete?
So, if you login with domain admin you still can't delete?
ASKER
thats correct I can not delete these printers. they install on every kind of session that is established on this server. whether it is local or remote, local admin or domain admin the printers from the print server install and I can not remove them
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Cool. Glad you figured it out. Registry deletion should do it
ASKER
Found the resolution myself.
http://blogs.msdn.com/b/rds/archive/2007/04/26/introducing-terminal-services-easy-print-part-1.aspx