Hi there, I'm rather new and have been looking for a solution to this for a little while. We have a server setup that, when you log into a user, their batch file is supposed to run and set them up with their respective mapped drives. For SOME reason when we converted over to windows 7 the mapping seems to fail. The error message we get (keep in mind this isn't with everyone) asks us to input the users name and password, however, it doesn't update the policy properly. So every time we log in as them, it asks us again. To stop this we REM out the line. I was wondering if their were some setting that we needed to change in either Windows 7 or server side that might fix this. I'm not familiar with the server, but I've heard the terms 2000 advanced server being thrown around. Thank you, shiro

Hi shiro, Thanks for the post! Did you enable the UAC on these Windows 7 clients? Does this script work via GPO? Please also refer to this thread: http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/1e791e31-c34a-4200-9caf-2601c5781cfd Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thank you very much for the reply! Sadly the solutions you pointed out did not work for us. I'm going to try and explain again what the problem is, since i've spent some more time working on it. We have server 2000 SP4 running group policy, and we also use Active Directory to direct which logon script (batch file) runs per person/per department. When the Windows XP machines logon, they run the script, visibly, and work just fine. So for example: I log into John Doe: The script runs, but when it gets to a network path that he isn't supposed to have access to, it simply says "path not found error 85", and the script continues on and completes. At the end it always says "updating policy" right before it finishes and disapears. This is all normal. On the Windows 7 machine, however: The script runs, and when it gets to the network path that John Doe doesn't have permissions to, it stalls, and instead asks for the username and password associated with the directory. So if John Doe needs a drive bellow the one it stalls on, he won't get it, and the script just sits there. We also can't just REM out all of the drives the person doesn't use, because these batch files are setup per department and not per person. So we would be shutting out other folks who still need the drives. I've tried many many solutions on the local machines, everything from the UAC, to setting the "send lm and ntlm v2" solution that seemed to work for several people. Also disabling the firewalls and virus protection etc etc.... At this point I'm not sure what to do or even try, and the only other bit of information I'm certain on, is that the server is only set for "lm and ntlm" so NOT for "NTLMv2". I couldn't modify it yesterday though due to it being a high use server. Would rather NOT bring it down in the middle of the day ;P Any ideas?? Thanks again, ShiroThis is only a test....