Advertisement
SQL user name and password official character set for the patch 5 installer
Allowed
Exceptions (for both usernames and passwords, except as noted)
2.
Issue: Cluster installation on Windows 2008 server is not supported.
Workaround: Cluster users should not migrate to Windows 2008 at this time.
3.
Issue: If the master repository is locked, package check-in fails, causing the installation to fail and roll back.
Workaround: Ensure that there are no repository actions that conflict with the installer. These actions can be currently
running or regularly scheduled repository pulls or replications.
4.
Issue: If a previous Patch installation is successfully completed with a database user configured to use a non-default
database schema, the following tables are created:
<schema used>.OrionExtensionsBackup
<schema used>.OrionConfigurationBackup.
The existence of these files causes the Patch 5 installation to fail. (Reference: 461433)
Workaround: Delete these tables and try the installation again.
5.
Issue: When using Windows 2008 ePolicy Orchestrator servers, a blank "Domain" selection drop-down list appears when
the user tries to browse for systems while adding new systems to the System Tree in the ePolicy Orchestrator console.
(Reference: 391040)
Workaround: On Windows 2008 servers, the McAfee ePolicy Orchestrator 4.0.0 Application Server service must have
sufficient permissions to complete the request. For more information, see KB article KB53861.
6.
Issue: On Windows 2008 ePolicy Orchestrator servers, external commands are not executed. (Reference: 433570)
Workaround: On Windows 2008 servers, the McAfee ePolicy Orchestrator 4.0.0 Application Server service must have
sufficient permissions to complete the request. For more information, see KB article KB53862.
7.
Issue: During a cluster installation, the IP address for a client system appears as 128.0.0.0 after an agent push.
(Reference: 435257)
Workaround: After the first successful communication, the IP address reflects the correct address.
8.
Issue: When the SQL Server "Nested Triggers" option is disabled, policy assignment timestamps are not updated. This
causes ePolicy Orchestrator to fail to deliver full policies to client systems. (Reference: 406765)
Workaround: Verify that the "Nested Triggers" SQL Server option is enabled for the ePolicy Orchestrator database. For
more information, see KB article KB52512.
9.
Issue: Modifications to policies are not written to the audit log unless they are from Host Intrusion Prevention policies.
(Reference: 470204)
Workaround: None.
Resolved issues
Issues that are resolved in this release are listed below.
1.
Issue: If an administrator changes the "Agent-server secure communication keys," non-Windows agents will not use the
new key(s). (Reference: 366792)
No leading backslashes, trailing backslashes, or passwords made up of solely backslashes (\)
No dollar signs ($)
No percent signs (%)
Usernames cannot contain a colon (:)
Usernames cannot contain a semi-colon (;)
All printable characters with a hex value of 0x20 – 0x7E (ASCII 32 through 126), with exceptions
listed below.
No leading space, trailing spaces, or passwords made up of solely spaces
No double quotes (")
No single quotes (')
No backslashes (\)
No percent signs (%)
Usernames cannot contain a dollar sign ($)
Usernames cannot contain a colon (:)
Usernames cannot contain a semi-colon (;)
Password size restriction
Passwords must not exceed 40 bytes in length. For multi-byte characters, this limits the
password to a maximum of 20 characters.
Advertisement
