Consider the following scenario that occurs in a domain environment:

• You configure the users in the domain to use roaming profiles.
• The folder redirection feature is enabled in the domain.
• The offline folder feature is enabled on the network share on which the users’ roaming profiles and the redirected folders are located.
• The values of all registry entries under the following registry subkeys have been set to the path of the network share:
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

In this scenario, when you try to log on to the domain from a Windows Vista-based client computer or from a Windows Server 2008-based client computer, the computer may stop responding.

Consider the following scenario:

• You have a shared folder that is available offline.
• On a Windows Vista-based computer, in an Office application or in WordPad, you use the Open File dialog box to open an offline file that is in the shared folder.

In this scenario, the shared folder goes offline. After the shared folder goes offline, you cannot make the shared folder go online from Windows Explorer.

The Public folder is inaccessible after you upgrade from Windows Vista to a different version of Windows Vista. This includes the following:

• You upgrade from the beta release version of Windows Vista to the release version of Windows Vista.
• You upgrade from Windows Vista to a different version of Windows Vista. For example, you upgrade from Windows Vista Home Premium to Windows Vista Ultimate.

Consider the following scenario:

• On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you create a Server Message Block (SMB) share.
• After the share is not accessed for some time, you remove the share.

In this scenario, you cannot delete the folder that is used to back the share. Additionally, you receive an error message that resembles the following:

Folder In Use
The action can’t be completed because the folder is open in another program
Close the folder and try again.

In this case, you have to restart the computer. After that, you can delete the folder.

Consider the following scenario:

• On a computer that is running Windows Server 2008 or Windows Vista, you log on immediately after you have restarted the computer.
• Windows Explorer tries to display the desktop before the Workstation service has started.
• Folder redirection is enabled on the computer.

In this scenario, you may experience one of the following symptoms.

Symptom 1

When you try to access redirected folders, you receive the following error message:

\\servername\Username\sharename is currently unavailable.

Symptom 2

The Documents, Pictures, Music, and Desktop folders are not visible.

Consider the following scenario. You are running a Windows Vista-based computer. On this computer, you use Windows Explorer to rename a folder on a network share or in a redirected folder. In this scenario, the renamed folder disappears in Windows Explorer.

Additionally, the renamed folder reappears after you perform one of the following operations:

• You press F5 to update Windows Explorer.
• You close Windows Explorer, and then you reopen it.

On a Windows Vista-based computer, files in an offline folder are randomly corrupted.

For example, assume that the offline folder contains an Internet shortcut (URL file). In this case, some files in the folder are empty, and you cannot use the Internet shortcut to open the URL.

When you use Windows Explorer to rename folders on a Windows Vista-based computer, you may receive the following error message:

The file or folder does not exist

On a computer that is running Windows Vista, you move the focus between folders. When you do this, Microsoft Narrator may not read the detailed information about a folder.

Note: When this problem occurs, Narrator does not notify you that a folder is empty.

When you redirect the Documents folder on a Windows Vista-based computer to a network share, the folder name unexpectedly changes back to Documents. You expect the folder name to be the user name.

This behavior may create many Documents folders on the network share. If you try to rename one Documents folder, all the other Documents folders change to that name.