-----Original Message-----
I AM SO SORRY IM SO CONFUSING.... the client machine is
not partitioned. i just want them to be able to map their
f:/ drive to a shared folder on the server. for instance,
an application resides on the server inside this shared
folder, APPS. so my user normally right clicks on my
computer, then map drive, then types... //server/APPs to
map their f: to //server/Apps.
the problem is that some of my users use different pcs. so
instead of them having to map the drives on each machine
they logon, i'd like to control it by some type of logon
script.
i have had problems with setting this up in active
directory. if i copy the script file to the client and
run it from there, it does run as thought, and it prompts
me that "F:/ is currently mapped to //server/Apps, do you
want to disconnect it ".. so it seems that the script file
is right, just i dont know if it sees it from the server.
it may be that its hung up at the prompt waiting for me to
answer it, and i can't see it through the windows browser.
that's why i was wondering if there was something i could
put in the script file, that would interrupt the browser
and have it tell me, hey i'm running your script file, but
im hung up.
but you also mention the global policy,
i saw an answer "jason" wrote to same question in another
forum with the global policy, so i tried it.. i copied the
bat file to the user configuration, windows settings,
logon/logoff, and it still didnt work for me.
what is best way?
all
.
Rob,
No worries about the confussion. It is mostly me as I am
really under the weather today and can not think straight!
Anyway, I am going to assume that the reason that the
logon.bat did not work is because in addition to
adding "logon.bat" to each user's profile ( btw - take a
look at ADModify which is a really cool tool from a
couple of guys at Microsoft - it will allow you to make a
change to a bunch of user accounts at once so that you do
not need to go to each and every user account! ) is that
you have to place the actual "logon.bat" in the shared
NETLOGON folder. And jsut a tip: I would use logon.cmd
if possible. I have read about .bat logon scripts
causing problems with WIN2000 but the .cmd logon script
does not. I do not have any empirical evidence to
support this, though. So maybe I should not say it!
Are you confortable with Group Policy? If you are not
then I might suggest that you start! However, please
please please do so in a test lab. I try to
never "learn" at the expense of the users. Really good
way to become very unpopular!
There is an excellent book by Jerry Moscovitz
called "Windows 2000 - Group Policy, Profiles and
InelliMirror". It is quite good. The ISBN number is 0-
7821-2881-5 and is from Sybex.
I would be more than happy to walk you through this (
using a logon script via Group Policy ) if you would
like. There would be two parts: actually creating the
logon script file and then creating the Group Policy.
Let me know.
Cary