Roaming Profiles - Need to logon and log off twice to synchronize

It seems that various parts of my roaming profile will not update unless I logon and log off twice.  Here is what I am talking about....

I'm working on computer A.  I log off.  I now logon to computer B.  My profile is not updated, but instead the local profile cached on computer B loads.

Now, I'm working on computer A.  I log off and then back on.  I then log off again.  I now go to computer B and logon.  My profile has been properly updated.

Why must I perform what seems like an extra step in order use the updated profile on another machine?  What do I not know about how roaming profiles work?
tim90gAsked:
Who is Participating?
 
tim90gAuthor Commented:
I found some info on TechNet that answers my question....

"Turning off the fast logon enhancement
With the fast logon enhancement in Windows XP, when users change from a local to a roaming profile, two logons on each computer are required for profile changes to be registered. (HERE IS WHAT I WAS LOOKING FOR...) This is because the user always logs on with cached credentials. Therefore, it takes one logon for the network to detect that the user has become a roaming user and a second logon to apply the new settings."

This confirms that for certain parts of the profile to operate correctly, two logons are needed.
0
 
lst-yvesCommented:
Hi Tim,

Please, provide the following informations :

Computer A : What OS ? Which SP ?
Computer B : What OS ? Which SP (service pack) ?

Also,

Where do you store the profiles ? If other than CPU A or B, please provide information regarding OS and  SP. Also, who controls your domain, if other than CPU A, B or file server, please provide OS and SP.

Who access computer A and B during your test ? Is it a user with admin rights or not. (Local admin rights on one of the 2 CPU ?).

How about replication from B to A, when you log off from B, does the replication works ?

How big are your profile (please to check, go to Settings, Control Pannel, User profiles).

Thanks,
Laurence.
0
 
tim90gAuthor Commented:
Computer A: Windows 2000 Pro sp4
Computer B: Windows 2000 Pro sp4
Profiles saved on the DC, a Windows 2000 Advanced Server sp4 in a Profiles share.
Using the Domain Admin's user account during test.
Starting with either Computer A or Computer B has the same results.
Profile is about 20MBs.
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
FocusynCommented:
IT is very possible your profile has not propogated yet if you are going back and forth right away.  Sometimes propogation among 2k domains can take way longer than you would think it should, particularly on a large network.  IF you haven't already, log on and off just once, wait a couple hours and try again.  See what happens
0
 
tim90gAuthor Commented:
Thanks Focusyn.  I am on a network with only one Domain Controller.  So I don't think propagation is an issue.  I'm sorry I didn't explain that more clearly.
0
 
Dave_SlaterCommented:
right this may help u. u can try it

open regedt 32 goto

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Edit or Add Value name DeleteRoamingCache, a REG_DWORD data type. Set the data value to 1.

this means it will always look to the server and should work all the time by deleting the cache off the machines each time. give it a go

Thanks
0
 
tim90gAuthor Commented:
That is a great tip.  I would like to have cached profile though, if for some reason the Domain Controller was unavailable.
0
 
FocusynCommented:
w00t! Give yourself 500 points and a grade of "A"
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.