IBM AS/400e, Руководство пользователя

Страница: 508 / 834

Operating System/400, 5769-SS1
478
AS/400e System Handbook
users do not need to do configuration. Client Access Express meets these needs by
delivering:
• Microsoft System Policy Support: Each time a PC is started, system policies are
downloaded from a server to the PC and enforced through Microsoft System Policies.
Client Access provides policy templates for use with the Microsoft System Policy Editor.
The Client Access for Windows 95/NT added support for Microsoft policies in its last
refresh (V3R2M0), and the Express client has built onto this support to enable AS/400
administrators more control over which Client Access functions are available to PC users.
Administrators can create, edit, and change policy information and could, for example:
– Prevent a specific user from running the Client Access Data Transfer to upload or
download data. Users can be restricted from creating a new file but allowing them to
append data to an existing file, or they can use only predefined transfer requests.
Additionally you could restrict users from running batch uploads/downloads, GUI
uploads/downloads, autostart uploads/downloads, use of the Excel add-in, or restrict
an AS/400 server that a request may be run against in networks with multiple AS/400
servers.
– Restrict the use of Operations Navigator.
– Limit the number of PC5250 sessions a user can start on a per-AS/400 basis.
– Restrict AS/400 ODBC driver or OLE DB usage on a per-AS/400 basis.
– Disable users from changing their passwords or modifying the password expiration
warning time frame.
– Pre-configure a user’s AS/400 system connectivity. Then when the user starts a Client
Access function, only pre-configured systems would be available for use.
– Define policies by connection environment. For example, when a user is connecting
from the “home” environment, SSL is required. However, when using an “office”
environment, SSL is not needed.
Each time a PC is started, the system policies are downloaded from the server to the PC.
Policy restrictions can be enforced on a per-user or per-PC basis. This function can be
used with any supported OS/400 release.
• Operations Navigator Application Administration: Operations Navigator provides
an Application Administration function that can be used rather than System Policies for
administering the network. Where System Policy restrictions are downloaded to the
desktop and managed through the Microsoft Windows registry, Application
Administration restrictions are maintained in the AS/400 user profile. This customizing
then “roams” with the user. Administrators can:
– Identify which Operations Navigator functions can be used
– See which first-level and most second-level folders can be accessed
– Control the use of other applications registered to Operations Navigator