Before creating a package to deploy Snagit to your user-base, there are a few questions that must be considered about the structure of your environment, and how Snagit will behave in your environment. We recommend using the TechSmith Deployment Tool to create the transform (MST) and BAT files. The TechSmith Deployment Tool, along with additional documentation regarding enterprise deployment can be found here.
The Datastore is where Snagit will store all of the captures (video and images) for a particular user. The Datastore is also what makes up the Library within the Snagit Editor, where the user is able to organize their captures. The captures are maintained using the Snagit900.SDF file within the Datastore.
Questions to consider
- Where is the user profile information being stored (local disk, network path)?
- What would you like the Datastore to act as within your environment? For example, will it be a temporary storage location for that user's session (and all content will be deleted when that user logs off)? Or, will it be a permanent storage location that should be synced with that user’s profile?
Example 1: Persistent Desktop/Static Datastore Folder
This is the default installation location for the Datastore folder. In many environments the
%LocalAppData% is a persistent folder. A static folder such as
E:\F.Last\ can also be used.
Example 2: Session Based/Temporary Storage Folder
A common procedure is to delete the
%LocalAppData% folder when a user logs off of a client when using Remote Desktop Services. This setting is configured in Group Policy with the name "Delete cached copied of roaming profiles." When removing the local cached profile, the Datastore would effectively be deleted every time the user logs out of the client if left at the default location of
%LocalAppData%\TechSmith\Snagit\Datastore (and therefore all of the user's unsaved captures would be deleted).
In this case, it would be wise to prevent users from being able to change the location of the Datastore (automatically stored files location) when creating the MST via the TechSmith Deployment Tool.
This will force the Datastore folder to be created when the user begins a new session. If users were to leave this check box ticked, every time they start Snagit, they would be prompted with the message below.
Example 3: Permanent Repository
Many organizations elect to store
%AppData% information using folder re-direction (e.g roaming profiles) or user profile disks. Configuring the Datastore to be in
%AppData% may be an option in this case. It may be worth disabling Snagit from starting with Windows when creating the MST in order to give the client enough time to pull down the
If the size of the Datastore is a concern, consider disabling automatically storing all image and video captures when creating the MST. This particular setting would need to be adjust by installing Snagit on a test machine, adjusting the options in Snagit Editor Preferences > Library (1), and then choosing to "Customize Snagit registry settings by using this computer's settings" (2) when creating the MST.
This will force the user to manually save any images they wish to keep in their library , and will discard any that are not specifically saved by the user.
The Snag900.sdf file inside the Datastore is what organizes and maintains the Snagit Library. The Snagit Editor initializes the Snag900.sdf file when SnagitEditor.exe is launched, and is required in order to launch successfully. This file is a SQL Server Compact Edition Database File. Microsoft does not support running this type of file format from a network location.
Microsoft does not support running SQL CE files (Snag900.sdf) from a network location. If the Datastore is configured to be on a network location, the SDF file is cached into
%LocalAppData% on the client during the user's session. If
%LocalAppData% is being redirected, a sharing violation may occur when launching the Editor.
A possible workaround in this case would be to configure the Datastore to a local folder, for example
C:\SnagitTemp\, and also disable automatically saving image and video captures in the MST (see above).
Accessories are integrated sharing outputs for specific applications (for example, Microsoft Office, Dropbox, ect).
Questions to consider
- What sort of network restrictions are in place that may conflict with certain accessories? For, example, is YouTube blocked for your users on your network? If so, then the YouTube accessory should not be installed with Snagit.
- Should your users be able to download and install (or, uninstall) accessories at their own discretion?
If you would like to prevent your users from managing their accessories, you may consider having them installed into a Read only location for those users and disable the Snagit Output Manager using the TechSmith Deployment Tool (Snagit 13.0 or later).
Other user settings
Other settings, such as a user's QuickStyles, thumbnail icons, and TUDI information. This information does vary slightly from Snagit 12.x to Snagit 13.x, as shown below.
|Snagit 12||Snagit 13|
Questions to consider
- Similar to the Datastore, are these items that should be synced with your user profiles? Or, should this information be deleted at the end of each session? Usually, this is set to the same path as the Datastore.
What type of technology are you using to implement Snagit?
Snagit has been tested and is supported via the following technologies:
- Remote Desktop
- Streamed Application (AppV)
Snagit has not been tested in the following technologies:
- Published Application
- Application layering
Even though these technologies have not been tested and are not supported, it may be possible to configure Snagit to work in these environment, assuming that it would make sense to. For example, implementing Snagit as a published application would only allow Snagit to capture from the host, rather than the client, so this may not make sense for your environment. If you do find ways to implement Snagit in these technologies, we would love to hear from you! Please submit a ticket above to get in contact with our Support team.