FS6200 Server System Implementation Guide - Public Support ...

Operating the Server
Audits
• LAN Manager Authentication Level is set to “Send LM and NTLM — use NTLMv2
session security if negotiated.”
Notes:
• To change this setting if necessary on the JProcessor Specialty Engine, I/O engine,
E-mode engine, or systems management engine, use the Local Security Policy
option available in Administrative Tools in Control Panel.
• The MCP Environment is preconfigured with NTLMv2 authentication enabled. If you
decide to disable NTLMv2 authentication in the MCP Environment, consult the topic
“Client Access Services Authentication Changes” in the Migration Guide for Local
Security Policy changes that are required in an environment to restore the ability to
authenticate using MCP Client Access Services.
Auditing is the process that tracks user activities and records selected types of events in
the Windows security log. An audit policy defines the type of event information that
should be collected. The MCP Firmware Environment Policy settings are listed in Table
4-3.
Table 4–3. MCP Firmware Environment Policy Audit Policy Settings
Event Name Security Log Records
account logon Success, Failure
account management Success
directory service access Success
logon/logoff Success, Failure
object access Success
policy change Success
privilege use Not audited
process tracking Success
system events Success, Failure (except the ″Filtering Platform
Connection″ and ″Other Object Access
Events″ subcategories)
To support the potentially large amount of auditing events, Security Event Log size has
been increased to 2GB. You can modify the auditing policy and the Security Event Log size
according to your corporate policy and specific usage characteristics.
MCP Firmware Environment Policy Utility Scripts
Two utility scripts are provided to manage the MCP Firmware Environment Policy. The
scripts are written with PowerShell.
4–12 8222 3694–000