SoftGrid: Mapped network folder invalidates on virtualized application streaming

When a virtualized application was streamed to a client, the client could no longer view the contents of a folder on a mapped network drive that contained files needed by the user. The user could see that the folder existed but the contents of the folder were incorrect. Cause: The application had been sequenced using […]

When a virtualized application was streamed to a client, the client could no longer view the contents of a folder on a mapped network drive that contained files needed by the user. The user could see that the folder existed but the contents of the folder were incorrect.

Cause: The application had been sequenced using the same path as the mapped network drive (e.g. T:\AppName).  Since the virtualized application and the mapped network drive were using the same path, SoftGrid would effectively take precedence in any calls made to that path.

Resolution: Assuming you don't want to use a different path for the mapped network drive/folder, the solution to this problem is to re-sequence the application but instead of installing it to T:\AppName (or whatever the path may be), install it to T:\AppX (or any path other than T:\AppName).

Source:→ SoftGrid Blog