About this article
Templafy Desktop is the client Templafy uses to deploy add-ins for Microsoft Office and Templafy Desktop can be installed on Citrix VDI environments. In this article we will explain how to deploy Templafy Desktop in a Citrix/RDS context.
For Published Apps, such as Citrix XenApp, it greatly depends on your current setup, and you might have to pre-register the registry keys that loads the add-ins in Office on the Citrix image manually.
On Citrix, %ProgramData% is locked and does not have Creator/Owner rights. Thus, users are not able to update Templafy Desktop or download Templafy Desktop Packages. For Citrix, users will not and cannot actively initiate an update of Templafy Desktop and packages.
Install Templafy Desktop
- Run below command in an Admin/Elevated prompt or using SCCM:
MSIEXEC /i TemplafyDesktop.[tenant].msi ALLUSERS="1" TEMPLAFYOPTIONS="ServerMode" /quiet
- Update Templafy Desktop
- Admins will need to run the following command(s). This can be run on the Citrix image, or it can be configured to run every night on all Citrix Servers.
Run as admin (for 32-bit):
Run as admin (for 64-bit):
Templafy Desktop installation paths
The Templafy Desktop Host is installed in this location
%programdata%\Templafy\DesktopThe Templafy Desktop Client is installed in this location
%programdata%\Templafy\AddInsThe addins for Office is installed here via Templafy Desktop Client
%appdata%\Microsoft\SignaturesEmail Signatures created via the Templafy addins are stored here. In the native Signatures folder for Outlook (“…\Signatures” may change depending on Office language installations and version)
%localappdata%\Templafy\Desktop\LogsLog files related to TemplafyDesktop is stored in this location (when updating)
%temp%\TemplafyAll assets (images, texts, shapes) inserted via Templafy addins are stored here temporarily. After the user exits the Office application using them, they will get deleted.