The Shadows window (available from the Windows menu) lists every known KeyShadow, as well as the current state of the Shadow. KeyShadows can be configured by an administrator to avoid KeyServer service outages during network failures.
The Shadows windows list has three column headers: Location,
State, and Last Synchronized.
Within the list there is a group header named
KeyServer, which represents the actual KeyServer. Clicking on the
expansion icon on the left of the line will reveal the Shadows.
In the group header, the State column simply tells the number of clients
and the version of KeyServer.
- The Location column shows the address of each known shadow.
- The State column shows the current state of the shadow
(as far as the server can tell. Note that the server must be able to reach the shadow to determine
the state). The possible states are:
A KeyShadow will distribute licenses to users only when it is in the Serving
- Unknown Shadow is on the hint list but cannot be reached in order
to determine a more accurate state.
- Disabled Service for this shadow has been disabled for the given protocol. This
appears only in the KeyShadow State dialog for an individual shadow and
reflects only the Shadow state for a given protocol. When an entire shadow has been disabled it
no longer appears in the Shadows Window.
- Inactive The KeyShadow is inactive. Either the administrator deactivated
it, or it has provided emergency service for over seven days. It is not
- Offline Service for this KeyShadow is not being supported on the protocol
because for some reason the protocol is not working correctly on the shadow
- Registering The KeyShadow is initiating shadow service. It is not
distributing licenses when in this state. This state is temporary (less than 1
- Serving The KeyShadow has lost contact with the KeyServer due to network
failure or KeyServer machine failure, so it is distributing licenses to users.
For AppleTalk shadows, only one KeyShadow in each zone can be in this state at any given time;
an AppleTalk shadow will not register if there is already a shadow (or server) present in that
zone. Should the existing server or shadow become unavailable however, that second shadow will
take its place.
- Sleeping The KeyShadow has been put to sleep, or has not yet begun service
(soon after restart).
- Shadowing The KeyShadow is in contact with its parent KeyServer (in a
different zone), so it is not distributing licenses. This is the normal state.
- Waiting The KeyShadow is starting shadow service after being inactive. It
is not distributing licenses. This state is temporary (less than 1 minute
- Last Synched column shows when the shadow last synched up to the KeyServer
(got up to date program and policy configuration, etc).
The Shadows window shows the basic state of each known shadow. Double-clicking on a particular
shadow will contact the shadow to get further details, and open up a
Shadow Details Window.
Note that if the shadow cannot be reached from the server, no details window
will be opened, since all the information shown in the details window comes from