Hi everyone
Today I wanted to talk a symptom you might hit if you do content redirection with RemoteApp for a remote office while, the user click on a file located on a remote file share.
The symptom is a file lock can happen for the person and that block the document’s saving.
That cause a bug in example Word or Excel that throw an error that the file is already in use. The user need to re-save the document to another name to save it when that happen.
The cause is simple; The content redirection access the share via the tsclient’s client redirection. That force the remote computer to retrieve the file and send the file to the TS’s server to be able to use the content redirection.
I did that small chart;
In my scenario the impact appear when the remote office got a high latency’s link. You can see the RemoteApp connection got longer delay to open due to that fact.
To resolve the issue it’s all done in the way you map the drive to the users. Normal drive mapping cause this issue, while a mapping done via the network location wizard solve that issue, as the RemoteApp open directly the file so it prevent all the network discussion from happening.
I would call that network map VS network location method to access the file.
If you do the wizard’s mode to add a network location, it’s via Explorer that you can trigger the wizard:
If you want to push that via GPO, it’s where it become tricky .. You have to create a folder, an .ini and a .lnk for that folder..
In the GPO it’s a 3 step procedure.
- GPP to create a folder inside that folder; %APPDATA%\Microsoft\Windows\Network Shortcuts
Ie; %APPDATA%\Microsoft\Windows\Network Shortcuts\HR Department
2. GPP to create a desktop.ini inside that folder with two options set inside it;
Ie;
Action Mettre à jour
Chemin d’accès au fichier %APPDATA%\Microsoft\Windows\Network Shortcuts\HR Department\desktop.ini
Nom de la section .ShellClassInfo
Nom de la propriété CLSID2
Valeur de la propriété {0AFACED1-E828-11D1-9187-B532F1E9575D}
AND
Action Mettre à jour
Chemin d’accès au fichier %APPDATA%\Microsoft\Windows\Network Shortcuts\HR Department\desktop.ini
Nom de la section .ShellClassInfo
Nom de la propriété Flags
Valeur de la propriété 2
3. You set the link to the correct resource with a shortcut named target;
Type de cible Objet système de fichiers
Chemin de raccourci %APPDATA%\Microsoft\Windows\Network Shortcuts\HR DEpartment\target
Chemin d’accès de la cible \\fileserver\hr
Touche de raccourci None
Exécuter Fenêtre normale
After that, now your users can click inside those folder to navigate to the file share, and when they will click a resource MSTSC will open directly the file from the network share, bypassing the tsclient redirection !
Phil’s Blog | IT to the core ! 