LOGON SCRIPTS

[Guest]

I created a logon script and I need to know where to place the script on my
domain (win2k serv. AD). I know in the user profile to type logon.bat, but
the script needs to be in a certain folder and I have forgotten where it goes.

Thanks.

 

[Michael Ellingson]

The logon scripts should be placed into:

%WINDIR%\SYSVOL\sysvol\DOMAINNAME\scripts

Where %WINDIR% is your windows directory (usually C:\WINNT\) and DOMAINNAME
is the name of your AD Domain. From there, they should be replicated to
your other servers.

 

[Guest]

Thanks Michael, but for some reason when I type under the users profile
LOGIN.bat, the login script doesn't run. Now I have created login scripts
before but this one doesn't run at all. I also did place the script in the
proper place, so thank you for the reminder...but the script still isn't
running.

 

[Michael Ellingson]

I've got a couple of thoughts:

How many servers are in your domain? Are they all replicating? Can you
locate this script in each of the SYSVOL folders on your servers? What are
the file permissions on your script?

In your original message, you mention your script is named "logon.bat", but
in your latest message it is "login.bat". Which one is correct?

I've used two methods to assign logon scripts in my company's week-old 2000
AD domain: Group Policy and the Profile tab in the user's property pages.
Both have worked without any fuss which was surprising. Let's hope one of
my questions above catches it, 'cause if not, I'm just scratching my head!

 

[Ken B]

Why not put the login script (which you assigned via the User's user object)
in \\domaincontroller\netlogon ? That's where I place my login scripts...
and they always work for me there.

HTH

Ken

 

[Cary Shultz [A.D. MVP]]

Al,

Have you considered using GPO and .vbs scripts? They are really nice. Take
a look at http://www.rlmueller.net for some ideas!

HTH,

Cary

 

[Michael Ellingson]

We're saying the same thing. You are going via a URL; my example below is
via the local harddrive.

 

[Guest]

sorry about that Michael, the proper name is logon.bat and I have only two
servers, I placed the script onto both servers...but I still can't get it to
work. weird.

 

[Guest]

ok lets clear up a few things.

1. placed the logon.bat file in it's proper place
winnt\SYSVOL\sysvol\domainname\scripts

2. utilizing MMC - AD Users and Computers
username, properties, Profile tab, under logon typed in logon.bat

3. 2 servers with replications so the script is on both servers.

4. script is nothing major just two drives that I need for the users:
NET USE Y: \\xxx\Forms /PERSISTENT:NO
NET USE X: \\xxx\Downloads /PERSISTENT:NO

but it still doesn't work...unreal.

 

[Cary Shultz [A.D. MVP]]

Al,

Everything is very clear. I was simply offering a possible alternative (
one, btw, that I like better than logon.bat or logon.cmd ). I know that it
is not fixing your problem, but at least the users could have their two
mapped network drives!

Now, let's start to look at your specific issue.

You have two Domain Controllers. There is apparently no frs issue as the
logon.bat file shows up in the correct place on both DCs (
c:\winnt\SYSVOL\sysvol\yourdomain.com\scripts ). Have you actually verified
that the logon.bat is in the same location on both Domain Controllers? I
would guess that you have based on your point 3!

What happens if you manually map a network drive from one of the clients to
the scripts folder ( er, to the sysvol shared folder and then traverse down
to it )? Are you able to run the logon.bat script and achieve your goal?

If that does not work ( and even if it does ) what happens if you bring the
logon.bat to the local client and execute it? Does it run there?

What operating system(s) is/are your clients running? If the are all WINXP
Pro then there might be a simple solution. WINXP boots up and handles this
sort of thing a bit differently. There is something called fast logon
optimization that kinda messes things up a bit ( like logon scripts not
working the first time...yet, if you log off and then back on the mapped
network drives are there! ).

HTH,

Cary

 

[Paul Tupou]

browse sysvol down to scripts folder and place there. Should fix.