REQ Help: Roaming Profile does not stay

[Swampfox (:^Þ]

WIN 2000 Servers
W2k Pro Clients
SP-4
all other updates.

When I logon a computer with a new employee's username it used to balk
and say that it didn't find a roaming profile and then I would make
any changes while signed on as them and then log off and when I went
back in it had the same wallpaper and any other changes I had made for
them.

Since we have been installing SP-4 we have found that at logon it
didn't recognize the ownership of the roaming profile as the user.

After Googling "Roaming Profile not available", we found a white paper
about it at http://support.microsoft.com/default.aspx?kbid=327259

"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."

The suggestion it made was to open Group Policy snap-in:
Computer Configuration
/Administrative Template
/System
/Logon
/User Profile

and <ENABLE> the line:
"DO NOT CHECK FOR USER OWNERSHIP OF ROAMING PROFILE FOLDER"

I tried this, but it didn't change anything. Does anyone have any
other ideas?

TIA

Swampfox...^Þ

 

[Lanwench [MVP - Exchange]]

WIN 2000 Servers
W2k Pro Clients
SP-4
all other updates.

When I logon a computer with a new employee's username it used to balk
and say that it didn't find a roaming profile

Did you set up a roaming profile path for them in ADUC & make sure that the
users have full control (share & NFTS) to the folder where the profiles are
loaded?

and then I would make
any changes while signed on as them and then log off and when I went
back in it had the same wallpaper and any other changes I had made for
them.

They were using a local profile.

Since we have been installing SP-4 we have found that at logon it
didn't recognize the ownership of the roaming profile as the user.

After Googling "Roaming Profile not available", we found a white paper
about it at http://support.microsoft.com/default.aspx?kbid=327259

"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."

The suggestion it made was to open Group Policy snap-in:
Computer Configuration
/Administrative Template
/System
/Logon
/User Profile

and <ENABLE> the line:
"DO NOT CHECK FOR USER OWNERSHIP OF ROAMING PROFILE FOLDER"

I tried this, but it didn't change anything. Does anyone have any
other ideas?

Check the settings/permissions on the profile folder on the server.

 

[Swampfox (:^Þ]

Yes, I use AD and copy a previous OU with the same groups and settings
as what I want this new OU to have.

None of the OUs have "FULL", but they have "CHANGE" & "READ" ...but
because of your comment I did try giving this OU "FULL CONTROL" in
permissions & security for the profile, but it didn't make a
difference.

Did you set up a roaming profile path for them in ADUC & make sure that the
users have full control (share & NFTS) to the folder where the profiles are
loaded?


They were using a local profile.

Check the settings/permissions on the profile folder on the server.

Tried FULL CONTROL, but it didn't help. :-(

 

[Lanwench [MVP - Exchange]]

Yes, I use AD and copy a previous OU with the same groups and settings
as what I want this new OU to have.

None of the OUs have "FULL", but they have "CHANGE" & "READ" ...but
because of your comment I did try giving this OU "FULL CONTROL" in
permissions & security for the profile, but it didn't make a
difference.

Users need full control. Check your NTFS settings again....it should work; I
do this all the time. Try creating a new user as a test -