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 )

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

When you configure a wireless connection in Windows Vista, the Service Set Identifier (SSID) information may display the wireless profile name instead of the actual SSID.

In the Active Directory domain, you configure different profile paths for a roaming user profile and for a terminal services profile. When a user logs on to a Windows Vista-based client computer by using a Remote Desktop session, Windows Vista uses the profile path that is defined on the Terminal Services Profile tab to load the profile. However, Windows Vista should use the profile path that is defined on the Profile tab to load the profile.

On a Windows Vista-based computer, you configure the following Group Policy setting:

Delete user profiles older than a specified number of days on system restart

Therefore, you expect the user profiles that have not been used within the number of days that you specify to be automatically deleted when Windows Vista restarts. However, you notice that some user profiles that have been used within that period are unexpectedly deleted some days later.

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.

In a Windows Server 2003 Active Directory directory service domain environment, you use a migrated user account to log on to a migrated computer that is running Windows Vista, Windows Server 2003, or Windows XP. In this case, you may receive the following error message:

Windows cannot find the local profile and is logging you on with a temporary profile. Changes to this profile will be lost when you logoff.

After you log on to the migrated computer, Windows creates a temporary profile for the migrated user account. Additionally, error messages that resemble the following may be logged in the Application log:

Message 1

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1511
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
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.

Message 2

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1512
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
Description: Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile. If this problem persists, contact your network administrator.
DETAIL - The process cannot access the file because it is being used by another process.

Message 3

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1518
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
Description: Windows was unable to load the registry. This is often caused by insufficient memory or insufficient security rights.
DETAIL - The process cannot access the file because it is being used by another process.

This issue occurs if the following conditions are true:

• You use a third-party migration tool to perform an intraforest migration of the user account and of the computer. After the migration, the source user account still exists.
• You have included the security identifier (SID) history in the migration.
• You have performed a translation for the cached profile on the migrated computer during the migration.

Note: The translation of the cached profile enables the migrated user account to access the profile of the source user account after migration.

Notes

• This issue also occurs in a Microsoft Windows 2000 Active Directory domain environment.
• This issue occurs if the migrated computer is running Windows Vista, Windows Server 2003, or Windows XP.

Every time that you log on to a Windows Vista-based computer that is connected to a domain, a temporary user profile is created. When you log off the computer, the user profile is deleted. Additionally, one of the following events may be 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

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: Date
Event ID: 1534
Task Category: None
Level: Warning
Keywords: Classic
User: User
Computer: Computer
Description: Profile notification of event Delete for component {error code} failed, error code is -2147024894.

Log Name: Application
Source: Microsoft-Windows-Search
Date: Date
Event ID: 3036
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: User
Computer: Computer
Description: The content source [csc://{content source number}/] cannot be accessed.