Question : Roaming profiles

All our users on our Windows 2000 Domain, with windows 2000 (SP4) clients have roaming profiles.  I have had an employee who has been here for a couple of years.  Last week here roaming profile was not being pulled from the server, saying:

"Windows did not load your roaming profile and is attempting to log you on with your local profile.  Changes to the profile will not be copied to the server when you logoff.  Windows did not load your profile because a server copy of the profile folder already exists that does not have the correct security.  Either the current user or the Administrator's group must be the owner of the folder.  Contact your network administrator."

Now, I did do windows updates to install all critical updates and the SP4.  I researched google and it talks about SP4 checking for correct permissions on precreated roaming profile folders, and do NOT permit roaming if the permissions are not what Windows requires.  Well WHAT DOES WINDOWS REQUIRE?????/

The permissions are correct, under the profile folder, the user, Administrator, and SYSTEM...all with full control.  In the domain controller, it paths the profile to that folder, which is shared.  It was working fine before the windows update and now it doesnt roam anymore.

Can anybody help me?  Thanks,

Mr. CJJimbos

Answer : Roaming profiles

Windows XP SP1 and Windows 2000 SP4 perform the following checks to verify correct security on roaming user profile folders:
If the roaming profile folder exists, Windows XP SP1 and Windows 2000 SP4 check to determine if either the user or the local Administrators group is the owner of the folder. Note that if a member of the local Administrators group, but not the local Administrators group itself, is the owner, this check will fail.
If the folder is owned by the user or the Administrators group and if the "Do not check for user ownership of Roaming Profile Folders" policy is not set, Windows XP SP1 and Windows 2000 SP4 consider the folder to be legitimate and copy files to the folder during the logoff process and from the folder during the logon process.
If the roaming profile folder exists, and if the user or Administrators group is not the owner of the folder, Windows XP SP1 and Windows 2000 SP4 do not copy any files from or to the folder, display an error message, and log an event in the System event log. The user's cached profile is issued, or a temporary profile is issued if no cached profile exists.
If the profile folder does not exist, Windows XP SP1 and Windows 2000 SP4 create the folder in its current secure manner.
If the "Do not check for user ownership of Roaming Profile Folders" policy is set, the ownership of the folder is not checked, and Windows XP SP1 and Windows 2000 SP4 assume that the folder is legitimate.
Error Messages
If Windows XP SP1 or Windows 2000 SP4 cannot save a user's profile because of incorrect security, the user receives the following error message. This error message is also recorded in the event log:

Event ID: 1526
Severity: Error

Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Windows did not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrator's group must be the owner of the folder. Contact your network administrator.
If a user cannot be logged on by using a cached profile and is issued a temporary profile, the standard temporary profile message appears after the error message.
To Turn Off the New Check for Existing Roaming User Profile Folders
A new computer policy that is named "Do not check for user ownership of Roaming Profile Folders" exists under Administrative Templates\System\User Profiles in Group Policy Editor. In Windows 2000 SP4, the new computer policy exists under Computer configuration\Administrative Template\System\Logon in Group Policy Editor. Administrators can use this policy to turn off the ownership check for existing roaming user profile folders and to revert to the Windows XP behavior. This new policy prevents Windows XP SP1 and Windows 2000 SP4 from checking for correct permissions on a user's roaming profile folder. In Windows XP without SP1 and versions of Windows 2000 prior to SP4, no checks are performed for correct permissions if the profile folder already exists.

Windows XP SP1 and Windows 2000 SP4 do not copy files to or from the roaming profile folder if all these conditions exist:
You turn off or do not configure this setting.
The roaming user profile folder exists.
Neither the user nor the Administrators group is the owner of the folder.
If you turn on this setting, the behavior is the same as Windows XP without SP1 and versions of Windows 2000 prior to SP4.

From: http://support.microsoft.com/default.aspx?scid=kb;en-us;327462