My current environment spans several buildings and remote locations, with quite a few buildings housing multiple departments, and unfortunately printer ratio is probably in the range of 1:2-4 in some departments.
I would like to implement a printer mapping solution, currently we only have a partial solution for the lab workstations we support. Our active directory is structured by physical location for workstations, so no clear lines of departments within the buildings.
I was looking at doing a powershell script that contains a hash table, which stores the building and department as a key, and a string array that contains the paths to the printer(s). So, at logon (!), I could get the user's dept from AD, the computer's location from AD, concat the strings together, then use that as the key to pull the string array from the hashtable, check each printer to see if it's been mapped, and map it if it isn't. This is ignoring default printers for the majority of the time.
I looked at group policy, but it would result in quite a few GPOs being created, so probably not the best route to go.
We really don't have an asset tracking solution in place, so there isn't one to leverage here. I would like to hear about solutions others have put in place, or where I could improve this solution.
I'm looking for a more elegant solution than a user calling the helpdesk requesting printers to be mapped, or a user trying to map a printer by going to start->run->. These printers already have a queue on the print server (Windows)