Client has an intranet on EPiServer.
They want to put an ".lnk" file in the File Management. This is a desktop shortcut to an Outlook form. The target is:
"C:\Program Files\Microsoft Office\Office12\OUTLOOK.EXE" /c "IPM.Note.NOA"
It works when served from raw IIS -- downloading the file executes it and opens this outlook form, so I know downloading and running it should be fine.
However, it appears EPiServer won't upload it correctly --
When you upload it into EPiServer, it shows up in File Management as "OUTLOOK.EXE". When you download it, it indeed downloads a 12.6 MB file, named "OUTLOOK.EXE". This appears to be the actual Outlook executable, as I've verifed that it's the same exact size as the EXE in the Microsoft Office directory. (I tried running it, but it complains that a DLL is missing.)
What is going on here? It looks like uploading the .lnk file instead uploads the Outlook executable, which is the target of the shortcut. Has anyone ever seen this before?
I think this might be more to do with the way Windows (or maybe IE) works rather than something EPiServer specific. I am guessing Windows tries to helpfully resolve the target of the shortcut when pointing to a file in the file upload browser rather than the shortcut itself. In this question the target is Outlook.exe so thats what gets uploaded.
Have you tried this on a standard file upload on a non-EPiServer site to test this?
Also it seems you are not alone in experiencing this behaviour: