Profile issues

[tyrannus]

I have a client that has approx 50 users on their network. They all use roaming profiles. The problem we are having is when they try to delete an icon off of their desktop, it reappears after they log off and then back on. For some reason it will not go into the recycle bin.

 

[Roadki11]

Do all users have unique user accounts or do they share generic accounts?

 

[tyrannus]

They are all unique accounts, all permissions are set correctly on the shares. The GPO is setup correctly to point each user to their unique desktop. Yet they cannot delete anything from their profiles.

 

[Roadki11]

What about client or server side errors in the event log? anything about "usrenv - Windows cannot update your roaming profile. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.

 

[tyrannus]

Nothing in the event logs, I was getting usrenv errors, but that was related to a terminal services license issue. That issue has been resolved.

 

[Dublin73]

have you deleted their locally cached profile from their PCs, under C:\Documents and Settings\username?

Within their profile folder on the network do you see the icon (which cannot be deleted) still there in the desktop folder? The path to the desktop folder would be...

profileshare\username\Desktop

 

[Roadki11]

You dont happen to have the "Dont save settings at exit" enabled in GPO do you? I cant remember if that policy includes deletes or not.

 

[tyrannus]

When I delete the icon from the desktop and check the profile share on the server, the icon is gone. It still exists on the local profile though.

I do not know if the local profiles have been deleted from all workstations. I am a new admin for this client and haven't gotten far enough to look at that.

 

[Lothian313]

I had the same problem. Check out MS KB287566. Are you storing the roaming profile inside your users network share (home drive)? Try creating a separate folder structure for profiles. Apply the same share security and ntfs permissions to these folders (user plus domain admins minimum). Modify the user profile in AD to point to the new share. This should fix your problem.