How do I remove existing short filenames from Windows 2008 Server (not R2)

I'm wondering if anyone can help me figure out how to remove existing 8.3 filenames from Windows 2008 Server.   I disabled 8.3 file naming in the registry but that is for any new files.  For any existing files I need to remove those 8.3 filenames.  

Windows 2008 R2 the fsutil has a command to remove them (fsutil 8dot3name strip /s /v K:\) but regular Windows 2008 Server (not R2) doesn't have that command.   I also read that I can copy a directory to a new directory and it will not have the short filenames.  The problem is that there are a lot of links, shares and applications that will break if I copy the directories to new directories.
ibidataAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kevinhsiehCommented:
First thought: why are you trying to do this?
Second thought: Copy the files to a new location and then copy them back to overwrite the originals.
Third thought: Shutdown the server and attach the disk to Windows 2008 R2 and then run fsutil on it.
Last thought: try to copy fsutil from later version of Windows and then run it. (Be SURE you have good backups!)
0
Davis McCarnOwnerCommented:
I was going to suggest logging in as an admin from a Windows 7 PC and doing it from there; but, after reading a bit, have hit a huge red flag!
If you strip the 8.3 names and any of your programs or clients reference an 8.3 filename, you're in serious kimchi.  Run regedit and search for ~ in the data field only.  If you find things like C:\PROGRA~1\ on the server or <shareddrive>:\MYDOCU~1\ on any client, you had better leave those 8.3 names alone.
0
ibidataAuthor Commented:
I'm doing this because there is an IIS tilde enumeration issue.  I agree with both of you and have some serious concerns with the fixes you present as well.  They made it so easy to fix in 2008 R2 so you would think there is an easy work around in 2008,  I'm thinking the command in 2008 R2 (fsutil 8dot3name strip /s /v K:\) strips those short filenames from the registry so if I can find out where or what that command is doing then I can just manually do it.
0
Davis McCarnOwnerCommented:
So grant full access to the IIS folder to somebody and run fsutil from a PC running 7 or R2; but, only strip the IIS folders.
And, no, fsutil doesn't touch any registry entries.
Did you find this?
http://weblogs.asp.net/scottgu/important-asp-net-security-vulnerability
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.