About Templafy Desktop
Templafy desktop is the client Templafy uses to deploy add-ins for MS Office.
Please see the following article for pre-requisites for installing Templafy:
Pre-reqs for installing Templafy
If any issues arise during the installation of TemplafyDesktop.msi, please add the below switch to add logging which will help to troubleshoot the installation:
/lvd* "log.txt"
Installation in Current User context
Templafy Desktop installs as default into Current User context (HKCU) and the .msi installer does not require admin rights for installation.
MSIEXEC /i TemplafyDesktop.[tenant].msi /quiet
Installation in Local Machine context
Templafy Desktop can also be installed in Local Machine context (HKLM). Whether to install in Current User or Local Machine is determined by a parameter setting that should be added when deploying via SCCM.
Run this command in an Admin/Elevated prompt or using SCCM:
MSIEXEC /i TemplafyDesktop.[tenant].msi ALLUSERS="1" /quiet
For every user that logs into the targeted PC, Templafy Desktop will start in the Current User context. This is to ensure that many of our features will be able to run without requiring admin rights or changing permissions on shared folders.
The Templafy Desktop.msi will download the Client version to %programdata% which is shared between users on a machine and holds non-office specific features, such as Offline Synchronization and Font Distribution.
The client version will then install the VSTO addin into %localappdata% and sync offline files to this location, as all users do not necessarily have access to the same files.
Installation in Citrix
Templafy Desktop can be installed on Citrix VDI environments.
For Published Apps, such as Citrix XenApp, it greatly depends on your current setup, and you might have to preregister the Registry Keys that loads the addins 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 can't active update of Templafy Desktop and packages.
To update, Admins will need to run the following command. This can be run on the Citrix image, or it can be configured to run every night on all Citrix Servers.
To install Templafy Desktop, Run this command in an Admin/Elevated prompt or using SCCM:
Note that Templafy Desktop for citrix must be enabled in Templafy before you can install it on a citrix server. Contact Templafy to have this option enabled.
Templafy Desktop installation paths
Current User
%localappdata%\Templafy\Desktop
The application itself is installed in this location
%localappdata%\Templafy\AddIns
The addins for Office is installed here via Templafy Desktop
Local Machine and Citrix
%programdata%\Templafy\Desktop
The application itself is installed in this location
%programdata%\Templafy\AddIns
The addins for Office is installed here via Templafy Desktop
Shared
%ProgramData%\Templafy\Desktop\Packages\[contenthash-package-x].zip
Cache for the addin deployment package
%LocalAppData%\Templafy\Desktop\Packages\installed.xml
An installed.xml file is maintained that tracks which files and registry settings have been added using Templafy Desktop
%appdata%\Microsoft\Signatures
Email 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)
%temp%\Templafy
All 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.
%temp%\TemplafyLog
Addin specific error logs are stored here.
Templafy Desktop Registry Entries
Registry Keys are either installed into HKCU or HKLM based off if Templafy Desktop is installed with the ALLUSERS="1" parameter
Templafy Desktop settings
- [HKCU or HKLM\SOFTWARE\Templafy] *
- "Url"="https://xxx.templafy.com/"
- "Token"="xxx"
- [HKCU or HKLM\Software\Templafy\Desktop\Options]
- "TemplafyOptions"="ServerMode"
- [HKCU or HKLM\Software\Microsoft\Windows\CurrentVersion\Run]
- ...\Templafy.Desktop.exe
- [HKCU or HKLM\SOFTWARE\Templafy\Desktop]
- "UpgradeRequired"="False"
* URL and Token are copied from HKLM to HKCU on first user login
Templafy addins Registry Enries
Certificate
- [HKCU or HKLM\Software\Microsoft\SystemCertificates\TrustedPublisher\Certificates\XXX]
Addin manifest file location and Office activations
- [HKCU or HKLM\Software\Microsoft\Office\Excel\Addins\Templafy.OfficeVstoAddIns.Excel]
- [HKCU or HKLM\Software\Microsoft\Office\Outlook\Addins\Templafy.OfficeVstoAddIns.Outlook]
- [HKCU or HKLM\Software\Microsoft\Office\PowerPoint\Addins\Templafy.OfficeVstoAddIns.PowerPoint]
- [HKCU or HKLM\Software\Microsoft\Office\Word\Addins\Templafy.OfficeVstoAddIns.Word]
- "Description"="Templafy VSTO Add-ins "
- "FriendlyName"="Templafy Word Add-in "
- "LoadBehavior"=dword:00000003
- "Manifest"="...\Templafy\\AddIns\\Templafy.OfficeVstoAddInsWord.vsto|vstolocal"
Office specific user settings (Add-ins)
- [HKEY_CURRENT_USER\SOFTWARE\Templafy\OfficeAddIns\Outlook\16.0]
- "EmailSignatureTimestamp"="XXX"
- "EmailSignatureChecksum"="XXX
- [HKEY_CURRENT_USER\SOFTWARE\Templafy\OfficeAddIns\”OfficeName”\”Office Version”]
- “HasUserSettings”=”True”
Internet Explorer Browser Emulation *
- [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION]
- "POWERPNT.EXE"=dword:00002710
- "WINWORD.EXE"=dword:00002710
- "EXCEL.EXE"=dword:00002710
- "OUTLOOK.EXE"=dword:00002710
* Templafy uses Internet Explorer to show content in Office and to ensure the same result across different versions, by setting a different default document mode for the web-browser control of all Office applications.
Comments
0 comments
Please sign in to leave a comment.