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

Posted on 2014-08-20
Last Modified: 2014-08-27
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.
Question by:ibidata
    LVL 41

    Expert Comment

    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!)
    LVL 42

    Expert Comment

    by:Davis McCarn
    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.

    Author Comment

    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.
    LVL 42

    Accepted Solution

    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?

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    Read about achieving the basic levels of HRIS security in the workplace.
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
    In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

    761 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now