been created. (Reference: 450163, 480057)
Resolution: The download credentials for source repository sites can now be edited.
12. Issue: Checking a new agent package into the ePolicy Orchestrator repository does not always update the ePolicy
Orchestrator list of supported platforms correctly. (Reference: 467664)
Resolution: Checking a new agent package into the ePolicy Orchestrator repository correctly updates the ePolicy
Orchestrator list of supported platforms.
13. Issue: In some environments, repository pulls from HTTP source repositories might never finish. (Reference: 453274)
Resolution: A new registry setting has been created to work around this issue. The new registry DWORD value is called
"RawHTTPDownloadSocketsOnly" and exists in the HLM\SOFTWARE\Network Associates\ePolicy Orchestrator key.
{
A value of 1 changes the HTTP pull functionality to use Windows Sockets (Winsock).
{
A value of 0, absence of a value, or absence of this key provides the pre-existing pull functionality using Windows
Internet (WinINet).
14. Issue: Replication of specific, selected packages to a distributed repository can intermittently fail if multiple replication
tasks are running simultaneously. (Reference: 462653)
Resolution: A concurrency problem with multiple running replication tasks has been resolved.
15. Issue: The Extra DAT package cannot be deployed to additional platforms without a patch to ePolicy Orchestrator each
time additional platform support is required. (Reference: 397874)
Resolution: The supported platform list for Extra DAT packages can now be updated without requiring a patch to ePolicy
Orchestrator.
16. Issue: The failure to push an agent can result in the ePO server not being able to create new network mappings, which
can cause pushagent commands and replication to UNC repositories to fail. (Reference: 449780)
Resolution: UNC network resource handles are now returned to the operating system after an agent push failure.
17. Issue: The removal of non-Windows agent packages from the ePolicy Orchestrator master repository prevents agent
update tasks from detecting that a new master server key has been assigned. (Reference: 463964)
Resolution: The removal of non-Windows agent packages no longer prevents agent update tasks from detecting new
master server keys.
18. Issue: The Roll Up server task can intermittently process the same computer twice, causing failure of the task and
computers not to be imported. (Reference: 446354)
Resolution: Computers are now processed only once each, and the server task completes successfully.
19. Issue: Threat-based notification rules can be triggered for non-threat events if the product and category filters of the
rules are satisfied. (Reference: 461917)
Resolution: Threat-based notification rules now are triggered only for threat events.
20. Issue: During an Active Directory synchronization, disabled computer accounts were being imported into ePolicy
Orchestrator. (Reference: 439191)
Resolution: Disabled computer accounts in Active Directory are no longer imported into ePolicy Orchestrator.
Note: If the ePO administrator has configured the Active Directory synchronization to "remove deleted systems" from
the System Tree, deleted systems and disabled systems are automatically removed at the next Active Directory
synchronization.
21. Issue: Installation for ePolicy Orchestrator 4.0 fails if the password for SQL includes the dollar ($) character. (Reference:
461677)
Resolution: The "$" character is now an acceptable character for the SQL password. For a complete listing of allowed
characters for your ePO and SQL user names and passwords, refer to the first entry under Known Issues (above).
