Despite several attempts to deploy Windows 7 (!) the majority of the infrastructure is still on XP. As a result, when users with roaming profiles log on to RDP sessions (or RDS sessions) the XP profiles are not compatible and a temporary profile is generated instead.

The key is to generate a Terminal Services Profile in AD which will be launched whenever the RDP session is connected. This profile has a “.V2″ extension which clearly defines it as separate from the original XP profile.

However, during the early stages of testing, we found that simply creating the new TS profile entry didn’t always kickstart the new profile, especially if the user had previously been logged in on the server.

it’s necessary to delete all traces of the original profile from the server that is generating the temporary profile,

Delete the profile folder from C:\Users or under the  Advanced System Properties –> User Profiles

Delete the profile list entry from the registry – HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Now the remote desktop server will generate the new user profile when the user logins. It resolves all the temp profile issue.