|My-T-Mouse®: for Windows; Indestructible Keyboards and Indispensable Utilites; Version 1.78 Release 4; User's Guide|
This section outlines relevant information if My-T-Mouse is going to be imaged via hard disk replication, incorporated into a different installation package, or handled externally from the publically provided installation approaches. Please refer to the other sections in this chapter to have a basic level of understanding regarding the files and issues involved in the installation of My-T-Mouse
This is a quick summary of the 3 steps typically used to prepare a master image - for more details and reference information, see below
Install the software. It is recommended you do not run the software until after the duplication.
Copy in custom configuration (if necessary). If configured on a separate system, refer to My-T-Mouse Setup | File menu | Show Config File Location for location of configuration files.
Copy in company/site/deployment license (if applicable) - replace LICENSE.LIC in Installation folder.
There are 3 main areas that need to be managed: Deployment, Default Configuration, and Licensing
The goal of this step is to ensure that all the required files are on the target system. For practical purposes, these are simply all the files and folders in the Installation folder, e.g. \Program Files\MYTMOUSE. Often, the default installation method can be used, with post installation management of configuration and license details handled after the installation.
When Imaging, the basic approach is to install the software onto the master system, then perform any updates to configuration and license files, and then DO NOT RUN the software (as settings and files can be modified by running the software).
For actual installation (i.e. including the software with an existing application), it is best to wrap the files into the existing application installation approach. Refer to the Zip files in the extended download area, as these are the installation files without any installation add-ons - these are just the program files that need to be installed on a system in a compressed, single file zip format. Often it is easiest to have a test system where normal installation / testing can take place, and refer to the information here, the post installation files on the test system, and also the MANIFEST.TXT text file (a post-build snapshot of the product files) in the installation folder for file details.
Doing folder comparisons, or simply testing on the target system (after imaging/installation), is the preferred approach to ensure the software has been deployed correctly.
The configuration is contained in the KEYBOARD.KBF / MYTMOUSE.INI files (and the MAC*.KMF files if the macro panels are used). Typically making sure the desired (correctly configured) files are the files in the installation folder is all that is necessary to bring a new/different default configuration when the software is run.
The simplest steps to create the desired configuration files are to configure the software as desired, then use the menu to Save Current Settings, and also Save Position. To test, re-start the software and verify the configuration is correct. Then obtain the KEYBOARD.KBF / MYTMOUSE.INI file (refer to the ConfigPath setting / or use Setup | File menu | Show Config File Location), and use these on your master image or as part of the installation files.
After duplication, when a new user runs the software, they will receive a copy of these default configuration files from the Installation Folder. They will then have their own personal copy which can be configured as they desire. This is the default setting of the software (ConfigPath=1). Note there are different approaches that could be taken with these configuration files based on the ConfigPath setting and permissions - for example, a fixed configuration for all users that cannot be modified.
Note: If secure logon is required, the Logon Utilities require a registry entry in the WinLogon group, which is not managed by installation or via the configuration files. This option requires proper configuration via the Logon Utilities.
If using the default (retail) license scheme, you just need to ensure that the file LICENSE.LIC in the installation folder is the same as LICENSE.ORG (the as shipped license file). If using any other type of license, refer to notes and instructions that were provided to you. In most cases, this means that you will have been provided a custom LICENSE.LIC file, and this must be the file installed as LICENSE.LIC.