Search the Community

Hi everybody. I am sure by now we have all seen the exact same old boring print script a thousand times. You create a set of groups sharing the same name as your printers and add your machines to those groups. How ever, I felt that this basic boring print script was actually sub standard and that as a programmer I could whip up something with a lot more functionality. So with out further delay I present to you my Over Complicated Printer Logon script lets begin with a break down of how this print script is superior Logging: The ability to create a text log of what the print script is doing, perfect for debugging those irritating issues. Recursive Groups: When searching for printer groups, say if my machine is a member of a sub group or a sub sub sub group with a printer then it still gets the printer. Multiple Servers: Why map printers on 1 print server, when you can map printers on all your print servers. Exclusion Group: You can add a group that prevents the print script from making any changes to the computers printers. OU Group Printers: You can define a group using a named prefix in an ou container, any machine in this ou will search that group for printer groups too. Follow Me Printers: Not only can you define print groups by machine and ou but it will also search the logged in user for printer groups. Easy to understand config section built into the script, this is the one part you are allowed to change. Print Servers Group name to prevent printer changes Print group name prefix Delete local printers, yes or no Enable ou printer groups Prefix name of ou printer groups File path for logging (supports %USER% and %COMPUTER%). I do apologise, I am the absolute worst at explaining things, but if you have any questions just drop em below and i shall do my best to reply with an answer. Printer Script: Click here for the Gist on Github. Please keep note of the version number in the top comment as this will be used to track changes. The bar for printer scripts has now been raised! Thank you and Enjoy! - - - Updated - - - Reserved for change log.

Hi guys Very strange issue that is occurring. I believe this issue has been occurring for a while as I had one printer which would repeatedly map to areas, outside of the scope of the GPO, but I am now experiencing a far more extreme version of this. I have a new Windows 10 client machine, which will be used by one member of staff. The client user should have four centralised virtual queues mapped via User GPO using Printer Deployment from the Print Management facility on the print server. Additionally he has a printer in his office, which should be mapped and another printer in a meeting room. However, when running a group policy update the user receives all six of these printers, plus some additional ones for which the machine should not be a target. Further to this there are also two printers which are not included in any GPO anymore which are also being mapped to it. One of those two doesn't even exist on the print server anymore. I have created a new user account for the user, removed his previous account from the PC and registry, none of which have helped. I have also run the RSOP tool, but that doesn't really tell me much about where these printers are coming from. Group Policy modelling strangely also wont help me - when I run this I get the following error message: "An error occurred while generating report: Object reference not set to an instance of an object" When searching online for what this error means, people seem very unclear and are just trying things. Also someone suggested that in Windows 10 the default is set to connect network printers, and that the way to disable this is to go into advanced network settings and remove this from the Private Profile. This is on a domain profile, so shouldn't matter, but I have disabled the feature incase. Also two of the printers are no longer even attached to the network so this shouldn't be the affecting factor. Any advice appreciated as I am brain fried as to where these are coming from...