I have a really confusing roaming profile issue on my hands...
We utilize roaming profiles and folder redirection in our RDS environment (Citrix, for what its worth). We dont utilize roaming profiles for users logging on via desktops; only when they come in through Citrix. This is a user experience configuration - mostly so that when a user configures their Outlook (or wahtever application...) the way they want - their settings remain.
My predecessor configured our original roaming profiles on the environment. A few days ago, i decided to break a few of our groups up into different roaming profile stores, separated by line of business. Think of the following ou structure as a guide, as the users server they are accessing will determine which GPO and TS location they use...
Core Busines (GPO1 applied)
Line of business 1 (GPO2 applied)
Line of business 2 (GPO3 applied)
Line of business 3 (GPO4 applied)
Essentially i wanted all 3 groups to store their roaming profiles in different locations. The following directory structure applies...
GPO1 = Base Configurations for environment + TS location \\server1\Core-Profiles
GPO2 = TS location \\server1\Line1-Profiles
GPO3 = TS location \\server1\Line2-Profiles
GPO4 = NO TS CONFIGURATION - Utilize local profile
SO NOW THE CONFUSING PART...
I created the GPO's and linked them to the appropriate OUs. When i move a server into one of the sub OUs and attempt to login via Citrix, TS starts to launch and then BOOM - "The User Profile Service Failed the logon. User profile cannot be loaded". Reboots do not resolve this issue. I move the server back to the original OU, with the original base location (\\server1\core-profiles), reboot, and everything works fine.
If i manually go into the registry at this point, and edit the registry key for roaming profiles (hklm/software/policies/microsoft/windows nt/terminals ervices/WFProfileFPath) to my intended location (\\server1\Line2 for example...) everything works without a hitch. The new user profile is created in that directory, and the user is able to login. If i run a GPUpdate /force, the registry key is switched back to the original location, and user is able to login with the profile going to original location. If i move the server to the different OU and reboot again - unsuccessful. I receive the failed logon error. If at this point, with the server in the NEW OU, i attempt to change the registry key to the original file location (where it was working...) - User profile fails to logon successfully.
I have deleted all of the correct ProfileList registry keys, i have deleted all roaming profiles, i have deleted all local user profiles. None of these settings makes any difference. I receive the identical same treatmeant either way. I have duplicated this exact same scenario across 5 different servers in my TS environment.
Really hope someone has an answer to this one...
