ClipMate's registration keys are not "hardware locked" in any way, and all users can share the same key, provided that it's licensed for enough "seats". To allow for automated installations, a registration key file (.ini file) can be placed into the directory where the setup program runs from. If found, it'll enter the registration key into the program, so that neither the IT staff nor the end-user are ever confronted with the "enter key" dialog.
Here is the structure of the ClipMate.ini file:
If you place this file into the same directory as the setup program, it will be copied into the program directory (usually c:\program files\ClipMate7). It'll be used one time to register the program automatically, and then the "Key" line is deleted.
In order for the registration key to successfully recorded, it must be run one time with administrator privileges. If this throws a monkey-wrench into your deployment plans, there is another option that doesn't require admin rights. Use the ClipMate.ini file as above, but change the "KEY" to "PORTABLEKEY" like this:
By using this format, the registry is not used to store the key, and thus, no admin rights are needed. Unlike the "KEY=" option (above), the PortableKey line is not deleted from the file.
Tip: On a workstation that is already registered, you can go to Help | Enter Registration Key, and there is a button that will create the ClipMate.Ini file, with the PortableKey option.
Trivia: PortableKey is named so because it was developed for use on portable devices like USB keychains and such. It's a standard setting with many programs protected with Armadillo 4 or later.
If there are some standardized settings that should
be replicated onto all users, this can be done by replicating the
registry branch with your deployment tools:
This can be used to pre-select database directories, temp files, and the "application profile", which "filters" inbound data formats for optimal performance when capturing clipboard data.
Pre-loading the registry can be used to pre-select the database location, either to avoid end-user confusion during the first run, or to prevent them from storing the database in an undesirable location. By default, the database is stored in the "application data" area, as directed by the registry. This is typically:
C:\Documents and Settings\<user>\Application Data\Thornsoft Development\ClipMate7
On a network domain, this may be re-directed to the server. This may or may not be desired by the server and network administrators.
Departments or workgroups may wish to have shared databases for common clips. Typically, they'll have their own database locally (or in their designated spot on the server) and then will have a second, shared database for workgroup clips. We have many helpdesk and customer service customers who use it this way. They have "canned responses" to common questions, which are available for anyone to paste. This can also be defined during installation, with the settings pre-populated into the registry with your software deployment tools.
The database consists of 22-24 files of .DAT .IDX and .BLB extensions. Single-user databases can be backed up with the internal backup mechanism, which is just a ZIP library that makes a ZIP of the database files. Likewise, the "restore" unzips a backup and inserts the contents into the database directory. Knowing this, you can easily "pre-populate" a new user's database with clips that they may need to do their job. An example would be a work-from-home customer service rep who needs access to the database of common support Q&A, but doesn't have a fast VPN connection to the server. In this case, just send them the backup, and have them restore the database from that backup.
The new XML Import/Export capability of ClipMate 7.1 gives you some interesting options with data deployment. Instead of distributing a database backup, which overwrites the user's database, you can "merge" an XML file into an existing database. Just export the clips of interest, distribute the XML file, and each user can import those clips and collections into their database. If the process is repeated later, clips can actually be updated on the target.
Suppose Sally manages a customer support center for a company that sells/services MP3 players. She has a ClipMate database with canned responses to common problems, and wants to share those clips with all service representatives. She's got them all in a series of collections, starting with "support". Below that, she's got "power", "download", "firmware", "LX1" (the model of their current MP3 player), and "misc".
She can right-click on the "support" collection, and select "select all clips in child collection", which gives a big selection of ALL of these clips. Then she uses File | XML Export to make a file.
She distributes the file to co-workers, who import it. Now they have all of these collections too.
Next month, there is new firmware for the LX1, so several clips change. And now there is the LX2, so there's a series of new clips. She can run a query to export the clips that are new/changed, re-export, and everybody else can merge the updates into their databases.
Multi-User pricing discounts are available! See pricing.htm
We are ready to assist your IT staff in evaluating, configuring, and deploying ClipMate throughout your department or enterprise. Contact us for details.