Active Directory User Login Scripts Not Working

The login scripts are already in the netlogon folder on my domain controller.

I did change the "Logon script:" field to only have the script itself instead of the full path.

This still did not work.  

Another question:  My login scripts that I made are using a .bat file type, but your example shows a .cmd file type.  Does this matter?

bat files should be fine but you can rename to .cmd if you prefer.
Do you have any virus scanners running - some of these have options to stop .bat files runnig from certain locations at startup.
also make sure you've spelt the name of the script correctly
not put any slashes in (are the scripts in the root of the netlogon share)
Also confirm the permissions on the bat file

I have the script I am trying to run in the root of the netlogon share.  I've tried running as both a .bat and .cmd file, but have had little luck with either.  It now appears that the script DOES try to run upon login, but it just hangs on the first command in the script and does nothing.

If I try manually running the same script from the same location, it works perfectly.  If I manually put a shortcut to the script (still in the netlogon share) in my startup folder, it will run upon login and have no problems either.

So the script works, and the user/computer clearly have access to it.  It's just when I try to let it run automatically using the Active Directory Logon Script option, it hangs on an open cmd window - with the text of the first line of the script displayed, but not working.  I've let it sit for like 10 minutes to make sure it wasn't just slow, but nothing changed.

I've tried changing the first line of the script to a few different things, but each time it still hangs.  I've tried a net time command to start, I've dried to map a drive to start, but nothing changed no matter what I tried to start with.

I've set the permissions of the .bat file for "everyone" to have read and run access.

I'm running out of ideas - anyone have any suggestions?

does a simple echo script also hang on the first line?

try something like the script below:

@echo off
echo this is the first command
pause
echo this is the second command
pause
echo this is the third command
pause
exit

                                              

1:
2:
3:
4:
5:
6:
7:
8:

I made a script called echo.bat and it does not appear to be hanging.  The cmd window was there and said:

this is the first command
Press any key to continue . . .

I could press a key and then it went to second, then third, then it exited.  So it appears to be working as it should.  Perhaps the hanging has something to do with my script?

This is basically what my script looks like.  I'm trying to map some drives and force a time sync (we run a weird time system, don't ask).  Again, this script works perfectly if run manually, or if placed in the startup folder (both times running from the netlogon folder).  Do I need to change something in my script maybe?

net use P: \\server\folder1 password /user:"username"
net use T: \\server\folder2 password /user:"username"
net use R: \\server\folder3 password /user:"username"
net time \\server /set /yes
                                              

1:
2:
3:
4:

do you shares contain any spaces? if so you should use:
net use P: "\\server\folder 1"

does your system require to logon to the shares with a specific username and password?
if so, remove the quotes:
net use P: \\server\folder1 password /user:username

also do you have any group policies enabled?

The shares don't contain spaces.  I made sure of that to avoid potential problems.  The shares are all going to require specific user names and passwords, as certain people are allowed access to certain files.

I'll try without the quotes (although the script works with the quotes - if run manually or in the startup menu).

Also, I do have group policies enabled.  This is actually something that concerns me.  If I go to a client and open and command prompt and type "gpupdate /force" I get the following:

Refreshing Policy. . .

User Policy Refresh has completed.
Computer Policy Refresh has completed.

Certain User policies are enabled that can only run during logon.

OK to logoff. (Y/N)

My gut is telling me that something in one of our group policies is doing something during logon, and it's fighting with my login script or preventing it from running, or something...

Is this a possibility?  I'll go take a look through my group policies and see if I can find anything that looks out of place, or something unnecessarily running during login.  Really not sure what it could be though.

i think i know what's causing your problem. let me check on my group policies. brb

do you have "run logon scripts synchronously" enabled? (user configuration > administrative templates > system > scripts)
if so, see what happens if you disable this setting

I looked in every group policy object I could find and "Run logon scripts synchronously" was not enabled in any of them.

given the additional info especially as it seems to start running and hangs I would suggest its more likely to be the 'wait for network at startup' ppolicy option
http://support.microsoft.com/kb/304970

The KB article linked is assuming that I have the "Run logon scripts synchronously" policy enabled, which I do not.

I will try enabling both "Run logon scripts synchronously" and "Always wait for the network at computer startup and logon" and see what happens.  I'll post back here shortly with my results.

Tried enabling both group policy settings listed in my last post, and the script still hangs at the same spot.

this may seem banal but make sure you give them at least 2 reboots to give the policies a chance to apply.

do you need to have user credentials in the script can you not rely on ntlm and use ntfs permissions, I assume you're in a domain.

have you been able to pin down which command it hangs on

I'm doing 2 reboots each time - just to be safe.  8-)

It hangs on whichever command is at the top.  I've tried moving commands around and still no luck.

If a net use X: \\server\blah is at the top, that's what it hangs on.
If a net time \\server /set /yes is at the top, then it will hang there.

I actually just tried a different script, which ONLY has a net time command, and it still hangs.  No mapping, no users, and still no luck.

We're deploying some new PCs so I snagged one early in the process and made sure I didn't have any antivirus on it yet - just in case the AV was preventing the script from running properly.  Still no luck on the AV-less no-firewall PC (PC is in the domain, all updates, logging in with same user I've been testing these scripts on).

Have you tried using a different user account.
I'm tempted to say we should increase userenv logging to verbose but I'm not sure it will catch the logon scripts

Can you confirm what the run logon scripts synchronously was originally set to (was it not configured) and did you check the computer and user configuration

Have you had any userinit errors in the event logs