If you've got a domain going, why aren't you mapping the printer with a login script? AFAIK that's the standard way to do it. It Works Just Fine here at work. I can find the login script for you if you'd like, but it's essentially "net use \\pathto\printer".
That would be fine with me. I think it wasn't done that way because whoever set up this network only wanted that printer installed for users when they logged onto those specific computers. That would make sense, but they only use their logins to log into those computers anyway, so it won't make a lot of difference.
I'm not familiar with login scripts, though. I'd appreciate more information. And is Tony correct, will that script not actually install the printer driver?
Previous Topic
Index
