Summary
ClinSpark Agent version 1.3.1 introduced a ‘properties’ file as a configurable mechanism to enhance certain integrations and capabilities with Zebra printer devices. Starting in Agent version 1.5.0, there is now improved support for implementation and use of the Agent ‘properties’ file across site installations.
Today sites commonly rely on the properties file to setup network printing configurations that can be shared across data collection machines. Full details on networked printing setups are documented in this article.
Prior to Agent 1.5.0, use of the Agent installation and upgrade process would replace any existing .properties file with defaults contained in the installation MSI. If needing to retain previously established property files, sites would need to manually update or replace the file, and repeat this process across all of PCs where the Agent is installed/upgraded.
...
For most sites, the location of the properties file will be the local user AppData\Roaming directory, which is the same directory that the Clinspark Agent log file is located . For example:
...
Further details about how this variable can be used for networked printing can be found in this article.
%APPDATA%
Overwhelmingly this environment variable will be present on local workstations and will likely be the default location of the properties file.
...
Customers wanting to see a technical demonstration of this topic can review the following screencast.INSERT VIDEO HERE
...
Using SET commands
In the screencast, use of the SET command is demonstrated. However, when using the SET command in command prompt to establish environment variables, they are only being written for the current shell session.
...