I have one user who is having trouble renaming their files within their redirected documents folder on our domain network. The client is Windows 7 Enterprise 32bit and all appears to be running well. The server where the files reside is Windows 2003 R2 and all permissions appear to be correct there. The user is the owner and has full control over all folders and files in their documents folder. Here is the odd thing. The user can rename the file in most cases, EXCEPT when trying to change the case of text. For example, the user has a file named, "file-SIV-date.pdf" and when they try to change it to "file-Siv-date.pdf", they are denied access. This happens ONLY when attempting to change case of text and nowhere else. I have had the user rename the file to twelve different things using twelve different methods and all work, except changing case of text. This is happening with all files in their redirected folder. The user, of course needs to be able to make this kind of change. Any ideas??James Nelson

This is indeed odd, I have successfully reproduced the problem. It seems that SetRenameInformationFile is what gives the access denied. Let me look into this further.Blogging about Windows for IT pros at www.theexperienceblog.com

I contacted Microsoft PSS on this and they have now reproduced the bug internally which is good. I am still waiting for more information about a solution.Blogging about Windows for IT pros at www.theexperienceblog.com

Thank you very much for your assistance! This is good news. JamesJames Nelson

Not so good news unfortunately, this behaviour is considered to be "by design". In pratice this means that it is not considered a bug and will therefore not be addressed (or perhaps it will be fixed but in that case it will happen in Windows 8...). This is not documented anywhere so I will write a blog post about it. Blogging about Windows for IT pros at www.theexperienceblog.com

Thank you very much for your assistance and interest Andreas! I understand that there isn't much left that can be done with MS on this topic, but I'm not so sure I buy that from them however. As the domain admin of my organization, I have the same exact permissions as the user on their folders and I can change the case of the text without issue. I think it is odd that the owner of a file cannot make that change, but a random administrator can. I'd like to know from MS how this is "by design"... Also, the user was able to make this kind of text case change before their files were redirected to a new server (old one failed), not to mention this only affects a single user and others are able to make this change on thier files. By design...really!?James Nelson

Maybe not so much by design after all, my guess is that this is something that was introduced when offline files was revamped from XP to Vista. I have shipped this feedback/bug for further review via "other" channels. I will not give up on this just yet :)Blogging about Windows for IT pros at www.theexperienceblog.com

A very common problem with Windows explorer is reported on all Windows help forums. I've seen people complaining about problem with long path files deletion. Some common problems with Windows Explorer people talk about: - Doesn't allow to delete files with long path names - Pops up error while deleting unwanted files or unnecessary files - Errors like: Access denied, sharing violation, source in use etc. I've found a very simple but smart solution for all these above mentioned common problems. A very simple but powerful tool to overcome these problems. Everyone who plays with the files must have this tool. Its compatible with all versions of Microsoft Windows. deletelongfile.com