Standalone Systems; In Case Of A Failure - Studer OnAir 3000 Operating Instructions Manual

Hide thumbs Also See for OnAir 3000:
Table of Contents

Advertisement

5.10.9.2

Standalone Systems

Standalone Console:
With Central User
Management Server:
5.10.9.3

in Case of a Failure...

Document generated: 10.10.14
Of course, the concept described above also works for a standalone console.
However, for a standalone console without central user management the
server is not required. The user extension runs locally on the core sub-system,
and it can be configured (in the user.xml file) to provide up to 64 users
and 16 policies.
If more users or policies are required, or if users need to be managed centrally
even on a standalone system, an additional sub-system must be started on the
server to run the central user extension. The user extension running locally
then only provides the Admin and Default user's parameters, as described
above.
User Extension
on:
Console
Console
Server
Failure of the central user management server or the network connection has
the following consequences:
• Login is possible as Admin only.
• The configuration tool provides access to the local user configuration only
(i.e. for the Admin and the Default user). A user configuration made while
the central user management server or the network connection is down
will be overwritten as soon as the central user extension re-appears on the
network.
But: • No consequences for the privileges of the user currently logged in, as they
are saved on the sub-system locally.
• Logout remains possible.
SW V6.0
OnAir 3000 Digital Mixing Console
Users
Policies
Comment
max.
max.
As specified by the user.xml file
64*
16**
(Defaults: *20 and **8, resp.)
User configurations of the Admin and the
2
2
default users are replicated to each console
4096
255
As specified by the user.xml file
Operation 5-135

Advertisement

Table of Contents
loading

Table of Contents