Weird: printer mapping issue
Don't know where to put this. It follows on from another thread, but decided to start afresh after further testing. (Previous thread http://www.edugeek.net/forums/window...-up-error.html).
We have 98 laptops and 31 desktops on the domain. Server 2003 and clients are XP Prof.
50 laptops of one model, all imaged from build of first one. 48 laptops of similar model, all imaged from build of first one.
Computer names for laptops are YRx-number (eg. YR3-01). Half of each year group is one model, and half the other.
All laptops in same OU in AD, not split by year group.
At login, script runs that maps drives and printers according to first two or three letters of computer name. Same script on all machines. Was running fine. Now getting scripting errors coming up on YR3, YR5 and YR6. These relate to two HP 2200dn printers, both same age. Other printers fine.
I know you're thinking it's a scripting error, but hold on. YR4 laptops are fine; we can't get a scripting error on YR4 laptops at all and they map the printers fine. So to test if it's machine specific (we've tried every other combination of tests we can think of - different room, wired/wireless, etc), we renamed a laptop that doesn't work for printers so that the name starts YR4. Still doesn't work for those printers. Can't manually map the printers, can't map them with script.
Tried it the other way (and this is all from the same room). Renamed a YR4 laptop to YR3. Still works for printers, can map with script (no scripting error) and can map manually.
I hope someone out there is sitting there thinking the solution is obvious.... Please tell me what I'm missing! :confused: