|
While we're on printer deployment, we currently deploy printers through group policy preferences. However, most of our computers are shared (student) machines, so have dozens, if not more, profiles. Works fine, except during initial log in when the system downloads and installs the printer drivers. This is done over a moderately slow WAN link, plus the computers themselves are pieces of poo poo. Since each student gets the same shared printers, we thought that the very fist install should get the drivers stored and installed somewhere. It takes 5 minutes sometimes, but whatever, it's the initial install. But instead, what we see is every single person downloads and installs the drivers during logon, for the same identical printer each time, meaning logon times suck poo poo. During subsequent logons, it's a very brief process. Anyone know how to deal with this?
|
#
¿
Jan 31, 2014 19:08
|
|
|
|
| # ¿ May 19, 2024 11:50 |
|
|
I use a combination. There are settings that 90+% of everyone uses, so they share a couple large, generic gpos. For other more specific needs, I break them into smaller policies. As an example, a typical student will have the All Students policy, which covers things like removing access to the control panel, local drives, the command prompt, etc. Students at a specific school have their school-related policies in a large gpo, to deal with folder and home dir redirection, printer mapping, etc. This policy is shared with administrators, teachers and other staff at the school as well. I have a couple smaller things, like a software restriction policy, and access to changing keyboard locale settings. Both of these have their own policy, and they are applied as need be.
|
|
#
¿
Apr 30, 2014 22:46
|
|