Technical Articles ID:
KB51111
Last Modified: 10/14/2021
Environment
McAfee VirusScan Enterprise (VSE) 8.x
McAfee Threat Intelligence Exchange Module (TIEm) for VSE 1.x
Microsoft Outlook Clients
Citrix Metaframe
Citrix Presentation Server 4.x
Citrix XenApp 6.x, 5.x
IBM Lotus Notes Client
Summary
Recent updates to this article:
Date
Update
October 14, 2021
Added Scan Engine 6300 support to the "Supported Engine version" section.
October 8, 2021
Added the End of Life date (December 31, 2021) for TIEm 1.0.3 and 1.0.2.
Updated the McAfee Agent supported table with links to all McAfee Agent compatible products articles.
July 14, 2021
Set several operating systems to End of Life (EOL): Windows Server 2003, Windows Server 2008, Windows Vista, Windows Embedded Standard 2009.
Added the VSE EOL date (December 31, 2021).
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
When Microsoft releases new operating systems or Service Packs, the original product guides might not reflect the current support policy for those platforms. Most of the following information is available in the product installation guides and Release Notes. But, some of the information is available only in Product Management statements published in the Knowledge Base.
Contents
Click to expand the section you want to view:
Product release information
McAfee Enterprise product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site.
WARNING: VSE 8.8 Patch 7 and earlier aren’tcompatible with the Microsoft Windows 10 Anniversary Update. Support for the Windows 10 Anniversary Update is included in VSE 8.8 Patch 8. Don’t install VSE 8.8 Patch 7 or earlier on systems running the Windows 10 Anniversary Update. Likewise, don’t upgrade systems running VSE 8.8 Patch 7 or earlier to the Windows 10 Anniversary Update.
IMPORTANT: All hotfixes listed below are rolled up into the next patch, or full product release. Patches are cumulative. Technical Support recommends that you install the latest one.
Product Version
General Availability (GA)
Released to Support (RTS)
VSE 8.8 Patch 3 was released to provide support only for Windows 8 and Windows Server 2012 operating systems. Patch 4 returns to being a single update, for use on all supported operating systems, for VSE 8.8.
This release was reposted on January 13, 2013. It included a new VSE 8.8 Patch 3 Management Extension to resolve the issue described in KB77066 - All VirusScan Enterprise policies are lost when VSE 8.8 Patch 3 fails to check in successfully.
2
IMPORTANT: [Upgrade considerations] The VSE 8.8 Patch 4 package doesn’t upgrade from VSE 8.8.0.777 (General Availability) or VSE 8.8.0.849 (Patch 1), if installed to a 64-bit system. To update with the Patch 4 package, you must follow the following upgrade paths:
On 64-bit systems, first install Patch 2 or later, and then Patch 4.
On 32-bit systems, first install Patch 1 or later, and then Patch 4.
Or, uninstall VSE 8.8.0 and reinstall with the latest patch.
Adds support for ePO 5.1, contains Management Extension 368, and Reports Extension 236.
Adds support for Windows 8.1 and Windows Server 2012 R2. Intended for all supported operating systems.
IMPORTANT: Patch 4 updates only VSE 8.8.0 clients, with Patch 1 (32-bit) or later, or Patch 2 (64-bit) or later.
3
With the release of Patch 6, VSE 8.8 now supports in-place upgrades. This feature means that on a Windows 7 or Windows 8.x computer with VSE 8.8 Patch 6, you can upgrade to Windows 10, without uninstalling VSE. But, uninstalling before the upgrade is a best practice.
Make sure that appropriate security permissions are enforced when the Access Protection feature is enabled. Doing so allows for a successful migration to the new AAC-based Access Protection engine.
4
VSE 8.8 Patch 6 and later, is supported for use with Windows 10 RTM (1507 build 10240) and Windows 10 Threshold 2 (1511 build 10586).
5
VSE 8.8 Patch 6 doesn’t support the Secure/UEFI feature of the Windows 10 Threshold 2 (1511 build 10586) release. Support for this feature requires Patch 7.
VSE 8.8 Patch 8 Hotfix 1159675 is mandatory for Windows Server 2016 support. This hotfix uninstalls Microsoft Windows Defender from Windows Server 2016. Removal is needed when you run VSE on Windows Server 2016. The reason is because of possible performance-related issues when you run more than one default security application.
8
VSE 8.8 Patch 15 build 8.8.0.2232.34 was released to address an installation issue. The issue is documented under reference VSE-16828 in the article below. NOTE:The ending digits (.34) apply to the package number, and isn’t be reported as part of the installed product version.
The following tables list the McAfee Enterprise products supported for use on Windows workstation and server operating systems.
NOTES:
VSE is committed to delivering support for new Windows releases within 60 days of Microsoft announcing their General Availability release.
We are often asked whether there are any known issues on a new platform, before our Support Statement is released. We can confirm that there’s a minimal issue with the Buffer Overflow Protection. This feature doesn’t work on new platforms until it’s has been updated with needed code changes. This change is typically done as part of the next update, for those products supported on the newer platform. The Buffer Overflow Protection feature fails silently in these conditions. Other features are expected to work as usual. But, until supportability for later operating systems is added to this article, support for the newer platform can't be provided.
If your operating system isn’t listed
This managed product is supported based on the NT Kernel version used by the operating system, rather than the operating system (version) in question. For VSE, this support breaks down as follows:
Windows NT Kernels 1.x - 4.x aren’t supported.
Windows NT Kernels 5.x and 6.x are supported with VSE 8.8 (General Availability) Patch 7.
Windows NT Kernels 10.x is supported with VSE 8.8 Patch 8 and later. IMPORTANT: To determine which patch version supports the proper build of Windows 10.x, view the comparison chart.
To verify which Kernel version your operating system uses, press Windows+R, type cmd, and press Enter. This action returns your kernel version, for example:
Windows Embedded POSReady 2009: Microsoft Windows XP [Version 5.1.2600]
Windows Server 2012 R2: Microsoft Windows [Version 6.3.9600]
Windows 10: Microsoft Windows [Version 10.0.10240]
IMPORTANT:
Windows Server 2008 and Windows Vista are no longer supported for VSE Patch 16 and later.
Windows XP and Windows Server 2003 aren’t supported. Patch 7 is the last patch that can install on these systems. Only customers with extended support contracts are permitted to use the product on Windows XP and Windows Server 2003. See your extended support contract for details. This statement also applies to Windows Embedded Point of Service POSReady 2009 because this release shares kernel as Windows XP.
Workstation operating systems
NOTE: Where applicable, both 32-bit and 64-bit versions are implied. Exceptions are noted explicitly.
IMPORTANT:Unless otherwise stated, all specific Windows Workstation editions are fully supported. Any exceptions, such as support for Windows Embedded, are called out where needed, and might also have a footnote. Examples of Workstation editions covered by this support are: Basic, Business, Enterprise, Home, Professional, and Ultimate.
Operating System
Minimum
Supported
Service Pack (SP)
Patch Versions
P16
P15
P14
P13
P12
P11
P10
P9
P8
P7
P6
P5
P4
P3
P2
P1
Windows 10 version 21H1
-
Yes
No
No
No
No
No
No
No
No
No
No
No
No
.No
Windows 10 Version 20H2 (October 2020)
-
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
Windows 10 version 2004 (May 2020)
-
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
Windows 10 version 1909 (October 2019)
-
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
Windows 10 version 1903 (May 2019)
-
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
Windows 10 version 1809 (October 2018)
-
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
Windows 10 version 1803 (April 2018)9
-
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
Windows 10 version1709 (Fall Creators Update)7
-
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
Windows 10 version 1703 (Creators Update)7
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
Windows 10 version 1607 (Anniversary Update)7
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Windows 10 version 1511 (November Update) 7
Windows 10 version 1507(General Availability) 7
Windows 10 IoT Enterprise 5, 6
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Windows 10 S 8
-
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Windows 8.1 August 2014 update rollup
Windows 8.1 Update 1
Windows 8.1
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes 4
No
No
No
Windows 8(Win NT 6.2)
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes 3
Yes 1
No
Windows 7
With/Without SP 1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No 3
Yes
Yes
Windows 7 Professional for Embedded Systems 6
Windows 7 Ultimate for Embedded Systems 6
With/Without SP 1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No 3
Yes 2
No 2
Windows Vista
With/Without SP 1 and 2
Operating system is EOL (January 25, 2007)
Windows Vista Business for Embedded Systems 6
Windows Vista Ultimate for Embedded Systems 6
For Windows Embedded to be supported (minimum requirements), see KB60902.- VirusScan Enterprise 8.8 support for Windows Embedded. NOTE:Thin clients and Enhanced Write Filtering (EWF) or File-Based Write Filtering (FBWF) technology isn’tsupported. Embedded operating systems are the same as their standard counterparts, except for licensing.
3
VSE 8.8 Patch 3 was originally released to provide support only for Windows 8 and Windows Server 2012 operating systems. Patch 4 returns to being a single patch for use on all supported operating systems for VSE 8.8.
4
Windows 8.1 requires at leastMcAfee Agent 4.8.2 to be supported. So, install MA 4.8.2 or later, at your earliest convenience, See KB51573 - Supported platforms for McAfee Agent 5.x. NOTE: MA 4.8.2 is now End of Life. MA 5.x are now the only supported versions.
5
VSE 8.8 requires Patch 6 to support Windows 10 and Windows 10 Threshold 2 (Win10 TH2). Patch 6 doesn’t support the Secure or UEFI feature of the TH2 release.
6
If an issue is reproduced on an embedded system, it must also be reproducible on a non-embedded operating system, for Technical Support to investigate.
7
VSE supports the following Windows 10 branches: Current Branch (CB), Current Branch for Business (CBB), and Long-Term Servicing Branch (LTSB).
8
Windows 10 S doesn’t support traditional desktop applications and doesn’t allow kernel level access for security vendors.
9
This release supports Windows 10 Spring Creators Update 2018 (Version 1803).
NOTE: VSE doesn’t support Universal Windows Platform (UWP) and there are no current plans to support UWP.
Server operating systems NOTE: Where applicable, both 32-bit and 64-bit versions are implied. Exceptions are noted explicitly.
IMPORTANT: Unless otherwise stated, all specific Windows Server editions and types are fully supported. Included are the core versions of all supported server operating systems. Any exceptions, such as support for Windows Embedded, are called out where needed, and might also have a footnote. Examples of Server editions covered by this support are: Advanced, Datacenter, Enterprise, Essentials, Foundation, Standard, Terminal Server, Web, and HPC.
Microsoft Operating System
Supported
Components
Minimum
Supported
Service
Pack
VSE
8.8
P16
VSE
8.8
P15
VSE
8.8
P14 P13
VSE
8.8
P12
VSE
8.8
P11
P10
VSE
8.8
P9
P8
VSE
8.8
P7
P6
P5
P4
VSE
8.8
P3
VSE
8.8
P2
VSE
8.8
P1
Windows Server 2020 version 20H2
-
Yes
No
No
No
No
No
No
No
No
No
Windows Server 2019 version 2004
-
-
Yes
Yes
No
No
No
No
No
No
No
No
Windows Server 2019 version 1909
-
-
Yes
Yes
Yes
No
No
No
No
No
No
No
Windows Server 2019 version 1903
-
-
Yes
Yes
Yes
No
No
No
No
No
No
No
Windows Server 2019 version 1809
-
-
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Windows Server 2016 core
-
-
Yes
Yes
Yes
Yes
Yes
Yes 11
No
No
No
No
Windows Server 201610
Cluster 2, 3
Hyper-V
Storage
Core 6
-
Yes
Yes
Yes
Yes
Yes
Yes 11
No
No
No
No
Windows Server 2012(Win NT 6.2)
Cluster 2, 3
Hyper-V
Storage
Core 6
-
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes 5
Yes 4
No
Windows Server 2012 R2 August 2014 update rollup
Windows Server 2012 R2 Update 1
Windows Server 2012 Release 2 (R2)
Cluster 2, 3 Hyper-V
Storage
Core6
-
Yes
Yes
Yes
Yes 7
Yes 7
Yes 7
Yes 7
No
No
No
Windows Small Business Server 2011
n/a
With
Or
Without
SP 1
Yes
No
No
No
No
No
Yes
No5
Yes
Yes
Windows Server 2008
Editions:
Standard1
Enterprise
Datacenter
Foundation (Special Edition)
Web (Special Edition)
HPC (Special Edition)
Cluster 2, 3
Hyper-V
Storage
Core 6
Operating system is EOL (January 14, 2020)12
Windows Server 2008 Itanium
(Special Edition)12
n/a
-
Operating system is EOL (January 14, 2020)12
Windows Server 2008 Release 2 (R2)12 NOTE: See footnote for Standard1
Cluster 2, 3, 8
Hyper-V
Storage
Core 6
With Or Without SP 1
Operating system is EOL (January 14, 2020)12
Windows Server 2008 R2
Server Itanium (Special Edition)
n/a
-
Operating system is EOL (January 14, 2020)12
Windows Small Business Server 2008
n/a
2
Operating system is EOL (January 14, 2020)12
Windows Server 2003
Cluster 2, 3
Storage
Core 6
2
Operating system is EOL (December 31, 2015)9
Windows Server 2003 R2
Cluster 3
Storage
Core 6
2
Operating system is EOL (December 31, 2015)9
Windows Small Business Server 2003
n/a
2
Operating system is EOL (December 31, 2015)9
Windows Small Business Server 2003 R2
n/a
2
Operating system is EOL (December 31, 2015)9
n/a = not applicable
1
The General Availability (GA) version of Windows Server 2008 'About' screen, shows the version as Windows Server 2008, Build 6001: Service Pack 1. This version is the base version and Service Pack 1 is included.
2
VSE supports a shared disk model and doesn’t interfere with the cluster failover process. The services installed with VSE aren’t cluster aware and aren’t installed as a failover group resource. You must install VSE separately on each node of the cluster. If the active node fails, it doesn’t have any impact on the VSE installations on the surviving nodes. When the node comes back online, VSE continues to operate as normal.
McAfee Enterprise didn’t fully certify Patch 2, but it’s compatible with Windows Server 2012. Full support for Windows Server 2012 is provided in the VSE 8.8 Patch 3 release.
5
VSE 8.8 Patch 3 was originally released to provide support only for Windows 8.0 and Windows Server 2012 operating systems. Patch 4 returns to being a single update for use, on all supported operating systems for VSE 8.8.
6
Windows Server Core releases can be supported only when managed by ePO. Server Core for Windows Server is a minimal server installation, where there’s no Windows shell, and limited user interface (UI) functionality. This reason is why the standalone installation of VSE can't support it. ePO is a requirement because the VSE console can't function properly without the needed fonts, for example marlett.ttf.
7
Windows Server 2012 R2 requires at least McAfee Agent 4.8.2 to be supported. So, install MA 4.8.2 or later. NOTE: MA 4.8.2 is now End of Life. MA 5.x are now the only supported versions.
Windows Server 2003 reached EOS and EOL for VSE, on December 31, 2015. VSE 8.8 Patch 7 and earlier install and run on Windows Server 2003, but isn’t supported with VSE. Upgrade your server to a supported version of Windows as soon as possible.
10
Server Core mode: VSE 8.8 Patch 8 Hotfix 1159675 isn’t supported when Windows Server 2016 is installed in Server Core mode.
For details of a known issue, see KB88819 - VirusScan Enterprise installation on Windows Server 2016 fails in the Server Core mode. Nano Server mode: VSE uses the Microsoft Windows Installer, which isn’t included in the Nano installation of Windows Server 2016.
11
VSE 8.8 Patch 8 Hotfix 1159675 is mandatory for Windows Server 2016 support, but can be installed immediately after VSE 8.8 Patch 8 is installed.
12
Microsoft ended mainstream support for Windows Server 2008/2008 R2 on January 13, 2015 and will end extended support on January 14, 2020. For details, see the Windows Server documentation. For best results and optimal security, upgrade to a newer supported operating system.
Compatibility with Citrix
Citrix Variant
VSE 8.8
Patches
6, to 16
VSE 8.8
Patch 5
Citrix Xen Guest
Yes
Yes
Citrix XenApp 7.5, 7.6
Yes
Yes
Citrix XenApp 5.0, 5.6, 6.0, 6.5 2
Yes
Yes
Citrix Presentation Server 4.5 1
No
No
Citrix Presentation Server 4.0 1
No
No
Citrix Metaframe 3.0 1
No
No
Citrix Metaframe 1.8 1
No
No
Citrix Metaframe XP 1
No
No
1
These product names have changed to Citrix XenApp, from version 5.0.
2
Hotfix Rollup 6 is needed for XenApp 6.5, because it solves an application hang symptom when a scan timeout occurs.
ePolicy Orchestrator (ePO)
The ePO version must be currently supported to be used with VSE, and is subject to change. The table below covers the VSE Product Extension, Management Extension, and Reporting Extension.
Product
ePO
5.10
ePO
5.9.0
ePO
5.3.x
ePO 5.1.x
VSE 8.8 Patch 16
VSE 8.8 Patch 15
Yes
Yes 1
EOL
EOL
VSE 8.8 Patch 14
Yes
Yes
EOL
EOL
VSE 8.8 Patch 13
Yes
Yes
EOL
EOL
VSE 8.8 Patch 12
Yes
Yes
EOL
EOL
VSE 8.8 Patch 11
No
Yes
EOL
EOL
VSE 8.8 Patch 10
No
Yes
EOL
EOL
VSE 8.8 Patch 9
No
Yes
EOL
EOL
VSE 8.8 Patch 8
No
No
EOL
EOL
VSE 8.8 Patch 7
No
No
EOL
EOL
VSE 8.8 Patch 6
No
No
EOL
EOL
VSE 8.8 Patch 5
No
No
EOL
EOL
VSE 8.8 Patch 4
No
No
EOL
EOL
VSE 8.8 Patch 3
No
No
EOL
EOL
VSE 8.8 Patch 2
No
No
EOL
EOL
VSE 8.8 Patch 1
No
No
EOL
EOL
VSE 8.8 (GA)
No
No
EOL
EOL
1
Supported from ePolicy Orchestrator 5.9.1.
Product Name
VSE 8.8 Patch 16
VSE 8.8 Patch 15
VSE 8.8 Patch 14
VSE 8.8 Patch 13
McAfee Active Response (MAR)
2.4.1, 2.4.3. 2.4.4
2.4.1,2.4.3
2.3.0, 2.4.1
-
Data Exchange Layer (DXL)
6.0.0
4.1.0
4.1.0,6.0.0
4.1.0
4.0.0.467, 4.1
Data Loss Prevention (DLP)
11.6.0
11.5.0
11.5.0
11.0.300
11.0.1162
Endpoint Security (ENS)
10.7.0
10.6.0, 10.6.1
10.5.5
-
-
-
McAfee Client Proxy (MCP)
2.4.0
3.1.0, 3.2.0
2.4.,3.1.0
2.4.0
2.4.0
Application Control (MACC)
8.2.1, 8.2.6
8.3.0, 8.3.1, 8.3.2
8.2.1, 8.2.6
8.3.0, 8.3.1, 8.3.2
8.2.1.435
8.0.0.651
SiteAdvisor Enterprise (SAE)
3.5.0 Patch 5, 6
3.5.0 (Patch 5, 6)
3.5.0 (Patch 5, 6)
3.5.1476
Threat Intelligence Exchange module (TIEm)
for VirusScan Enterprise
1.0.3.134
1.0.3.134
1.0.3.134
1.0.3.134
Host Intrusion Prevention (HIP)
Patch 12–15
8.0.0 (Patch 11–15)
8.0.0 (Patch 10–14)
8.0.0 (Patch 12)
Drive Encryption (DE)
7.2.10
7.2.9
7.2.9
7.2.5
7.2.1.16
File and Removable Media Protection (FRP)
5.3.0
5.2.0
5.2.0
5.0.6
-
VirusScan Enterprise for Storage (VSES)
1.3
1.3
1.3
1.3
McAfee Installation Designer
The version structure for McAfee Installation Designer (MID) is parallel to that of VSE. Only the corresponding versions can be used together. For example: VSE 8.8 requires MID 8.8.
A new version of MID is released within two weeks, after the corresponding VSE release date.
IMPORTANT:
The latest available MID version created for Patch 10 is compatible and supported for use with VSE 8.8 Patch 11, 12 and 13.
MID is compatible with the VSE 8.8 Patch 8 repost on September 19, 2016.
Installation of MID is supported on the same operating systems as VSE, but only on 32-bit systems.
You can deploy created packages to any platforms that VSE (32-bit and 64-bit systems) supports.
McAfee Profiler
McAfee Profiler gathers statistics from the systems that show how On-Access Scan affects the CPU. Profiler captures top processes and files that the on-access scanner accesses. Based on the data collected, an administrator can decide whether to exclude a process or a file for scanning. These exclusions can then reduce the impact on the system.
Email clients
The On-Delivery Email Scanner is installed by default.
Microsoft Outlook
VSE supports Messaging Application Programming Interface (MAPI) only in Microsoft Exchange-connected environments, running Microsoft Outlook as the mail client. VSE doesn’t support Internet Message Access Protocol (IMAP) or Post Office Protocol 3 (POP3) mail. Email Scanning can become redundant depending on your email environment. The on-access scanner in VSE, scans attachments when running or writing to local disk. This scan happens after Outlook Scan finishes scanning. If email is scanned at the Gateway, you can stop using Outlook Scan, because of scan redundancy.
Product Version
VSE 8.8
Outlook 2016
Yes 2
Outlook 2013
Yes 1
Outlook 2010
Yes
Outlook 2007
Yes
Outlook 2003
Yes
1
Full support for Outlook 2013 is provided in VSE 8.8 Patch 4 and later, which is available from the Product Downloads site, using a valid Grant Number.
NOTES:
The Outlook 2013 Email Scan feature was supported initially only with VSE 8.8 Patch 3 on Windows 8.
Email Scan is redundant for environments using an Exchange Mail Server with AV protection. Support is only provided for Outlook 2013, with the Email Scan feature, with VSE 8.8 Patch 4 and later.
2
Full support for the Microsoft Office 2016 suite is provided in VSE 8.8 Patch 8 and later, which is available from the Product Downloads site, using a valid Grant Number.
Lotus Notes
Product Version
VSE 8.8
Lotus Notes 8.5.1
Yes
Lotus Notes 8.5
Yes
NOTE: VSE doesn’t support versions of Lotus Notes on platforms that IBM doesn’t support.
For example:
Lotus Notes 8.5.1 Fix Pack1 (and above) is supported on Windows 7 64-bit.
Internet browser support for VSE ScriptScan IMPORTANT: This table relates only to whether the ScriptScan feature works or is supported with the browser. It isn’trelated to whether VSE is supported with the browser. The versions listed below and tagged as 'Yes', have passed QA testing.
Browser
VSE 8.8
Patches
4–16
VSE 8.8
Patch 3
VSE 8.8
Patch 2
VSE 8.8
Patch 1
VSE 8.8
Microsoft Internet Explorer 11 2
Yes
No
No
No
No
Microsoft Internet Explorer 10 2
Yes
No
No
No
No
Mozilla Firefox 7 and later 1
No
No
No
No
No
1
Mozilla Firefox blocks the McAfee ScriptScan add-in, which isn’tsomething the Product Development team can resolve. Support for the Firefox browser and ScriptScan is no longer supported.
2
Support provided in VSE 8.8 Patch 4 and later.
NOTE: For Windows 8 and later, ScriptScan is supported only when Internet Explorer is used in Desktop mode. Metro mode isn’t supported.
Supported Engine Versions
Because of the security risks involved in running an out-of-date Scan Engine, McAfee Enterprise actively enforces an End of Life (EOL) policy for older Scan Engines. We also stop all internal testing of DAT files on EOL Scan Engines. Any issues encountered with an EOL Scan Engine, are out of scope or support.
The 5800 and 5900 (EOL) Scan Engines both support Windows 10 when Patch 6 or later is also installed.
2
The 6000 (EOL) Scan Engine is compatible with all currently supported versions of VSE 8.8. But, testing was limited to Patch 11 and Patch 12.
3
The 6010 (EOL) Scan Engine is compatible with all currently supported versions of VSE 8.8. It has been tested with Patch 13. The 6010 Scan Engine is only included in the full installation package.
4
The 6200 Scan Engine is compatible with all currently supported versions of VSE 8.8. It has been tested with Patch 15 and Patch 16.
VMware
The Product Development team tries to resolve product issues that are seen to occur only in VMware environments. But, VMware can only resolve any issue found to be the result of VMware. If an issue is discovered with VSE and requires a code change to resolve, are only available in the latest release.
Release
VSE 8.8
VMware ESXi 6.x
Yes
VMware ESXi 5.1, 5.0 2
Yes
VMware ESXi 5.5
Yes
VMware ESX/ESXi 4.x 1
Yes
VMware Workstation 5.0
Yes
1
VMware ESX and ESXi 4.x will no longer be supported as of May 21, 2016. For more information, see the VMware Lifecycle Matrix.
2
VMware ESX and ESXi 5.1 and 5.0 will no longer be supported as of August 24, 2016. For more information, see the VMware Lifecycle Matrix.
NOTE: We can provide support only as long as VMware supports these versions.
Third-party applications
Application
VSE 8.8
Comments
EMC Celerra Network Server
EMC Celerra Antivirus Agent (CAVA)
Note 1
CAVA is an agent running on a Windows Server that communicates with a third-party antivirus engine to scan files stored on a Celerra Network Server.
1
To identify what versions of VSE the CAVA agent supports, contact EMC. Make sure that you enable the When reading from disk option. Also, select the On network drives checkbox.
IP version
VSE 8.8
Comments
IPv6
Yes
In the limited areas where it plays a role, VSE is ready for IPv6.
The Development team recommends a Pentium IV class processor or higher.
RAM
The following specifications are subject to change.
Physical RAM
VSE 8.8
Recommended
1 GB
Needed
512 MB 1
1
A minimum of 512 MB of RAM + 512 MB of Virtual Memory. The Development team recommends 1 GB of RAM minimum, plus the use of Virtual Memory for improved performance.
Disk space
These table entries are the updated requirements as applicable, with current patch levels and hotfixes.
Disk Space
VSE 8.8
Needed for installation
1 GB
Needed for DAT updates
1 GB
USB support
VSE 8.8
Yes 1
1
By default, the on-access scanner in VSE scans USB devices, only when the files on the devices are accessed.
Supported languages
Language
VSE 8.8
Chinese Simplified
Yes
Chinese Traditional
Yes
Danish
Yes
Dutch
Yes
English USA, UK
Yes
French
Yes
Italian
Yes
German
Yes
Japanese
Yes
Korean
Yes
Mexico
Yes
Polish
Yes
Portuguese/Brazilian
Yes
Russian
Yes
Spanish
Yes
Swedish
Yes
VSE supports Microsoft Resilient File System (Re-FS). But, VSE doesn’t support the case sensitivity feature of Re-FS. If this feature is enabled, it causes issues with VSE.
Compatibility with VSE and Windows 10 upgrades:
The table below provides the needed minimum supported VSE version to be installed, before upgrading the Windows 10 operating system.
Microsoft Windows Versions
Minimum Supported
VSE Version
Windows 10 Enterprise for Virtual Desktops1
VSE 8.8 Patch 16
Windows 10 version 21H1
VSE 8.8 Patch 16
Windows 10 version 20H2 (October 2020 Update)
VSE 8.8 Patch 16
Windows 10 Version 2004 (May 2020)
VSE 8.8 Patch 15
Windows 10 Version 1903 (May 2019)
VSE 8.8 Patch 13
Windows 10 version 1809 (October 2018)
VSE 8.8 Patch 12
Windows 10 Version 1803 (April 2018 Update)
VSE 8.8 Patch 11
Windows 10 Version 1709 (Fall Creators Update)
VSE 8.8 Patch 10
Windows 10 Version 1703 (Creators Update)
VSE 8.8 Patch 9
Windows 10 Version 1607 (Anniversary Update)
VSE 8.8 Patch 8
1
Windows 10 Enterprise for Virtual Desktops is a version of Windows 10 Enterprise that incorporates some Windows Server technology. This technology allows multiple remote desktop sessions simultaneously. Windows Virtual Desktop runs on the Microsoft Azure Cloud environment. Windows Virtual Desktop provides a multi-session Windows 10 deployment that delivers a full Windows 10 with scalability for many users on the same system.
Operating System
TIEm
1.0.3
TIEm
1.0.1.137
To 1.0.2
TIEm 1.0.1.000
Windows Server 2019
Yes
No
No
Windows Server 2016
Windows Server 2016 - Server Core mode (version 1607)
Yes
No
No
Windows Server 2012 R2
Yes
Yes
Yes
Windows Server 2012
Yes
Yes
Yes
Windows Server 2008 R2
Yes
Yes
Yes
Windows Server 2008 R1
No
Yes
No
Windows 10 Version 20H2 (Oct 2020)
Windows 10 Version 2004 (May 2020)
Windows 10 Version 1909 (Nov 2019)
Windows 10 Version 1903 (May 2019)
Windows 10 version 1809 (October 2018)
Windows 10 Version 1803 (April 2018 Update)
Windows 10 Version 1709 (Fall Creators Update)
Windows 10 Version 1703 (Creators Update)
Windows 10 Version 1607 (Anniversary Update)
EOL period—The time frame that runs from the day McAfee Enterprise announces product discontinuation, until the last date that McAfee Enterprise formally supports the product. In general, after the EOL period is announced, no enhancements are made.
EOL date—The last day that the product is supported, according to the terms of the McAfee Enterprise standard support offering.
