Both these methods work (they're the same approach). I started on two computers with this method, and curiously when I did a test logon with one of the student accounts, I started getting script errors. This indicated to me that there actually was a script set up to install the printers.

So I found the script, and edited it to change it to the new printer name. It worked!!

But I have urgent help needed (I'm at the place right now and I need to fix this today). The script works on all the XP machines in this lab, but unfortunately it does not work on the newer Vista machines (I get the same script errors as before, claiming the printer doesn't exist). Research didn't come up with much, but I've concluded something: it has nothing to do with Vista and everything to do with when these newer, faster machines are running the scripts. The script fails at logon (before the desktop even shows), but if I run the same script once everything has loaded, the printer installs perfectly.

How do I fix this? Is there a way to delay the script?