K
kevmar
I have a problem with users missing mapped drives in my computer /
explorer when they first login to a new computer (and build a profile).
NET USE will list them, command line can see them, applications can
file open and see them, and killing and starting explorer will show
them. But looking at my computer will not show them.
I see other people post that they have the problem, but I have not seen
any solutions.
Here are some more details.
If the drive gets mapped after the desktop loads, it is not a problem.
Once the user relogs, they will have most (if not all) the drives.
All machines are XP sp2 and are mapping several different 2003 servers
in the same domain. All are workstations.
To map the drives I normaly use a vb script using WScript.Network, but
the net use command has the same problem.
The script can either be in the policy or in the users logon script and
it will have the same problem.
Setting the drives to persist in the profile fixed the fallow up logon
attempts, but the initial logon where the profile is built is giving us
the problems.
I tried toggling the setting to have explorer process to run in there
own threads with no luck.
Our most restriced users and domain admins (my self included) all
suffer from the problem.
We have a large group of users (300) that use any number of machines
(150) that get ghosted nightly. Every login they do is a new profile
building login on that machine.
My current workarounds include adding a 35 sec delay on each mapping
(but thats forever on users that log in quickly). I am also
considering fliping the policy that make script run in synchronous mode
on. but that has other problems that will cause me to rework lots of
other scripts (that were desigend to run forever in the background or
require user interaction to close). Those other scripts currently
prevent the user from loggin on in that mode.
Anyone have any ideas of things to try? or having the same problem?
explorer when they first login to a new computer (and build a profile).
NET USE will list them, command line can see them, applications can
file open and see them, and killing and starting explorer will show
them. But looking at my computer will not show them.
I see other people post that they have the problem, but I have not seen
any solutions.
Here are some more details.
If the drive gets mapped after the desktop loads, it is not a problem.
Once the user relogs, they will have most (if not all) the drives.
All machines are XP sp2 and are mapping several different 2003 servers
in the same domain. All are workstations.
To map the drives I normaly use a vb script using WScript.Network, but
the net use command has the same problem.
The script can either be in the policy or in the users logon script and
it will have the same problem.
Setting the drives to persist in the profile fixed the fallow up logon
attempts, but the initial logon where the profile is built is giving us
the problems.
I tried toggling the setting to have explorer process to run in there
own threads with no luck.
Our most restriced users and domain admins (my self included) all
suffer from the problem.
We have a large group of users (300) that use any number of machines
(150) that get ghosted nightly. Every login they do is a new profile
building login on that machine.
My current workarounds include adding a 35 sec delay on each mapping
(but thats forever on users that log in quickly). I am also
considering fliping the policy that make script run in synchronous mode
on. but that has other problems that will cause me to rework lots of
other scripts (that were desigend to run forever in the background or
require user interaction to close). Those other scripts currently
prevent the user from loggin on in that mode.
Anyone have any ideas of things to try? or having the same problem?