Link to home
Start Free TrialLog in
Avatar of jduawa
jduawa

asked on

Still having a profile issue

I have a domain admin account that has a roaming profile.  Originally it was set to \\server1\profiles$\admin.ts .  I setup a new server and moved all user profiles to this new server using robocopy.  I then changed the profile path in AD to point to the new box \\server2\profiles$

This one domain admin account keeps looking at the old box for the profile, and if i stop sharing the old location then i get the message that windows cant locate your roaming profile message.

I really want this account to use the location on the new box.  Any idea why it keeps looking at the old box when it clearly has the path to the new one.
ASKER CERTIFIED SOLUTION
Avatar of Alan_White
Alan_White
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jduawa
jduawa

ASKER

definitely changed the right field and this user is in the default user folder in AD so isnt associated with an OU to have a GPO applied.
Does it matter which PCs / Servers they attempt to logon to?
There could still be a GPO applied to the system they are logging into if loop back processing in enabled.
Two more thoughts:
1. Are you sure that your Domain Controllers are sync'ed up?
2. Try turning UserEnv logging on and see if the logs give you anything more: http://support.microsoft.com/kb/221833
Also take a look at this:

http://groups.google.com/group/microsoft.public.windows.server.active_directory/browse_thread/thread/1d86bf00e5ac745f/9a54707af80d43a2?hl=en&ie=UTF-8&q=still+pointing+to+old+profile#9a54707af80d43a2

You may have a different GP for that user applied.  Check under GPMGMT and MAKE SURE that you don't have a linked or inherited GPO.

Another:  http://support.microsoft.com/kb/888203

You may just have to setup the profile again.

HTH
Avatar of jduawa

ASKER

Wow i am an idiot....The profile under the terminal server tab was set differently, thanks