Re: Really stupid mapped drive question

Using the /persistent switch at the same time as mapping drives
in a batch file is like using belts and braces and is lilely to cause
error messages because the PC remembers the persisten mappings.
It would be better for the OP to resolve the problem instead
of walking around it, by inserting a "pause" statement in his
logon script. This would let him see why the problem drive
does not get mapped for certain users. I suspect that the
solution will then become obvious.


"Tas" <tasita@xxxxxxxxx> wrote in message
news:1164922863.364762.145350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I had this issue in the past. It seemed to be random computers who
weren't able to map the drive off of the startup script I was using.
If I manually ran the script on the computer, however, the drive would
map. So, to solve the issue I just setup the mapped drive to be
persistent with the following command:

Net use x: \\Server\Share /persistent:yes

You can run this command from the computer manually or with the script.



MPHinPgh wrote:
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



.

Relevant Pages

  • Drive Mapping Script Not working
    ... I have a script that maps drives based on a machines name here is a sample ... net use and map the share correctly net use reports the share to already be ...
    (microsoft.public.windows.server.scripting)
  • Re: Script Mapping all Drives
    ... I put the script together quickly, ... trap the error and then remove the existing mapping. ... Should code be added to remove all drives, ... Dim intIndex, objList, objGroup ...
    (microsoft.public.scripting.vbscript)
  • Re: Please evaluate logon script
    ... I'm not too worried about mapping drives because everyone gets almost every ... the printer mapping is a bit of a PITA. ... I have created the logon script below. ... But some users also have local printers. ...
    (microsoft.public.scripting.vbscript)
  • Re: Mapped Drives based on Security Groups
    ... Currently it's sole purpose is to call the script file, ... AT "Mapping Drives" ... If InGroup ... AT "Mapping Additional Drives" ...
    (microsoft.public.windows.server.sbs)
  • Re: Help
    ... I am using 5.8 and 2 machines that will not execute the copyhere portion of ... same script and that part of the code works perfectly 100% on all machines. ... The code to map drives is written to use error trapping. ... 'Check if the ProfileBackup Folder exists, if not create it, if yes then ...
    (microsoft.public.scripting.vbscript)
Loading