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:

• In a network environment, you enable the Delete cached copies of roaming profiles Group Policy setting in a particular domain.
• In this domain, you configure some user accounts to use a mandatory user profile.
• You log on to the domain by using a user account that uses the mandatory user profile from a client computer that is running Windows Vista or Windows Server 2008.
• You log off the computer.

However, if you log on to the domain from this client computer by using any other user account, you notice that the mandatory user profile is not deleted from the %SystemDrive%\Users directory as expected.

Note: This issue does not occur on a client computer that is running Windows XP.

• Support guidelines for migrating roaming user profiles data to Windows Vista or to Windows Server 2008
  If you’re looking to migrate users to Vista, and they are currently using roaming profiles, you’ll find this document useful.
  (tags: Roaming Profile Migrate )
• Palm, Inc. - Palm Desktop by ACCESS 6.2 for Windows
  Vista compatible and includes enterprise friendly HotSync enhancements.
  (tags: Software Palm Compatibility )

If you’re looking to migrate users to Vista, and they are currently using roaming profiles, you’ll find this document useful. Keep reading →

Consider the following scenario:

• In an Active Directory domain environment, you configure users in the domain to use a roaming user profile.
• You enable the Process even if the Group Policy objects have not changed option for some Group Policy objects in the domain.
• The user profile on the profile server contains read-only files.

In this scenario, when a domain user logs off from a Windows Vista-based client computer, some redundant files that are named Prfx.tmp may be generated in the user profile folder on the profile server.

Consider the following scenario. In a Active Directory domain environment, you configure the following settings for users in the domain:

• You enable the User must change password at next logon setting for users in the domain.
• You configure the users to use roaming user profiles.

Then, a domain user logs on to the domain for the first time from a Windows Vista-based client computer. In this scenario, Windows Vista does not download the network-based default user profile from the from the Netlogon share. However, Windows Vista loads the local default user profile.

Note: This problem also occurs when the user password has expired and the user changes the password before logging on to the domain.

On a Microsoft Windows Vista-based computer, you may experience one or more of the following symptoms in a wireless network environment.

Symptom 1
IEEE 802.1X authentication that is based on Virtual Local Area Network (VLAN) switching may fail.

For example, you try to use computer authentication and user authentication to switch the client computer to different VLANs. However, the client computer does not obtain the correct IP address during VLAN switching.

Symptom 2
In a wireless profile, the information about the Extensible Authentication Protocol (EAP) method that is selected in a user interface may be incorrect.

For example, if different vendors provide more than one EAP method, the EAP method that is displayed in a wireless profile is not the EAP method that is actually selected.

Symptom 3
A wireless profile that an independent hardware vendor (IHV) provides may be corrupted after you use the wireless profile user interface to edit the profile. When this problem occurs, you may receive an error message that Windows Explorer has crashed.

Symptom 4
Every time that you roam to a different wireless access point, you are prompted to provide a user credential. This problem occurs even if you have saved the user credential.

Symptom 5
You registered a Protected Extensible Authentication Protocol (PEAP) method that the IHV provided. When you try to authenticate against an Internet Authentication Service (IAS) server, the server may reject the authentication, and the IAS server may send an error message that the authentication has failed. The Onex.dll file crashes when this problem occurs.

After you enable the Credential Roaming feature for Windows Vista-based client computers in a domain, the size of the Ntds.dit file on the domain controller grows continually larger. Additionally, when Active Directory database changes are replicated to other domain controllers in the domain, the size of the Ntds.dit files on the other domain controllers also grows larger. Therefore, this growth eventually occurs on all domain controllers in the domain.