Mike Hammer
asked on
users not getting there profile
windows 2012 AD.
several users not getting there profile (Dfs) when logging in to server(rds) instead they get c:/users/temp one .
the pattern is there all users that have been previously disabled. then enabled (we disable any that have not been active for a set time )
any ideas as to a resolution ?
several users not getting there profile (Dfs) when logging in to server(rds) instead they get c:/users/temp one .
the pattern is there all users that have been previously disabled. then enabled (we disable any that have not been active for a set time )
any ideas as to a resolution ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
right. we don't set a path on ther account. they just get created in the c:\users folder.
perms are fine some are full admins. and new accounts work
so my mistake. dfs just redirects some folders. nothing to do with profile.
my problem user logs on and gets a temp folder profile instead of his name. I've removed the ref keys in profile list
perms are fine some are full admins. and new accounts work
so my mistake. dfs just redirects some folders. nothing to do with profile.
my problem user logs on and gets a temp folder profile instead of his name. I've removed the ref keys in profile list
ASKER
so a rephrase. why would disabling an account mess up local profile ? once it's been re enabled
Disabling and re-enabling an account shouldn't mess up the local profile.
You say you've removed the profile from the profile list. Is the user's profile folder still there in the C:\Users folder?
You say you've removed the profile from the profile list. Is the user's profile folder still there in the C:\Users folder?
ASKER
sorry. I mean I can fix. by removing the folders. in users and removing the ref entry in profile list. but it does affect everyone who has had account disabled. I have yet to see it happen to a normal account that's not being disabled. it's nit happened on dev rig either but less users of course
ASKER
not really a solution but can't recreate on any test rigs. just odd behaviour. cheers
ASKER
thank you
ASKER
thank you
ASKER