I have wrote a program to map printers. You call it in script with the printers as command line arguments.
I will try to post the windows 7 she'll it calls later if I can find the code.
@Arthur The problem with using GPO for us is we have a lot of staff that move from school to school, and they have their own laptops. We have scripts for each school, and the users run a masterlogin script which detects their AD Site and compares it to their home school/location which is stored in AD. If they match then it runs their home schools script. If they don't match, it runs their home schools script , and then script for the school that they are at. It's worked really well until the drivers were updated.
So a GPO really only works for mapping printers at their home school, not great for when they travel.
If you want to assign a printer on a computer OU you can create a Policy and set the Policy Loopback settings in the Computer Configuration section to Merge apply the policy with the settings at the beginning of the thread and then this should apply the printer to the computers in the OU no matter who logs on. If you set the Printer to Remove when no longer applied it would then remove the printer from the machine if it were moved to a different OU and should prevent printers from following users around if using Roaming profiles.
Make sure you allow non-administrators the ability to install printer drivers via the device GUID via policy and this will save the necessity for admins to log on for drivers to install.
Thanks Davit2005. We still use scripts for printer installs. GPO doesn't give us the flexibility we need for staff travelling to multiple locations with their laptop.
There are currently 1 users browsing this thread. (0 members and 1 guests)