KeyReporter HTTPS
|
Connecting
to KeyReporter via SSL (https) will present more configuration options
for KeyReporter. You will need to set KeyReporter to listen on the
HTTPS port (or custom port) via the standard configuration page. Once
connected via HTTPS, you can set KeyReporter to generate reports from
an external data source and a few other additional options.
|
|
| KeyReporter RSS |
| KeyReporter
can be set to deliver reports via RSS. Depending on password access,
any report viewed via a browser can be set to be delivered via RSS. |
|
| Managing Users |
| To
manage
Users, you can implement external authentication. KeyServer will make a
call to your external authentication schema (AD, LDAP, etc.) where
Users (& Groups) are identified. The KeyConfigure Groups window
will then be populated via this schema and then can be used to manage
licenses. |
|
| K2 Mobile client |
| If
you wish
to take advantage of KeyCheckout - to allow users to check out "keyed"
applications - they will need to install the K2 Mobile client. If the
default client agent is already installed (using the regular client
installer), you will need to first de-install KeyAccess and then
install K2Mobile client to get access to installer option for
KeyCheckout. |
|
| ODBC Driver |
| Please be
aware there is a known issue between Windows 32 bit applications and 64
bit operating systems. View the MS KB
on this. If
you host your KeyServer on a 64 bit Windows operating system, either
create a user
DSN (not system
DSN) or use a 32 bit ODBC driver. |
|
| Printing Histograms in KeyReporter
|
| Within
Internet Explorer (8) select Page Setup and check on the Print
Background Colors & Images checkbox. For earlier versions of IE
this setting is in the Internet Options/Printing section.
Alternatively, download report from Archive section as a KSR report and
open within KeyConfigure and print from there. |
|
|
| KeyServer SiteID Registry
key |
You
may want to use KeyServer to identify which SOE build is deployed for
any particular PC.
You could do this via 2 methods. First is if you have the ability to
create custom executables. Create an exe that has the SOE build in the
name of the exe and then deploy and discover that exe per PC.
Second method is to populate the "computerSite" field. This is a free
text registry field (63 chars), and can be set per SOE build.
Located here:
HKLM\SYSTEM\CurrentControlSet\Services\
KeyAccess\Settings\options\site
and for Mac:
/Library/Preferences/
com.sassafras.KeyAccess.plist in the "site" property.
Then you can view this field within KeyConfigure for sorting
purposes.
|
|
| KeyConfigure - CTRL Refresh |
| KeyConfigure,
the admin console, works on a
local cached copy of data
tables to ensure speedy response. If you have multiple administrators
working on KeyConfigure at the same time, it is a good idea to do a
"hard" refresh of the Computers and Programs list every so often. This
brings down a full refresh from the KeyServer to the local
KeyConfigure. Hold down the "CTRL" key and hit the "refresh" button on
the lower left of the Program or Computers window. |
| KeyConfigure - Date
Expiration |
| You
can create a hard
expiration date on any license - by selecting the license/Options/
Expiration Date. This is useful if you want to select a future date
when a license is no longer available for use (for support contracts,
etc.) |
|
| KeyAccess - Registry Key |
The
location of the address for the KeyServer is stored on the local client
within the registry key for KeyAccess. The location is:
HKLocalMachine/System/CurrentControlSet/
Services/KeyAccess/Settings/logon/host
|
| KeyConfigure - Legacy reports |
If you're a fan of the
old legacy reports in KeyConfigure:
sassafras k2/admin/report
modules/reportmenu.xml
change the "no" below to "yes", save and close:
<group name="Legacy" hidden="no">
<class>lgcy</class>
</group>
<!-- customized = no -->
to = yes
|
|
|
