I initially had roaming profiles implemented but it turned into a massive headache of constant issues and sync failures. Decided to remove roaming profiles and remove the roaming location from each user in AD, then setup a GP to force local profiles on the hosts. This works for new users and existing users show as "local/local" when looking at user profiles in System & Security –> System –> Advanced –> User Profiles. .
When I login and type "set" into a CMD window though, it shows APPDATA as still pointing to the NFS/SMB roaming location (even though the user profile reports as a local profile).
I have verified nothing is setup in AD (User properties –> Profile –> Profile Path) is empty.
I created a GPO at the top level where I set “Only allow local user profiles” and “Prevent Roaming Profile Changes from propagating to the server” to enabled.
Users are able to login and navigate to Control Panel –> System & Security –> System –> Advanced Settings –> User Profiles. The account I login with shows Type and status of "local".
I ran gpresult /H and searched through the policies for anything "Roaming" and the only things that showed up were "Only allow local user profiles” and “Prevent Roaming Profile Changes from propagating to the server” which I implemented above to disable these roaming profiles.
Creating a new user and logging in doesn't automatically setup the user with a roaming profile (ie APPDATA point to C:\Users\etc).
How do I get the profiles to point APPDATA back to local or what could be stopping the profiles from returning back to normal?
Best Answer
Only solution I was able to find was to delete the accounts and create new ones. This required removing the accounts, deleting the C:\Users\Username folder on the windows computer the users uses, fixing permissions on the old shared folder, then having the user login. Not ideal but it works.