Login Scripts not running

[Jeremy]

I recently created a login script and placed it in the
NetLogon directory on my domain controller. I added the
file name to my users profile in AD. The login script is
not running and nothing shows up when the user logs in.
Any advice? Thank you.

 

[Lanwench [MVP - Exchange]]

How many DCs?
You have *only* the file name and no path in the profiles tab/login script
field, right?
Can you browse/run the file manually as the user after logging in?
What's the client OS?

 

[Chriss3 [MVP]]

did you typed the full path or just the name of the script in the field. it
suppose to be only the name.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup

 

[Jeremy]

Ive tried both...currently I have only the name. I have
one Primary Domain Controller, and 1 secondary. It looks
as though my secondary is logging me in.

 

[Jeremy]

I have one primary domain controller, and 1 secondary. IT
seems as though the secondary is logging me in.

Correct, I have only the file name in the path.
I can browse to the file and run it etc...I have full
permissions as well.
Windows 2000 server, and the client pc is Win2k

 

[Chriss3 [MVP]]

Are the NETLOGON share the same on both DCs?

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup

 

[Jeremy]

I noticed that before if I went to check this out, it
would give me an error message if I typed Net at the
command prompt.
I have since edited the registry and am waiting to reboot
the pc. This possibly could be the problem.

 

[Lanwench [MVP - Exchange]]

I have one primary domain controller, and 1 secondary. IT
seems as though the secondary is logging me in.

Check to see if the netlogon shares have the same info (to make sure
replication is working).

There's no PDC/BDC in Active Directory- they're all peers (with a few
special roles assigned)

 

[jeremy]

I got it to work. On the secondary domain controller, I
noticed that the Net command was not working. I figured
it was do to the Path being messed up. I had to go into
the registry and change the type of variabble the "path"
was created as. Reg_Extended something or other.

 

[jeremy]

I got it to work. On the secondary domain controller, I
noticed that the Net command was not working. I figured
it was do to the Path being messed up. I had to go into
the registry and change the type of variabble the "path"
was created as. Reg_Extended something or other.

 

[Chriss3 [MVP]]

Okay, thanks for sharing the solution with us,

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup

 

[Lanwench [MVP - Exchange]]

Glad you found the solution - thanks for posting back.