D
DanaK
I can't belive it...
I have a school that has XP Pro workstations in each room
used by multiple students. Each student has their own
logon and home directory which means a new profile for
each student on each workstation.
Each room has one printer in it, usually a shared printer
connected to the teachers' computers. I set the
workstations in one room, all I had time for that day, in
the Administrator's profile to use the teacher's shared
printer assuming (silly me) that the printer would be
propagated to all students that happened to log onto the
workstations like the old W9x OS's would do. Now I find
after searching these and other tech forums that I need to
set up some kind of script for the workstations, I guess
on the DC, to have the same printer across all profiles?!
Should, or couldn't, this be a login script using the net
use command? Or could it be preformed using Group Policies
assigned to specific computer groups?
Can someone please explain the logic behind this
foolishness? I have zero knowledge of Visual Basic and
less time to get a degree in this stuff just to have
minimal functionality with it.
I have a school that has XP Pro workstations in each room
used by multiple students. Each student has their own
logon and home directory which means a new profile for
each student on each workstation.
Each room has one printer in it, usually a shared printer
connected to the teachers' computers. I set the
workstations in one room, all I had time for that day, in
the Administrator's profile to use the teacher's shared
printer assuming (silly me) that the printer would be
propagated to all students that happened to log onto the
workstations like the old W9x OS's would do. Now I find
after searching these and other tech forums that I need to
set up some kind of script for the workstations, I guess
on the DC, to have the same printer across all profiles?!
Should, or couldn't, this be a login script using the net
use command? Or could it be preformed using Group Policies
assigned to specific computer groups?
Can someone please explain the logic behind this
foolishness? I have zero knowledge of Visual Basic and
less time to get a degree in this stuff just to have
minimal functionality with it.