| Reference Number |
Related Article |
Found in SAE Version |
Resolved in SAE Version |
Issue Description |
| 1243566 |
|
3.5.0 Patch 6 |
3.5.0 Patch 6 Extension Hotfix 1239261 |
Issue: You are unable to add multiple sites to the Prohibit List with the Add Multiple option, when using ePolicy Orchestrator (ePO) 5.9. This issue does not occur with ePO 5.3.
Workaround: Add sites to the Prohibit List one at a time with the Add option.
Resolution: This issue is resolved in SAE 3.5.0 Patch 6 Extension Hotfix 1239261. |
| 1239261 |
KB90546 |
3.5.0 Patch 6 |
3.5.0 Patch 6 Extension Hotfix 1239261 |
Issue: The SAE 3.5.0 Patch 6 extension fails to check in to ePolicy Orchestrator (ePO) 5.3. This issue does not occur with ePO 5.9.
The ePO console shows the following error:
Unexpected error occurred
The ePO orion.log shows an error similar to the following:
2018-04-30 10:42:22,230 ERROR [http-bio-8443-exec-1] ext.InstallScriptImpl - runTask Error= C:\PROGRA~2\McAfee\EPOLIC~1\server\extensions\installed\SITEADVMETA\3.5.0.395\install.xml:83: com.mcafee.orion.core.cmd.ErrorCodeCommandException: No such command: SITEADVMETA.cmd.licenseSetup
Resolution: This issue is resolved in SAE 3.5.0 Patch 6 Extension Hotfix 1239261. See the related article for more information. |
| 1229381 |
|
3.5.0 Patch 5 |
3.5.0 Patch 6 |
Issue: Firefox Web Extensions in version 55 and later cause a mismatch between the extension version and the client version because of the Electrolysis (also known as E10S) feature.
Resolution: This issue is resolved in SAE 3.5.0 Patch 6. |
| 1229379 |
|
3.5.0 Patch 5 |
3.5.0 Patch 6 |
Issue: Firefox Web Extensions in version 55 and later cause the SAE toolbar menu to fail because of the Electrolysis (also known as E10S) feature.
Resolution: This issue is resolved in SAE 3.5.0 Patch 6. |
| 1229376 |
|
3.5.0 Patch 5 |
3.5.0 Patch 6 |
Issue: Firefox Web Extensions in version 55 and later cause the mouseover balloon to not display because of the Electrolysis (also known as E10S) feature.
Resolution: This issue is resolved in SAE 3.5.0 Patch 6. |
| 1216857 |
|
3.5.0 Patch 5 |
|
Issue: The Content Actions policy is not displayed under Assigned Policies or Policy Catalog for SiteAdvisor Enterprise if you install extensions in the following order: EXTSITEADVCFMETA, EXTSITEADVLICMETA, EXTSITEADVMETA. This issue is in the user interface only and there is no data loss. Policy edits and assignments are still preserved.
Workaround: To prevent this issue, install extensions in the following order: EXTSITEADVMETA, EXTSITEADVCFMETA, EXTSITEADVLICMETA. If you have already encountered the issue, uninstall and reinstall the EXTSITEADVCFMETA extension. The Content Actions policy displays. |
| 1216854 |
|
3.5.0 Patch 5 |
|
Issue: The Content Actions policy is not displayed under Assigned Policies or Policy Catalog for McAfee SiteAdvisor Enterprise if you upgrade only the extension EXTSITEADVMETA. This issue is in the user interface only and there is no data loss. Policy edits and assignments are still preserved.
Workaround: Upgrade the EXTSITEADVCFMETA extension. The Content Actions policy displays. |
| 1216383 |
KB89947 |
3.5.0 Patch 5 |
3.5.0 Patch 5 Repost 4 |
Issue: Because of changes in Mozilla Firefox 56, SAE web protection does not load in the browser.
Resolution: This issue is resolved in SAE 3.5.0 Patch 5 Repost 4. See the related article for more information. |
| |
KB88952 |
3.5.0 Patch 5 |
As Designed |
Issue: Chrome reports the SAE extension version as 3.5.0.1275 when a different version of SAE is installed.
Explanation: This behavior is expected. Chrome displays the version of the SAE extension hosted in the Google Play Store, not the version of the locally installed SAE Chrome extension. See the related article for more information. |
1204890
1168932 |
KB89602 |
3.5.0 Patch 5 |
|
Issue: Installation of SAE 3.5.0 Patch 5 fails. The SAE Launch Extended.Log contains the following error:
[2017-07-18 10:28:47:128] [I] [BootstrapSetup.cpp] IsVSCoreInCompatible 130 iMin & iActual (15) @ index [0], are same; Continuing comparison for the remaining version components.
[2017-07-18 10:28:47:128] [I] [BootstrapSetup.cpp] IsVSCoreInCompatible 118 Installed VSCore version doesn't meet expectations; iIterationCounter [1], iMin [4], iActual [1].
Hence declaring VSCore's Version as Incompatible.
Resolution: Deploy a McAfee product that includes VSCore 15.4.0.649.22 or later (for example, VirusScan Enterprise 8.8 Patch 7 or later). See the related article for details.
|
| 1183692 |
KB88889 |
3.5.0 Patch 5 |
3.5.0 Patch 5 Repost 3 |
Issue: Searches conducted from the Google Chrome Omnibox bar can result in a blank page being displayed.
Resolution: This issue is resolved in SAE 3.5.0 Patch 5 Repost 3. See the related article for more information. |
| 1163732 |
KB88697 |
3.5.0 Patch 5 |
|
Issue: SAE events cannot be sent from one ePolicy Orchestrator server to an ePolicy Orchestrator roll up reporting server.
Status: This functionality will not be added in SAE. See the related article for more information. |
| |
PD25670 |
3.5.0 Patch 4 |
|
Issue: The SiteAdvisor Enterprise 3.5 Patch 4 Release Notes (PD25670) list an incorrect release date and build number.
Resolution: The release date for SAE 3.5.0 Patch 4 is October 7, 2015. The build number for the SAE client is 3.5.0.1365. |
| |
|
3.5.0 Patch 4 |
As Designed |
Issue: Because of changes from Mozilla, users can disable the SAE extension in Firefox on the endpoint.
Resolution: This behavior is expected. The SAE hardening policy cannot prevent the user from disabling the SAE extension. Every 30 minutes the SAE service checks that the status of the SAE extension is enabled. |
| 1125704 |
KB87238 |
3.5.0 Patch 4 |
3.5.0 Patch 6 |
Issue: SAE add-ons in Internet Explorer show as Not Verified.
Workaround: You can safely ignore this value because SAE still functions in Internet Explorer.
Resolution: This issue is resolved in SAE 3.5.0 Patch 6, which is signed by an SHA-2 certificate. This certificate makes the extension appear as verified in Internet Explorer. See the related article for more information. |
| |
PD25669 |
3.5.0 Patch 3 Hotfix 1015409 |
|
Issue: The file name for standalone installations is listed incorrectly in the SiteAdvisor Enterprise 3.5.0 Patch 3 Hotfix 1015409 Release Notes (PD25669).
The file sae_3.5.0.1278_hf1015409.zip is what you check in to the ePolicy Orchestrator Master Repository. This .zip file has a pkgcatalog.z, installation script, detection script, and saehotfix1015409-3.5.0.1278.1.exe.
Resolution: For standalone installations, run saehotfix1015409-3.5.0.1278.1.exe. |
| 1050861 |
KB85495 |
3.5.0 Patch 3 |
3.5.0 Patch 4 |
Issue: The SAE block page does not display in non-English operating systems.
Resolution: This issue is resolved in SAE 3.5.0 Patch 4. See the related article for details. |
| |
KB84983 |
3.5.0 Patch 3 |
3.5.0 Patch 4 |
Issue: ePolicy Orchestrator does not process SAE events if the URL is over 1024 characters.
Resolution: This issue is resolved in SAE 3.5.0 Patch 4. See the related article for details. |
| |
KB84254 |
3.5.0 Patch 3 (3.5.0.328) |
3.5.0 Patch 3 (3.5.0.333) |
Issue: SAE 3.5.0 Patch 3 (3.5.0.328) extension events are not parsed by ePolicy Orchestrator. SAE requires MSXML 4 be installed on the ePolicy Orchestrator server for events to be parsed.
Resolution: Use the repost SAE 3.5.0 Patch 3 (3.5.0.333) extension, which no longer requires MSXML 4 to parse events. See the related article for details. |
| |
KB84982 |
3.5.0 Patch 3 |
3.5.0 Patch 4 Hotfix 1076106 |
Issue: SAE 3.5.0 Patch 3 does not support Firefox 40.
Resolution: This issue is resolved in SAE 3.5.0 Patch 4 Hotfix 1076106. See the related article for more information. |
| 1074921 |
KB85082 |
3.5.0 Patch 2 |
3.5.0 Patch 3 |
Issue: SAE 3.5.0 Patch 2 events are not parsed by ePolicy Orchestrator 5.3.
Resolution: This issue is resolved in SAE 3.5.0 Patch 3. See the related article for more information. |
| |
KB79591 |
3.5.0 Patch 2 |
As Designed |
Issue: The SAE 3.5.0 Patch installation is stopped and the SAE installer prompts for a system restart if a browser window is open when the installation task runs.
Resolution: This behavior is expected. Allow the system to restart, which causes the SAE 3.5.0 installer to complete the installation of the SAE 3.5.0 Patch. See the related article for more information. |
| |
|
3.5.0 Patch 2 |
As Designed |
Issue: The SAE 3.5.0 extension can cause error messages (for example, 'Use caution with this file download') when managing SAE 3.0 clients.
Resolution: This behavior is expected. Upgrade SAE 3.0 clients to SAE 3.5.0 and manage SAE 3.5.0 clients only with the SAE 3.5.0 extension. |
| |
KB79967 |
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: SAE 3.5.0 Patch 2 does not support Firefox 26.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. See the related article for more information. |
| 928846 |
|
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: When browsing to a secured website, SAE does not display the secure logo annotations.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 923239 |
|
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: The SAE safety balloon displays incorrect licensing product information.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 923218 |
KB79654 |
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: For SAE 3.5.0 Patch 2, the Zero day protection policy setting is set to Block by default.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. See the related article for more information. |
| 901368 |
|
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: Installing SAE 3.5.0 Patch 2 and a hotfix together over Patch 1 installs only the hotfix and the Patch 2 installation fails.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 911304 |
KB79305 |
3.5.0 Patch 2 |
|
Issue: The SiteAdvisor Enterprise 3.5 Patch 2 Installation Guide (PD24660) incorrectly lists information about SAE 3.5.0 Patch 1. See the related article for more information. |
| 907783 |
KB78225 |
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: Internet Explorer 10 is supported only with Microsoft Windows 8.0.
Resolution: SAE 3.5.0 Patch 2 Hotfix 923218 adds support for Internet Explorer 10 with Windows 7. See the related article for more information.
NOTES:
- This issue was previously resolved in SAE 3.5.0 Patch 2 Hotfix 836656. To view the Release Notes, see KB81086.
- This issue was previously resolved in SAE 3.5.0 Patch 2 Hotfix 907783. To view the Release Notes, see KB79563.
|
| 883214 |
KB78453 |
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: If the McAfee Agent policy enforcement interval is the same as the event uploading interval, the events are not sent to the ePolicy Orchestrator server.
Workaround: Increase the McAfee Agent policy enforcement interval to greater than 30 minutes.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. See the related article for more information. |
| 873175 |
|
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: On Windows 8, the SAE service path might not contain quotes around McSAcore.exe.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 836656 |
|
3.5.0 Patch 2 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: The browser crashes when opening a website running a JavaScript application.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 835801 |
|
3.5.0 Patch 2 |
|
Issue: The SAE Secure Search add-on is not installed when using Firefox.
Workaround: Manually change the search engine on the client to the one set in the SAE policy in ePolicy Orchestrator. |
834335
834336 |
|
3.5.0 Patch 2 |
As Designed |
Issue: After deselecting the SAE policy option "Enable SiteAdvisor Toolbar", the toolbar is not hidden when opening a new tab. This issue affects Firefox 16, 17, and 18 and Chrome 24.
Resolution: This behavior is expected. Because of the way these browsers are designed, the user has to close all browser sessions for the policy changes to apply.
NOTE: This way is different from the way Internet Explorer works, where each tab runs in a separate Internet Explorer process and initialization gets called for each tab. That difference is why this issue does not occur with Internet Explorer. |
| 821133 |
|
3.5.0 Patch 2 |
As Designed |
Issue: SAE Secure Search is not set as the default in the Search provider list (Manage add-on) with the following Internet Explorer setting enabled: Prevent Programs from suggesting changes to my default search provider.
Resolution: This behavior is expected. Administrators must enforce Group Policies to allow changes to the search engine settings or disable this option on the client. |
| 820861 |
|
3.5.0 Patch 2 |
As Designed |
Issue: SAE Secure Search functionality is still available even when SiteAdvisor policy enforcement is disabled.
Resolution: This behavior is expected. When SAE is disabled on the client, users are still able to change the search engine because the search engine registry key is not hardened by SAE. |
| 812186 |
|
3.5.0 Patch 2 |
|
Issue: With Internet Explorer, the current tab shows the next tab SiteAdvisor toolbar ratings when the user opens a link from the current page in a new tab. |
| 811768 |
|
3.5.0 Patch 2 |
As Designed |
Issue: The SAE banner is not displayed. This issue can happen when an email is formatted with Rich Text Format (RTF), has links to red or yellow sites, and is opened in a web-based browser email application where the SAE client is installed. Also, no annotations are seen because the banner is not displayed.
Resolution: This behavior is expected. Set the web-based email application to use HTML. |
| 811763 |
|
3.5.0 Patch 2 |
As Designed |
Issue: When using Internet Explorer 10/11, the SAE toolbar is not compatible with Enhanced Protected Mode (EPM). The following system messages occur:
- 'McAfee SiteAdvisor Toolbar' isn't compatible with Enhanced Mode and has been disabled.
- 'McAfee SiteAdvisor BHO' isn't compatible with Enhanced Mode and has been disabled.
The SAE toolbar might also not be displayed.
Resolution: This behavior is expected. To make plug-ins compatible with EPM, see the following articles:
|
| 806614 |
|
3.5.0 Patch 2 |
As Designed |
Issue: No Patch or Service Pack details are provided after checking in or deploying the SAE 3.5.0 Patch 2 package to a client.
Resolution: This behavior is expected. SAE 3.5.0 Patch 2 is not an independent package, it is repackaged in with SAE 3.5.0. |
| 758155 |
|
3.5.0 Patch 2 |
|
Issue: SAE Events pushed to the Web Reporter server incorrectly display the IP address as 127.0.0.1 in an IPv6 environment. |
| 894359 |
KB78652 |
3.5.0 Patch 1 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: The SAE browser balloon displays incorrectly in Internet Explorer 10 on Windows 8 after installing SAE 3.5.0 Patch 1 Hotfix 809552.
Workaround: Implement one of the following:
- Set the zoom level of the browser to 100%.
- Use the SAE feature to disable the browser balloon. This action is possible only when SAE 3.5.0 Patch 1 Hotfix 809552 and SAE extension 3.5.0.290 are checked in, because these versions provide a new policy feature to enable and disable the SAE toolbar.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. See the related article for more information. |
| 822080 |
|
3.5.0 Patch 1 |
3.5.0 Patch 1 Hotfixes 788673 and 809552 |
Issue: SAE 'About' reports SAE as unlicensed for licensed installations.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1 Hotfix 788673 (Repost build 3.5.0.935), which is available from the Product Downloads site. Or, install SAE 3.5.0 Patch 1 Hotfix roll-up 809552, which is available from Technical Support. |
| 810025 |
|
3.5.0 Patch 1 |
3.5.0 Patch 1 Hotfix 809552 |
Issue: After you install SAE, some HTML links to open a new browser window no longer function or the browser stops responding.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1 Hotfix roll-up 809552, which is available from Technical Support. It adds a new policy option to disable the browser balloon. When you apply the policy update to the SAE clients, SAE no longer shows the browser balloon, but all SAE enforcement and safe search ratings continue to function. |
| 808772 |
KB77120 |
3.5.0 Patch 1 |
3.5.0 Patch 1 Hotfix 809552 |
Issue: File downloads are blocked when you enable the SAE file download enforcement policy.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1 Hotfix roll-up 809552, which is available from Technical Support. See the related article for more information. |
| |
|
3.5.0 Patch 1 |
As Designed |
Issue: SAE is not supported when accessing Microsoft Outlook emails via Outlook Web Access.
Resolution: This behavior is expected. |
| |
|
3.5.0 Patch 1 |
|
Issue: Enforcement messaging is left blank if there is a carriage return in the Enforcement messaging policy.
Workaround: To insert new lines in the Enforcement messaging policy, use the <br> tag. |
| 764401 |
|
3.5.0 Patch 1 |
|
Issue: SAE 3.5.0 Patch 1 is unexpectedly able to successfully downgrade from SAE 3.5.0 Patch 1 to SAE 3.5.0 RTW.
Resolution: Do not check in SAE 3.5.0 Patch 1 and SAE 3.5.0 Patch 1 Repost to the same branch of the Master Repository. |
762596
758257 |
|
3.5.0 Patch 1 |
As Designed |
Issue: Web Reporter hits are not sent to Web Reporter in a proxy server environment.
Resolution: This behavior is expected. |
| 759301 |
KB77215 |
3.5.0 Patch 1 |
3.5.0 Patch 1 Hotfix 809552 |
Issue: The McAfee Agent icon does not appear in the notification area on 64-bit operating systems.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1 Hotfix 809552. See the related article for more information. |
753134
759547 |
|
3.5.0 Patch 1 |
As Designed |
Issue: The administrator must edit the SAE Prohibit policy at least once to allow the policy to be applied to the client. This requirement applies to the situation when the SAE 3.0 policy is exported or imported, or upgraded to SAE 3.5.0 Patch 1.
Resolution: This behavior is expected. Change the imported Prohibit policy and enforce the policy. |
| 720302 |
|
3.5.0 Patch 1 |
As Designed |
Issue: The Rating Action policy is not enabled automatically when the CF extension expires.
Resolution: This behavior is expected because a valid CF extension is required. Uninstall the CF extension or check-in a licensed CF extension. |
| 713136 |
KB75844 |
3.5.0 Patch 1 |
As Designed |
Issue: After upgrading from SAE 3.0 to 3.5.0, SAE 3.5.0 places SAE in Observe mode until policies are applied. Users accessing Red or Yellow tagged sites are shown a message balloon stating "This site is allowed".
Explanation: SAE 3.5.0 clients need the SAE 3.5.0 Extension to be managed.
Resolution: This behavior is expected. Disable all clients using Observe mode before upgrading to SAE 3.5.0. See the related article for more information. |
| 708033 |
|
3.5.0 Patch 1 |
As Designed |
Issue: When a user selects to view Secure Content only, SAE annotation images are broken in web-based emails.
Resolution: This behavior is expected. The user must enable Compatibility Mode in Internet Explorer for web-based email annotations to work consistently. |
| 706162 |
KB75696 |
3.5.0 Patch 1 |
As Designed |
Issue: You see an application error when starting Internet Explorer after completing a custom SAE installation. This error is because the user selected a custom installation path that exceeded the 240 character path limit.
Resolution: This behavior is expected. When you perform a local installation and select a custom path, ensure that the path is fewer than 240 characters. Or, install silently to use the default program file's installation path, which is much less than the 240 character limit. See the related article for more information. |
| 702922 |
|
3.5.0 Patch 1 |
As Designed |
Issue: The SAE balloon shows only one category, even if Global Threat Intelligence (GTI) gives multiple category codes for the URL.
Resolution: This behavior is expected. Currently, the category with the most restrictive action is shown as a result. |
| 699528 |
|
3.5.0 Patch 1 |
As Designed |
Issue: SAE continues using previous proxy settings in an existing browser session. This issue occurs when the proxy server details are changed in the SAE policy, but both the previous and new proxy servers are present and reachable by the client.
Resolution: This behavior is expected. The new proxy server settings do not take effect until one of the following occurs: the SAE service is restarted, a Global Threat Intelligence (GTI) outage occurs, or the original proxy server becomes unavailable (shut down) in the existing sessions. |
| 693628 |
|
3.5.0 Patch 1 |
|
Issue: In an IPv6 environment, SAE cannot connect to Global Threat Intelligence (GTI) Technical Support sites and obtain ratings. SAE logs show the message "host lookup on tunnel.web.trustedsource.org failed".
Workaround: SAE can rate websites in a pure IPv6 environment if there is proxy or NAT that will convert IPv6 to IPv4 traffic. |
| 692422 |
|
3.5.0 Patch 1 |
3.5.0 Patch 2 Hotfix 923218 |
Issue: You see incomplete prohibit Enforcement Messages with the 'My default' policy.
Workaround: Create a duplicate policy and enforce the policy.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2 Hotfix 923218. |
| 582284 |
KB75843 |
3.5.0 Patch 1 |
As Designed |
Issue: If you install Outlook after SAE, the SAE Microsoft Outlook email annotations are not shown in the Outlook viewing pane.
Resolution: This behavior is expected. Restart the client after installing Outlook. See the related article for more information. |
| 580668 |
|
3.5.0 Patch 1 |
|
Issue: The SAE policy does not accept the IPv6 notation with a Zone ID in a link-local or site-local address format. |
| 759301 |
|
3.5.0 |
3.5.0 Patch 2 |
Issue: SAE fails if the Web Gateway Interlock policy is behind a proxy that uses NTLM authentication.
Resolution: This issue is resolved in SAE 3.5.0 Patch 2. |
| 729794 |
KB73562 |
3.5.0 |
3.5.0 Patch 1 |
Issue: No ratings are provided when SAE resides behind a proxy.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1. See the related article for more information. |
| 700802 |
|
3.5.0 |
As Designed |
Issue: During an SAE network outage, the Troubleshoot link in Show Balloon does not start the Troubleshooting SiteAdvisor Communication Errors page in Internet Explorer.
Resolution: This behavior is expected. Deselect Enable Protected Mode (requires restarting Internet Explorer) from Tools, Internet Options, Security, Local Intranet. |
695715
704804 |
|
3.5.0 |
As Designed |
Issue: If SAE 3.5.0 is installed first and then VirusScan Enterprise is installed, SAE hardening rules are not enforced.
Resolution: This behavior is expected. From the Services console, restart the SAE Service. |
| 586727 |
|
3.5.0 |
As Designed |
Issue: When SAE is deployed on a client computer where Microsoft Outlook is open, SAE annotations do not appear in emails containing malicious information.
Resolution: This behavior is expected. Close and reopen Microsoft Outlook for the annotations to appear in emails containing malicious information. |
| |
KB73419 |
3.5.0 |
3.5.0 Patch 1 |
Issue: Application Control, Host Intrusion Prevention, and VirusScan Enterprise might cause the installation of SAE to fail when installed locally.
Resolution: This issue is resolved in SAE 3.5.0 Patch 1. See the related article for more information. |
