I'm wondering if someone has solved this or at least has some guidance on how to approach it. I'm working on updating & locking down an older site that still uses CFmenu (yeah, legacy stuff is fun). I copied over the folders from an earlier CF install that are needed for CFmenu. After I ran the auto-lockdown tool, I'm stuck on how to get the site to serve files from the cf_scripts\scripts folder & subfolders. The lockdown tool created a virtual directory in IIS that points to the correct physical path in my install and updated the "Default ScriptSrc Directory" in CFAdmin/Server Settings/Settings. In the IIS manager app I can view the contents of the virtual directory and see the files there. If I create a "test.cfm" in any of the folders under the cf_scripts\scripts\ directory I can actually pull it up in a browser. However, trying to even browse to any js/css/gif files under the virtual directory gives me a 401.3 error even though it's in the exact same directory where the "test.cfm" file sits. The user that CF is running as has permissions to the files in the physical path and also in IIS to the virtual directory. So I'm wondering what has worked for someone else to get the CFMenu working again? Is it an IIS setting? Is it related to creating a mapping in CFAdmin under Server Settings/Mappings? Any help is appreciated.