Printers not mapping for some users

[LinkZ]

I've been pulling my hair out for a few days trying to solve this and i'm running out of ideas. I am having problems with users printers either a) not being mapped on login b) being removed while logged in c) getting printers mapped for each computer they login in to and having these printers stay on their account rather than being removed on login and only show the rooms printer.

 

I have a group policy setup which contains all the printers in User Config > Preferences > Control Panel Settings > Printers which contains all the printers (with the action set to update) and item level targeting so only the computers in a specific OU get given the printer (these OU's are based on the machines location so we have a separate OU for each classroom). I have a printer set to order number 1 which has the 'Delete all shared printer connections' option set to try and counter the issue of accounts picking up every printer they get connected to. The group policy also has Computer Config > Policies > Administrative Templates > System > Group Policy > Configure printers preferences extension policy processing set to not apply during periodic background processing. This group policy has been set at the top of the domain so it applied to all computers and users.

 

The printers not being mapped on login seems to be contained on a user basis as I have 2 test accounts, 1 where the printers do not get mapped at all and I can't find anything in the event log for it, and another test account which gets the correct printers on several different computers. I can't find anything in the event log that says why the printers weren't connected so i'm a bit stumped.

 

We're using roaming profiles for our staff accounts which are the accounts being effected.

[LinkZ]

Ok a bit of follow up. I found a post https://social.technet.microsoft.com/Forums/windows/en-US/72b9fc06-d550-4621-a763-ddb96eb5441a/printer-mapping-using-gpp that says try turning on CSE logging in group policy to get some verbose logging for printer deployments. When I turn this on the printers connect just fine (which really confuses me)...the problem is i'm going to have tons of logs files littering the computers every time someone logs on so i'm reluctant to leave this turned on.

[gaz350b]

Just out of curiosity are you able to connect the machines manually to the print queue by browsing to the server?

[rrrrr]

I had a similar issue. I think by putting in fqdn of the server resolved it.

Try for testing, mapping the same printer 3 times to a room and see what the result is.

 

Do one by ip address e.g \\192.168.1.50\printer

 

Do one by share name e.g \\printserver\printer

 

And one more by fqdn e.g \\printerserver.domain.com\printer

 

See what format is most successful.

This is what i did and since changing it to fqdn it resolved issue