For now, seems this question is too board. I am going to submit more focus questions.
As stated above, I felt the problem needed to be broken up as I am counting 6 parts now. If totallytonto wants I can keep this one going
I branched out two parts of the rediection problem. What the can not delete redirection file gave me was that built-in administrator needed to be used. Can you give me an explanation of why I am taking the folders of desktop, documents and favorites, give ownership to builtin administrator then to administrators before I can delete the files of someone who has left?The default behaviour of redirected folders and romaing profiles is to apply very specific permissons to the folders to prevent the administrators browsing the end user's data at will.
The other question gave me that redirection works usually. Can you tell me why a particular computer can not participate? with W's computer it does not matter whether I or he logs in, any file created on the desktop will not be passed onto the server. W's redirection folder does exists. I tried taking W's computer off the domain and putting it back.If the redirection works fine for a the same user on another PC it suggests the PC is at fault and not the server/network.
Redirected folders and Roaming Profiles are not the same thing. You can have either/neither or both. If the users have large amounts of stuff stacked on their desktops and in local profiles, pulling them accross every time a user moves to a different station can be a drag on network performance.
I have never found the need for roaming profiles as users in most small businesses do not hop around much. However, redirected folders is a must, imo, if the server has the capacity.
Hard to say with the information given exactly what went wrong. Folder redirection is a gpo, as is roaming profiles and should override any local settings.