We're using group policy to redirect the Windows 7 Start Menu to a UNC path. (This incidentally is a domain-based DFS namespace). (Each target is hosted by a Windows Server 2003 server). Almost everything seems to be working as expected, with the icons at the target location appearing as expected on the start menu. The problem is that for the first 10 minutes or so after logging on, clicking on any of the icons has no effect. Also right-clicking the icon does NOT display the right-click-context-menu, it simply does not respond at all. Icons on the desktop (also redirected) work fine. Then after about 10 minutes or so, they suddenly start working. Also, any icons "clicked in vain" earlier, suddenly register, resulting in a click-delay of about 10 minutes too! The right-click behavior returns to normal at this point too. We've discovered that by enabling offline files for Windows 7, that this problem goes away, meaning icons work immediately after logon. This is presumably because the OS caches the redirected start menu network folder into the CSC, and it's likely the local copy of the files which are being used by the start menu instead of the network ones, enables the start menu icons to work. The problem we're seeing with this work-around in place is that for about 30% of users, their network drives don't map reliably, also for the first 10 minutes or so, and I suspect Windows 7's networking which is causing both of these problems. We've seen the same thing happen on Windows Server 2008 terminal servers. This problem does not occur for Windows XP client PCs and users under the same group policy. Is there anything in the Windows 7 workstation client and the way it access the network which might be responsible for this 10 minute delay effect? edit: the problem appears to be independent of hardware used, and has persisted since the launch of Windows 7 about a year ago. It happens in virtual machines, physical machines from different vendors etc, and different form factors, desktops, laptops etc, with or without antivirus software, with or without IPv6 bound/unbound, and independent on which Windows updates are installed. It keeps happening to this day on fully patched Windows 7 boxes.

Hi, As I know, Windows 7 and Windows XP has different Start Menu structures. To redirect the Start Menu, you can enable GPO for folder redirection in Windows 7, the path is \User Configuration\Policies\Windows Settings\Folder Redirection. Then redirect the Start Menu folder ( %Systemdrive%\users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu ) to another available location. Meanwhile, enable the entry "Remove user's folders from the Start Menu" using GPO. For references: Folder Redirection Overview Windows 7 Start Menu Redirection,Folder Structure Also I will give you some suggestions you can try: 1 Login with Clean Boot Safe Mode with networking 2 Update network card driver 3 Enable NetBIOS Since this issue occurs on several Windows 7 PCs, it’s possible the issue relates with your Server, I suggest to asking Windows Server for further help: http://social.technet.microsoft.com/Forums/en-US/category/windowsserver · The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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, Did your issue solved? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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, I will mark your reply as answer. It could help other communities here who have the same issue. Thanks for your understanding. Regards, Leo Huang 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 Leo, It was rude of me to not respond to your response earlier, please accept this apology. I had followed up on some of the suggestions referenced by your links and have just completed one of the tasks which is validating that all DFS root namespace servers are correctly serving the root of the namespace, and that they are indeed all visible to all clients. Also, some of the other things you suggested: a. NetBIOS is already enabled b. This happens to multiple machines, different generations and manufacturers, so it's unlikely they all have the same fault in the NIC. c. we're about to run some safe-mode-with-networking tests shortly. A problem I can see with a specific windows version client having trouble accessing a group of server's resourcs, is that the Windows 7 guys will say "it's a server problem", and the server guys will say "it's a windows 7 client problem", and each will refer back to the other, shirking all responsibility or willingness to assist, even if within the context of a $508 PSS incident. (there's nothing better for them to feel that they can simply refer to the other group and close the call to collect the cash for their business division) On this occasion, because Windows XP works fine, and the problem is specific to Windows 7, we can rule out server issues. Remember, it's not that it isn't working, it's just that it doesn't appear to work for the first 10-15 minutes after logging in or rebooting the PC. Folder redirection aside, what other aspects of Windows 7 networking can result in it taking so long to get ready to work?

Hi, Did you try to login with Safe Mode with Networking? In order to exclude third party tools or driver conflict, you’d better to perform this test. Any other test to troubleshoot the issue you can try: 1 Disable antivirus software and firewall 2 Disable “Remote Differential Compression” in Control Panel-----Programs and Features-----Turn Windows features on or off. Hope that helps. Regards, Leo Huang 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.

We'll be doing the safe-mode-with-networking test next week, and I'll post the results back here then. 1. The problem persists with or without antivirus software. 2. We've already turned off RDC, but thanks for pointing this one out for other readers. We're also going to try Windows 7 Service Pack 1 which we'll download probably tomorrow.

Hi, Did your issue solved by in Safe Mode with networking or update to Windows 7 SP1? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.

Here are the results so far: Service Pack 1 for Windows 7 - no change, problem persists. we're about to try the last suggestion, safe mode with networking.

Hi, seen something similar, check the server where the share resides, How many NIC's ? BR Alexey

Hi, seen something similar, check the server where the share resides, How many NIC's ? BR Alexey

Hi, seen something similar, check the server where the share resides, How many NIC's ? BR Alexey It's a UNC path into a DFS namespace, the specific target being referenced and used as the start menu redirection target is hosted by multiple servers, accross multiple AD sites, spread accross WANs as well. \\domain\dfs\folder1\thestartmenu --> \\server1\folder1\thestartmenu \\server2\folder1\thestartmenu \\server3\folder1\thestartmenu \\server4\folder1\thestartmenu The problem happens both at the main site, where three servers host one target each (eg servers1 through 3). These servers have 2 NICs each, with one connected and one disabled. The problem also happens at branch offices (eg server4), where the servers there only have one NIC Please keep in mind that Windows XP has no problem with this arrangement, and is still working fine this way for over 10 years. It's only Windows 7 that seems to have this weird delay effect. Looking further into the issue, and examining a PC which is exhibiting the issue, it's as if the workstation service, responsible for accessing network resources of any kind takes about 15 minutes before it's working properly. Unfortunately, the user logs into the PC and expects network resources to be available (such as network drives, or the start menu), but the PC just isn't ready yet for another 20 minutes. The following log shows some commands typed at the command prompt shortly after logging in. The PC has an IP address, IE happily access the internet etc. The command is simply repeated every 5 minutes or so: C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ Volume in drive \\domain\dfs is SERVER3_E Volume Serial Number is xxxx-xxxx Directory of \\domain\dfs\folder1 29/07/2008 08:37 PM <DIR> . 29/07/2008 08:37 PM <DIR> .. 30/08/2010 05:41 PM <DIR> StartMenuFolders 0 File(s) 0 bytes 10 Dir(s) 12,001,111,856 bytes free C:\> remember: XP=no problem, Windows7=delay getting ready to access the network.

Hi, seen something similar, check the server where the share resides, How many NIC's ? BR Alexey It's a UNC path into a DFS namespace, the specific target being referenced and used as the start menu redirection target is hosted by multiple servers, accross multiple AD sites, spread accross WANs as well. \\domain\dfs\folder1\thestartmenu --> \\server1\folder1\thestartmenu \\server2\folder1\thestartmenu \\server3\folder1\thestartmenu \\server4\folder1\thestartmenu The problem happens both at the main site, where three servers host one target each (eg servers1 through 3). These servers have 2 NICs each, with one connected and one disabled. The problem also happens at branch offices (eg server4), where the servers there only have one NIC Please keep in mind that Windows XP has no problem with this arrangement, and is still working fine this way for over 10 years. It's only Windows 7 that seems to have this weird delay effect. Looking further into the issue, and examining a PC which is exhibiting the issue, it's as if the workstation service, responsible for accessing network resources of any kind takes about 15 minutes before it's working properly. Unfortunately, the user logs into the PC and expects network resources to be available (such as network drives, or the start menu), but the PC just isn't ready yet for another 20 minutes. The following log shows some commands typed at the command prompt shortly after logging in. The PC has an IP address, IE happily access the internet etc. The command is simply repeated every 5 minutes or so: C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ This operation is supported only when you are connected to the server. C:\>dir \\domain\dfs\folder1\ Volume in drive \\domain\dfs is SERVER3_E Volume Serial Number is xxxx-xxxx Directory of \\domain\dfs\folder1 29/07/2008 08:37 PM <DIR> . 29/07/2008 08:37 PM <DIR> .. 30/08/2010 05:41 PM <DIR> StartMenuFolders 0 File(s) 0 bytes 10 Dir(s) 12,001,111,856 bytes free C:\> remember: XP=no problem, Windows7=delay getting ready to access the network. Hi I spend some time with the same problem and created a small workaround: 1. Mapped the Startmenu Destination folder as a Drive - I know dangerous because the letter could be already taken, but if you are managing the environment then it is not a problem and i mapped it using GPO preferences as hiden B:\ letter that is not used anymore ;) I hope. 2. Here i faced another problem you are not able to redirect the Start menu to a local drive, well you can but the mapped drive is not present at GPO processing so the redirection fails. - maybe some one knows how to add some delay ... but i solved it on another way. For users with Local and Roaming profiles I created a simple WMI logon script that changes the User Shell Folders destinations to B:\StartMenu for the Startmenu and B:\StartMenu\programs for the start menu root programs. on error resume next startmenu = "B:\StartMenu" Programs = "B:\StartMenu\Programs" const HKEY_CURRENT_USER = &H80000001 strComputer = "." Set oReg=GetObject( _ "winmgmts:{impersonationLevel=impersonate}!\\" &_ strComputer & "\root\default:StdRegProv") strKeyPath = "Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" strValueName1 = "Start Menu" strValueName2 = "Programs" oReg.setExpandedStringValue _ HKEY_CURRENT_USER,strKeyPath,strValueName1,startmenu oReg.setExpandedStringValue _ HKEY_CURRENT_USER,strKeyPath,strValueName2,Programs For users with MANdatory profiles just modified the hive. Hope that Helps. BTW DFS is not recomended for Redirected folders.