Solved

Server 2012 Print Management - Printers no longer Deployed?

Posted on 2016-10-03
2
13 Views
Last Modified: 2016-11-09
We have a server 2012 R2 environment with a dedicated print server.  When deploying printers using "Deploy with Group Policy", the existing deployments normally appear after a few seconds.  This changed a few weeks ago.

Existing deployments no longer display in the deployment dialog and the "Deployed Printers" sections shows only recently deployed printers.   It seems that Print Manager is no longer reading existing GPO's.  With close to 1000 printers in our system this is a huge problem.

Does anyone have any ideas?  I suspect a recent update is the cause.

Brian Pecora
Bridgeport (CT) Schools
0
Comment
Question by:bripct
[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
2 Comments
 
LVL 16

Accepted Solution

by:
Carol Chisholm earned 500 total points
ID: 41826608
There was an update a short while back that stopped Group Policies working if they were filteres to a specific group of users.

Solution is to update your policy
Simple solution is you should add the Active Directory computer account to security group or give Domain computers group / Authenticated Users to read permission to fix this issue for all the domain joined computers, steps are
Open GPMC.MSC (Group Policy Management Console)
Select the policy
on right site of the console, select delegation
Add the Authenticated Users and select read Permissions
Add the Domain Computers and select read permissions


http://www.windowstricks.in/2016/06/group-policy-not-applyingworking-patching-gpo-permission-issues.html
0

Featured Post

Now Available: Firebox Cloud for AWS and FireboxV

Firebox Cloud brings the protection of WatchGuard’s leading Firebox UTM appliances to public cloud environments. It enables organizations to extend their security perimeter to protect business-critical assets in Amazon Web Services (AWS).

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
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 walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

726 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