In a domain environment, you configure the domain users to use mandatory user profiles. You set the profile path by using the %LogonServer% environment variable. However, when a user tries to log on to the domain from a Windows Vista-based or Windows Server 2008-based client computer, the user is logged on by using a temporary profile. Additionally, if the Do not log users in with a temporary profile Group Policy setting is applied in the domain, the user cannot log on to the domain.

Note: This issue does not occur if the user logs on to the domain from a Windows XP-based or Windows Server 2003-based client computer.

In a domain environment, you configure the Slow network connection time-out for user profiles Group Policy setting to reduce the time that is required for roaming profile users to log on to the domain through a slow network connection. Assume a user then logs on or logs off the domain through a slow network connection from a Windows Vista Service Pack 1 (SP1)-based or a Windows Server 2008-based client computer. In this scenario, the time that is required to log on or to log off the domain is still longer than expected.

Note: After you configure this Group Policy setting, you expect the roaming profile client to use a local copy of the profile if the network connection is slow.

If you check the user environment debug log or if you capture a network monitor trace, you see that the client computer downloads or uploads the roaming user profiles every time that the user logs on or logs off the domain. This behavior occurs even in a slow network environment.

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.

Consider the following scenario. In an Active Directory domain environment, you configure the Windows Firewall with Advanced Security Group Policy setting. Specifically, you specify three firewall log files for these three profiles, respectively. Then, you apply this Group Policy setting to a Windows Vista-based client computer. However, when the network profile is changed in this scenario, you notice that the firewall information for the private profile is unexpectedly logged in the log file for the public profile.

On a Windows Vista-based client computer, Windows Firewall applies local program exceptions and port exceptions in the private profile and in the public profile. This behavior occurs even when the Windows Firewall standard profile settings indicate that these exceptions are not allowed.

This behavior may cause the following problems.

Problem 1
On the client computer, you may unexpectedly receive a Windows Firewall notification.

Problem 2
A local administrator can unblock a program even though the Windows Firewall: Allow local program exceptions Group Policy setting is disabled.

Problem 3
A local administrator can add program exceptions and port exceptions through the Windows Firewall Control Panel program even though the following Group Policy settings are disabled:

• Windows Firewall: Allow local program exceptions
• Windows Firewall: Allow local port exceptions

On a Windows Vista-based computer, the netsh firewall command together with the profile=all parameter does not configure the public profile. For example, the following command opens local port 80 to TCP traffic for the domain profile and for the private profile. But the following command does not open the public profile:

netsh firewall add portopening protocol=TCP port=80 name=”Web Port” profile=all

The Windows Firewall Control Panel program only displays settings for the currently active profile. Therefore, if you run this command, and you then open the Windows Firewall Control Panel program when the public profile is active, you receive the following exception:

“Web Port” was not created for the public profile.

Note: This is expected behavior.

If you open the Windows Firewall Control Panel program when the domain profile or the private profile is active, you will receive the following exception:

“Web Port” was created.

When you log on to a Windows Vista-based computer by using a temporary profile, you receive the following error message:

The User Profile Service failed the logon. User profile cannot be loaded.

This error may occur if the “Do not logon users with temporary profiles” Group Policy setting is configured.

After you log on to a Windows Vista-based system, you may notice that a temporary profile has been loaded instead of the profile that corresponds to the current user. Therefore, any changes that you make to the current desktop are lost after you log off the system. Additionally, the notification area may display the following error message:

Your user profile was not loaded correctly! You have been logged on with a temporary profile.

Changes you make to this profile will be lost when you log off. Please see the event log for details or contact your administrator.

Finally, the following event is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: Date
Event ID: 1511
Task Category: None
Level: Warning
Keywords: Classic
User: User
Computer: Computer
Description:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

• 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 )