We've deployed Windows 7 Professional. With about 10% of the computers, there is a problem with network drives not being displayed or accessible through Windows Explorer. A user will get three drives mapped using the login script: X:, Y:, and Z:. On the problem computers, Windows Explorer will not show the drives at all. Typing in X: in the Windows Explorer address bar will bring up a message saying the location can't be found. The weird thing is that other applications, such as Word, Acrobat, and even Internet Explorer can see the network drives; Word's open file dialog will display the drives fine. Typing X: into Internet Explorer's address bar will then open a Windows Explorer window displaying the contents of the X: drive. I've searched forums for similar problems, but I haven't come across anything close as of yet.

What does the command "net use" give you?

Please refer the following article: Deploying Group Policy Using Windows Vista It says: UAC may prevent Group Policy logon scripts from appearing to work properly. For example, a domain environment contains a GPO that includes a logon script to map network drives. A nonadministrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the nonadministrative user starts Windows Explorer. The user sees their mapped drives. Under the same environment, an administrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the administrative user starts Windows Explorer. The user does not see their mapped drives. When the administrative user logs on, Windows processes the logon scripts using the elevated token. The script actually works and maps the drive. However, Windows blocks the view of the mapped network drives because the desktop uses the limited token while the drives were mapped using the elevated token. To get around this issue, administrative users should map network drives under the limited user token. This mapping is accomplished by using the launchapp.wsf script shown in Appendix A, which works by scheduling the commands using the task scheduler. The task scheduler launches the script under the administrative full token, thereby allowing Windows Explorer, other limited token processes, and the elevated token process to view the mapped network drives.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.

I've just posted quite the same question today, this happens too to non administrative users Did this answer fix the problem ? My post is here : http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/988ed3a1-5a53-4c6c-bdf6-0606f5e0baac Cheers. François Dagorn Université de Rennes 1 France