Procedure) - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING INFRANET CONTROLLER GUIDE REV 01 Manual

Configuring infranet controllers guide
Hide thumbs Also See for NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING INFRANET CONTROLLER GUIDE REV 01:
Table of Contents

Advertisement

Copyright © 2010, Juniper Networks, Inc.
Table 7: User Role Access Configuration Details (continued)
Option
Function
Enable Host
Enables Host Enforcer
Enforcer
on the endpoint and
sends Host Enforcer
policies to Odyssey
Access Client for this
role (Windows only).
Session start
Executes the script
script / Session
after the start or stop
stop script
of the OAC session.
odyssey-settings
Specifies the IC Access
and Preconfigured
Installer settings
Agentless tab
Chapter 6: Configuring User Roles and Administrator Roles
Your Action
Select this option to enable the Host Enforcer for
this role.
NOTE:
By default, after you enable the Host Enforcer
option on a role, Odyssey Access Client denies
all traffic on the endpoint except for the following
allowed types: traffic to and from the Infranet
Controller and Infranet Enforcer, WINS, DNS,
IPsec, DHCP, ESP, IKE, outgoing TCP traffic, and
some ICMP messages (for example, PING from
the endpoint to other devices is allowed).
Therefore, it's important that you configure Host
Enforcer policies to specify the additional types
of traffic you want to allow on each endpoint. For
example, you must configure Host Enforcer
policies to allow any incoming TCP traffic. See
"Configuring Infranet Enforcer Resource Access
Policies (NSM Procedure)".
To avoid blocking all traffic on endpoints and
preventing users from accessing all network and
Internet resources, we recommend that you
configure Host Enforcer policies to allow the
specific types of traffic on endpoints before you
enable the Host Enforcer option on a role.
Specify the location of the session start scripts /
session stop script you want to run on Windows
endpoints after Odyssey Access Client connects or
disconnects with the Infranet Controller. You can
specify a fully qualified path. Scripts can be
accessed locally or remotely by means of file share
or other permanently available local network
resource. You can also use environment variables,
such as %USERNAME% in the script path name.
For example:
\\abc\users\%USERNAME%\myscript.bat
Click the odyssey-settings button. See "Configuring
OAC Settings for a User Role (NSM Procedure)".
41

Advertisement

Table of Contents
loading

Table of Contents