Microsoft User Loopback Processing of Group Policy

"Typically printer installation is done in the enterprise via login scripts that are based on usernames. This works fine in most cases, however, I recently began looking into a better way to do this. The problem with installing printers based on usernames is that on a given day a teacher or student can log into as many as three or four different computers in various locations throughout a school. With this being the situation, we could for instance map the printer “GCHS-MATHLAB” to a student active directory account, but then when the student walks into the business lab, he will still be printing to the math lab. The obvious reaction to this would be to setup a script that installs all available printers in the building for the student, however this creates an unnecessary security risk, and would allow students to print into room they are not located in which could cause trouble."

You can read the full article here.

Posted by Gabriel Maciel

No comments: