FRP: Create symlink or shortcut on a computer without FRP but to be access from a computer with FRP

[nlehoux]

Hello, thought it would be good to share an experience I 've got as I couldn't find anything about this.

I came out to a situation where we needed to move files from a share (Share 1) to another share (Share 2) for some internal practical reasons.

The files on the Share 1 had to be move to Share 2 and a symlink was then created to allow users to still be able to access their files with no impact for them.

It turns out that because the files were encrypted we got a hard time to make this use case to work. 

The main difficulties was that the migration of the files and the creation of the symlink were done from a server without FRP.

The problem was that each encrypted files appear from a computer without FRP with a special character (0xECF0) at the end of the extensions. That character is used by FRP to identifies the encrypted files. This made the user when opening the file from the symlink to choose the application to open the file with because extension+ special character wan't knwon by windows.

The solution we found was to adapt our script to remove that special character.

Another issue we got in our way but this one was due to how PowerShell works was that PowerShell tests the actual targets during its creation and because the full path of the file was changed due to the extension - special characters we had to use cmd which doesn't do this check during the creation of the Symlink.

This issue is the same with shortcut or hardlink and the solutions are the same.

[aschumac]

Very useful!