Hello, Login Script (login.bat file) does not run when user logs into their Win 7 Pro System. This login script worked when all the client Domain Controller were running Windows 2003 Servers (2) DC's). These server were rplaced by Windows 2008 Server. Please advise on how to troubleshoot and correct. Thanks, Nick Nick V. Kosmas

Use rsop or gpresult to check with group policy settings are applied. Make sure that your script is used as a startup or logon script and that the group policy is linked to the domain. Are you able to run the script manually. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Hello, if the script is configured on the user account properties open \\domain\netlogon folder logged on as a suer and run the script manual. If with GPO borwse to the containing folder and try it also. Then post the result. Make sure the DC/DNS servers are not multihomed and that all domain machines use only domain DNS servers on the NIC, An unedited ipconfig /all from the DC/DNS servers and a problem client can help us to verify some other settings also.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Nick, What is the function of the script? How did you configure the script, via User profile, Logon script or via GPO? As Meinolf suggested, please check whether the script can be applied manually? Did you receive any error when the user logon? If so, please write down the detailed error message here for research. Did you see any error in Event Log? If so, please also paste the error events here. On the problematic Windows 7 computer, run Command Prompt with administrator privilege, then run “gpresult/v > C:\policy.txt” Please paste the results for troubleshooting. Best Regards, Nina Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com. 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.

Hi Nick, I would like to confirm the current situation. If there is anything that I can do for you, please do not hesitate to let me know, I will be happy to help. Regards, NinaPlease 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.

I recommend you change from logon scripts to the more modern way of mapping drives: Group Policy Preferences: http://technet.microsoft.com/en-us/library/cc731892(v=WS.10).aspx

Are the users members of the local Administrators group? If so, and UAC is enabled, the user logon script may run with admin permissions (an admin token is used), but the desktop uses normal user permissions (another token) so the mapped drives are not visible. Two possible solutions (besides disabling UAC), one to use a launchapp.wsf described here (see section titled "Group Policy Scripts can fail due to User Account Control") http://technet.microsoft.com/en-us/library/cc766208(WS.10).aspx another solution uses EnableLinkedConnections registry setting: http://support.microsoft.com/kb/937624 Richard Mueller - MVP Directory Services

Hi Nina, just experienced the same problem today, the script is used to automatically map network drives on workstations when users turn their pc's on, it works fine on XP Pro machines but on Windows 7 pro computers users have to map network drives manually. Thanks in advance.