Novell ZENWORKS ENDPOINT SECURITY MANAGEMENT 3.5, Installation Manual, Page: 61 / 76

Endpoint Security Client 3.5 Installation 61
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
8.2.2 Distributing a Policy with the MSI Package
The default policy included at MSI installation can be replaced with an enterprise-configured policy.
To push down a specific policy with the MSI image:
1 Create a policy to be distributed to all users through the Management Console (see the
ZENworks Endpoint Security Management Administration Guide for details on Policy
Creation).
2
Export the policy, then it as
policy.sen
.
STRBR=ReallySuppress No reboot after install completes. Security enforcement and client self
defense are not fully functional until
after the first reboot.
STBGL=1 Strict white list enforcement on
application control. A policy MUST be created that
identifies the application on the white
list, and distributed with this policy.
STUPGRADE=1 Upgrade the Endpoint Security Client
3.5. Use when upgrading the Endpoint
Security Client 3.5.
STUNINSTALL=1 Uninstall the Endpoint Security Client
3.5. Use when uninstalling the Endpoint
Security Client 3.5. For detailed
uninstall instructions, see
“
Uninstalling the Endpoint Security
Client 3.5 ” in the ZENworks Endpoint
Security Management Administration
Guide
.
STUIP=password Uninstall with password Use when an uninstall password is
active.
STNMS=”MS Name” Change the Management Service
name. Changes the Management Service
name for the Endpoint Security Client
3.5.
POLICYTYPE=1 Change Endpoint Security Client 3.5
to machine-based policies. Use to change MSI-installed Endpoint
Security Clients to accept machine-
based, rather than user-based
policies.
POLICYTYPE=2 Change Endpoint Security Client 3.5
to user-based policies. Use to change MSI-installed Endpoint
Security Clients to accept user-
based, rather than machine-based
policies.
STVA=”Adapter name” Add Virtual Adapter. Use to activate policy control over a
virtual adapter
/L*v c:\log.txt Turn on logging. Use to activate logging at installation.
If not, this will have to be done
through the Endpoint Security Client
Diagnostics tools (see Administrator’s
Manual).
Command Line Variable Description Notes