Are there any disadvantages to this idea?
Best answer by Vincent Doppenberg
View original
TSF_dotNET.exe versus TSF_CS.exe
Userlevel 5
+20
- Superhero
- 356 replies
We consider using TSF_dotNET.exe instead of TSF_CS.exe from a network share for starting the Windows GUI in a terminal server setup. This way we want to avoid the growth of the App Data folder.
Are there any disadvantages to this idea?
Are there any disadvantages to this idea?
The disadvantage of running TSF_dotNET.exe directly from a network share is that it will be impossible to replace the Windows GUI's binaries while it is in use by anyone. TSF_CS.exe circumvents this problem by copying the binaries of the Windows GUI to the user's AppData folder before running it from there.
However, the AppData folder should not grow endlessly when using TSF_CS.exe. TSF_CS.exe will always copy the Windows GUI's binaries to a folder with the same name as the folder on the network share. In doing so, it will overwrite the files at the target location, meaning that the size should always remain roughly 300MB. The only reason for the AppData folder to grow endlessly is that the name of folder containing the Windows GUI binaries on the network share is changed every time it is replaced by a new version. The best practice here is to replace the binaries in the folder, rather than deleting the folder and replacing it with a new one.
However, the AppData folder should not grow endlessly when using TSF_CS.exe. TSF_CS.exe will always copy the Windows GUI's binaries to a folder with the same name as the folder on the network share. In doing so, it will overwrite the files at the target location, meaning that the size should always remain roughly 300MB. The only reason for the AppData folder to grow endlessly is that the name of folder containing the Windows GUI binaries on the network share is changed every time it is replaced by a new version. The best practice here is to replace the binaries in the folder, rather than deleting the folder and replacing it with a new one.
Userlevel 2
+1
In such deployment scenarios it's a good idea to use the CachePath extended property. In the latest release (2018.3.18), environment variables such as %USERPROFILE% and %LOCALAPPDATA% are properly resolved.
See also: Extended properties - Thinkwise Docs
See also: Extended properties - Thinkwise Docs
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.