B
Bobr
We have a logon script that has run flawless for our Win
NT 4 clients. In addition about 5 other clients are
running Win2k Pro. We are currently in the process of
upgrading to Win2k and have noted a problem. If a generic
user log's on all the drives with the exception of the
first drive mapping will map themselves. I have added
comment lines in front to cause the scipt to run a bit
longer with no success. These scipts will run for myself
fine. I have Domain Admin and Enterprise Rights. The IT
director only has Domain Rights. All my mappings work on
any workstation, the IT director is like the generic
users. The first drive mapping does not map, but the
others do. I relize if I put the drive mapping at the end
of the drive listing again it will work. I have in the
interim put a shortcut on the desktop in the all users, so
the users can run the script again when they are logged
on. This forces the drive in question to map.
NT 4 clients. In addition about 5 other clients are
running Win2k Pro. We are currently in the process of
upgrading to Win2k and have noted a problem. If a generic
user log's on all the drives with the exception of the
first drive mapping will map themselves. I have added
comment lines in front to cause the scipt to run a bit
longer with no success. These scipts will run for myself
fine. I have Domain Admin and Enterprise Rights. The IT
director only has Domain Rights. All my mappings work on
any workstation, the IT director is like the generic
users. The first drive mapping does not map, but the
others do. I relize if I put the drive mapping at the end
of the drive listing again it will work. I have in the
interim put a shortcut on the desktop in the all users, so
the users can run the script again when they are logged
on. This forces the drive in question to map.