M
MPHinPgh
It's Stupid Question Time!!!!!
I have a group of users who are configured via group policy to run a
login script (just a .bat file, no vbs). One of the things the script
does is map drive K: to a share on one of my 2K3 DCs. Most of the
people boot up, login and get their K:, in addition to 6 or 7 other
mappings from the script.
But I have 5 or 6 people, who when they boot, don't get the K:.
Everything else in the script has completed just fine. If they just
logout and log back in, the K: is there. The mapping does not disappear
as long as they don't reboot, even if the leave the machine on for
days. It's just when they turn the computer off overnight. Also, if I
run the .bat file from the cmd line after they've booted, the K:
mapping is there.
All of the clients are XP SP2. The only difference I can find between
the machines with the problem and machines without the problem is the
fact that the machines that don't get the K: mapping all have VMWare
Workstation installed (don't ask, they need it). Other than that, the
machines are all the same. The users are mostly just "users" although
two of the people having the problems are members of the domain admins
group.
Any takers on this one?
Thanks
MPHinPgh
I have a group of users who are configured via group policy to run a
login script (just a .bat file, no vbs). One of the things the script
does is map drive K: to a share on one of my 2K3 DCs. Most of the
people boot up, login and get their K:, in addition to 6 or 7 other
mappings from the script.
But I have 5 or 6 people, who when they boot, don't get the K:.
Everything else in the script has completed just fine. If they just
logout and log back in, the K: is there. The mapping does not disappear
as long as they don't reboot, even if the leave the machine on for
days. It's just when they turn the computer off overnight. Also, if I
run the .bat file from the cmd line after they've booted, the K:
mapping is there.
All of the clients are XP SP2. The only difference I can find between
the machines with the problem and machines without the problem is the
fact that the machines that don't get the K: mapping all have VMWare
Workstation installed (don't ask, they need it). Other than that, the
machines are all the same. The users are mostly just "users" although
two of the people having the problems are members of the domain admins
group.
Any takers on this one?
Thanks
MPHinPgh