Replicating Kappris CFF for Multiple Offices
For every print job, Kappris refers to its Central Configuration. It requires the following information:
- Kappris configuration, including paper types, print modes, printers etc;
- Snapshots, stored printer-specific settings;
- Printer priority lists, whether user-specific, workstation-specific or specific to some other entity;
- Print job logs
- Licence key
- .NET custom script/s
Central Configuration Folder contents
All shared information is stored in the Central Configuration Folder (CCF). This folder should be shared on your network and accessible to all Kappris users.
Settings: contains printer priority lists for all users/workstations and stationery if in use.
Snapshots: contains printer-specific settings
XMLData: contains print logs (optional)
All users required READ access to the CCF itself. Users needing to configure Kappris using the Kappris Control Panel (KpMgr.exe) will also need WRITE access to this folder.
ALL users require READ and WRITE access to the Settings, Snapshots and XML Data sub-folders of CCF.
There is an implicit pointer to the CCF in each local config.ini, which is in <PROGRAM_FILES>\Kutana\Kappris (the program folder) on each PC.
The relevant lines in this file will be similar to this:
Alteration of the path to kappris.ini is sufficient to point Kappris towards a different configuration.
In order to maximise efficiency, it may be favourable to replicate the CFF to a local server on each site. This means that users on a particular site would need to have a specific site version of config.ini that pointed to the CFF in their location.
The best way to facilitate this would be to use Group Policy to push out the correct config.ini file based on location or AD Group.
The actual replication process should of course be set up and managed by your IT department using whichever method they favour.