Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Wednesday, February 15, 2017

PostgreSQL - End Of Life (EOL) dates

End Of Life (EOL) dates

VersionCurrent minorSupportedFirst release dateEOL date
9.69.6.2YesSeptember 2016September 2021
9.59.5.6YesJanuary 2016January 2021
9.49.4.11YesDecember 2014December 2019
9.39.3.16YesSeptember 2013September 2018
9.29.2.20YesSeptember 2012September 2017
9.19.1.24NoSeptember 2011September 2016
9.09.0.23NoSeptember 2010September 2015
8.48.4.22NoJuly 2009July 2014
8.38.3.23NoFebruary 2008February 2013
8.28.2.23NoDecember 2006December 2011
8.18.1.23NoNovember 2005November 2010
8.08.0.26NoJanuary 2005October 2010
7.47.4.30NoNovember 2003October 2010
7.37.3.21NoNovember 2002November 2007
7.27.2.8NoFebruary 2002February 2007
7.17.1.3NoApril 2001April 2006
7.07.0.3NoMay 2000May 2005
6.56.5.3NoJune 1999June 2004
6.46.4.2NoOctober 1998October 2003
6.36.3.2NoMarch 1998March 2003



- wong chee tat :)

PostgreSQL 9.6.2 Release Notes

Release 9.6.2

Release Date: 2017-02-09
This release contains a variety of fixes from 9.6.1. For information about new features in the 9.6 major release, see Section E.3.

E.1.1. Migration to Version 9.6.2

A dump/restore is not required for those running 9.6.X.
However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.
Also, if you are upgrading from a version earlier than 9.6.1, see Section E.2.

E.1.2. Changes

  • Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt (Pavan Deolasee, Tom Lane)
    If CREATE INDEX CONCURRENTLY was used to build an index that depends on a column not previously indexed, then rows updated by transactions that ran concurrently with theCREATE INDEX command could have received incorrect index entries. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update.
  • Ensure that the special snapshot used for catalog scans is not invalidated by premature data pruning (Tom Lane)
    Backends failed to account for this snapshot when advertising their oldest xmin, potentially allowing concurrent vacuuming operations to remove data that was still needed. This led to transient failures along the lines of "cache lookup failed for relation 1255".
  • Fix incorrect WAL logging for BRIN indexes (Kuntal Ghosh)
    The WAL record emitted for a BRIN "revmap" page when moving an index tuple to a different page was incorrect. Replay would make the related portion of the index useless, forcing it to be recomputed.
  • Unconditionally WAL-log creation of the "init fork" for an unlogged table (Michael Paquier)
    Previously, this was skipped when wal_level = minimal, but actually it's necessary even in that case to ensure that the unlogged table is properly reset to empty after a crash.
  • If the stats collector dies during hot standby, restart it (Takayuki Tsunakawa)
  • Ensure that hot standby feedback works correctly when it's enabled at standby server start (Ants Aasma, Craig Ringer)
  • Check for interrupts while hot standby is waiting for a conflicting query (Simon Riggs)
  • Avoid constantly respawning the autovacuum launcher in a corner case (Amit Khandekar)
    This fix avoids problems when autovacuum is nominally off and there are some tables that require freezing, but all such tables are already being processed by autovacuum workers.
  • Disallow setting the num_sync field to zero in synchronous_standby_names (Fujii Masao)
    The correct way to disable synchronous standby is to set the whole value to an empty string.
  • Don't count background worker processes against a user's connection limit (David Rowley)
  • Fix check for when an extension member object can be dropped (Tom Lane)
    Extension upgrade scripts should be able to drop member objects, but this was disallowed for serial-column sequences, and possibly other cases.
  • Fix tracking of initial privileges for extension member objects so that it works correctly with ALTER EXTENSION ... ADD/DROP (Stephen Frost)
    An object's current privileges at the time it is added to the extension will now be considered its default privileges; only later changes in its privileges will be dumped by subsequentpg_dump runs.
  • Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes (Tom Lane, Michael Paquier)
    Previously, non-default settings of default_tablespace could result in broken indexes.
  • Fix incorrect updating of trigger function properties when changing a foreign-key constraint's deferrability properties with ALTER TABLE ... ALTER CONSTRAINT (Tom Lane)
    This led to odd failures during subsequent exercise of the foreign key, as the triggers were fired at the wrong times.
  • Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation (Tom Lane)
    This avoids "could not find trigger NNN" or "relation NNN has no triggers" errors.
  • Fix ALTER TABLE ... SET DATA TYPE ... USING when child table has different column ordering than the parent (Álvaro Herrera)
    Failure to adjust the column numbering in the USING expression led to errors, typically "attribute N has wrong type".
  • Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via ALTER TABLE ... INHERIT (Amit Langote)
    The OID column should be treated the same as regular user columns in this case, but it wasn't, leading to odd behavior in later inheritance changes.
  • Ensure that CREATE TABLE ... LIKE ... WITH OIDS creates a table with OIDs, whether or not the LIKE-referenced table(s) have OIDs (Tom Lane)
  • Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options (Dean Rasheed)
    Previously the command would fail if the new options were inconsistent with the old view definition.
  • Report correct object identity during ALTER TEXT SEARCH CONFIGURATION (Artur Zakirov)
    The wrong catalog OID was reported to extensions such as logical decoding.
  • Fix commit timestamp mechanism to not fail when queried about the special XIDs FrozenTransactionId and BootstrapTransactionId (Craig Ringer)
  • Fix incorrect use of view reloptions as regular table reloptions (Tom Lane)
    The symptom was spurious "ON CONFLICT is not supported on table ... used as a catalog table" errors when the target of INSERT ... ON CONFLICT is a view with cascade option.
  • Fix incorrect "target lists can have at most N entries" complaint when using ON CONFLICT with wide tables (Tom Lane)
  • Fix spurious "query provides a value for a dropped column" errors during INSERT or UPDATE on a table with a dropped column (Tom Lane)
  • Prevent multicolumn expansion of foo.* in an UPDATE source expression (Tom Lane)
    This led to "UPDATE target count mismatch --- internal error". Now the syntax is understood as a whole-row variable, as it would be in other contexts.
  • Ensure that column typmods are determined accurately for multi-row VALUES constructs (Tom Lane)
    This fixes problems occurring when the first value in a column has a determinable typmod (e.g., length for a varchar value) but later values don't share the same limit.
  • Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string (Tom Lane)
    Normally, a Unicode surrogate leading character must be followed by a Unicode surrogate trailing character, but the check for this was missed if the leading character was the last character in a Unicode string literal (U&'...') or Unicode identifier (U&"...").
  • Fix execution of DISTINCT and ordered aggregates when multiple such aggregates are able to share the same transition state (Heikki Linnakangas)
  • Fix implementation of phrase search operators in tsquery (Tom Lane)
    Remove incorrect, and inconsistently-applied, rewrite rules that tried to transform away AND/OR/NOT operators appearing below a PHRASE operator; instead upgrade the execution engine to handle such cases correctly. This fixes assorted strange behavior and possible crashes for text search queries containing such combinations. Also fix nested PHRASE operators to work sanely in combinations other than simple left-deep trees, correct the behavior when removing stopwords from a phrase search clause, and make sure that index searches behave consistently with simple sequential-scan application of such queries.
  • Ensure that a purely negative text search query, such as !foo, matches empty tsvectors (Tom Dunstan)
    Such matches were found by GIN index searches, but not by sequential scans or GiST index searches.
  • Prevent crash when ts_rewrite() replaces a non-top-level subtree with an empty query (Artur Zakirov)
  • Fix performance problems in ts_rewrite() (Tom Lane)
  • Fix ts_rewrite()'s handling of nested NOT operators (Tom Lane)
  • Improve speed of user-defined aggregates that use array_append() as transition function (Tom Lane)
  • Fix array_fill() to handle empty arrays properly (Tom Lane)
  • Fix possible crash in array_position() or array_positions() when processing arrays of records (Junseok Yang)
  • Fix one-byte buffer overrun in quote_literal_cstr() (Heikki Linnakangas)
    The overrun occurred only if the input consisted entirely of single quotes and/or backslashes.
  • Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently (Michael Paquier)
    This avoids an assertion failure, and possibly worse things, if someone tries to run these functions in parallel.
  • Disable transform that attempted to remove no-op AT TIME ZONE conversions (Tom Lane)
    This resulted in wrong answers when the simplified expression was used in an index condition.
  • Avoid discarding interval-to-interval casts that aren't really no-ops (Tom Lane)
    In some cases, a cast that should result in zeroing out low-order interval fields was mistakenly deemed to be a no-op and discarded. An example is that casting from INTERVAL MONTH to INTERVAL YEAR failed to clear the months field.
  • Fix crash if the number of workers available to a parallel query decreases during a rescan (Andreas Seltenreich)
  • Fix bugs in transmitting GUC parameter values to parallel workers (Michael Paquier, Tom Lane)
  • Allow statements prepared with PREPARE to be given parallel plans (Amit Kapila, Tobias Bussmann)
  • Fix incorrect generation of parallel plans for semi-joins (Tom Lane)
  • Fix planner's cardinality estimates for parallel joins (Robert Haas)
    Ensure that these estimates reflect the number of rows predicted to be seen by each worker, rather than the total.
  • Fix planner to avoid trying to parallelize plan nodes containing initplans or subplans (Tom Lane, Amit Kapila)
  • Ensure that cached plans are invalidated by changes in foreign-table options (Amit Langote, Etsuro Fujita, Ashutosh Bapat)
  • Fix the plan generated for sorted partial aggregation with a constant GROUP BY clause (Tom Lane)
  • Fix "could not find plan for CTE" planner error when dealing with a UNION ALL containing CTE references (Tom Lane)
  • Fix mishandling of initplans when forcibly adding a Material node to a subplan (Tom Lane)
    The typical consequence of this mistake was a "plan should not reference subplan's variable" error.
  • Fix foreign-key-based join selectivity estimation for semi-joins and anti-joins, as well as inheritance cases (Tom Lane)
    The new code for taking the existence of a foreign key relationship into account did the wrong thing in these cases, making the estimates worse not better than the pre-9.6 code.
  • Fix pg_dump to emit the data of a sequence that is marked as an extension configuration table (Michael Paquier)
  • Fix mishandling of ALTER DEFAULT PRIVILEGES ... REVOKE in pg_dump (Stephen Frost)
    pg_dump missed issuing the required REVOKE commands in cases where ALTER DEFAULT PRIVILEGES had been used to reduce privileges to less than they would normally be.
  • Fix pg_dump to dump user-defined casts and transforms that use built-in functions (Stephen Frost)
  • Fix pg_restore with --create --if-exists to behave more sanely if an archive contains unrecognized DROP commands (Tom Lane)
    This doesn't fix any live bug, but it may improve the behavior in future if pg_restore is used with an archive generated by a later pg_dump version.
  • Fix pg_basebackup's rate limiting in the presence of slow I/O (Antonin Houska)
    If disk I/O was transiently much slower than the specified rate limit, the calculation overflowed, effectively disabling the rate limit for the rest of the run.
  • Fix pg_basebackup's handling of symlinked pg_stat_tmp and pg_replslot subdirectories (Magnus Hagander, Michael Paquier)
  • Fix possible pg_basebackup failure on standby server when including WAL files (Amit Kapila, Robert Haas)
  • Improve initdb to insert the correct platform-specific default values for the xxx_flush_after parameters into postgresql.conf (Fabien Coelho, Tom Lane)
    This is a cleaner way of documenting the default values than was used previously.
  • Fix possible mishandling of expanded arrays in domain check constraints and CASE execution (Tom Lane)
    It was possible for a PL/pgSQL function invoked in these contexts to modify or even delete an array value that needs to be preserved for additional operations.
  • Fix nested uses of PL/pgSQL functions in contexts such as domain check constraints evaluated during assignment to a PL/pgSQL variable (Tom Lane)
  • Ensure that the Python exception objects we create for PL/Python are properly reference-counted (Rafa de la Torre, Tom Lane)
    This avoids failures if the objects are used after a Python garbage collection cycle has occurred.
  • Fix PL/Tcl to support triggers on tables that have .tupno as a column name (Tom Lane)
    This matches the (previously undocumented) behavior of PL/Tcl's spi_exec and spi_execp commands, namely that a magic .tupno column is inserted only if there isn't a real column named that.
  • Allow DOS-style line endings in ~/.pgpass files, even on Unix (Vik Fearing)
    This change simplifies use of the same password file across Unix and Windows machines.
  • Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot (Takayuki Tsunakawa)
  • Fix incorrect error reporting for duplicate data in psql's \crosstabview (Tom Lane)
    psql sometimes quoted the wrong row and/or column values when complaining about multiple entries for the same crosstab cell.
  • Fix psql's tab completion for ALTER DEFAULT PRIVILEGES (Gilles Darold, Stephen Frost)
  • Fix psql's tab completion for ALTER TABLE t ALTER c DROP ... (Kyotaro Horiguchi)
  • In psql, treat an empty or all-blank setting of the PAGER environment variable as meaning "no pager" (Tom Lane)
    Previously, such a setting caused output intended for the pager to vanish entirely.
  • Improve contrib/dblink's reporting of low-level libpq errors, such as out-of-memory (Joe Conway)
  • Teach contrib/dblink to ignore irrelevant server options when it uses a contrib/postgres_fdw foreign server as the source of connection options (Corey Huinker)
    Previously, if the foreign server object had options that were not also libpq connection options, an error occurred.
  • Fix portability problems in contrib/pageinspect's functions for GIN indexes (Peter Eisentraut, Tom Lane)
  • Fix possible miss of socket read events while waiting on Windows (Amit Kapila)
    This error was harmless for most uses, but it is known to cause hangs when trying to use the pldebugger extension.
  • On Windows, ensure that environment variable changes are propagated to DLLs built with debug options (Christian Ullrich)
  • Sync our copy of the timezone library with IANA release tzcode2016j (Tom Lane)
    This fixes various issues, most notably that timezone data installation failed if the target directory didn't support hard links.
  • Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

\

- wong chee tat :)

Tuesday, February 14, 2017

PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!

PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!

Posted on 2017-02-09
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and 9.2.20. This release includes fixes that prevent data corruption issues in index builds and in certain write-ahead-log replay situations, which are detailed below. It also patches over 75 other bugs reported over the last three months.
Users should plan to apply this update at the next scheduled downtime.

Build corruption with CREATE INDEX CONCURRENTLY

There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been indexed incorrectly.
If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update.
This issue is present in the 9.2, 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL.

Fixes for visibility and write-ahead-log stability

These release contains several fixes to improve the stability of visible data and WAL logging that we wish to highlight here.
Prior to this release, data could be prematurely pruned by a vacuum operation when a special snapshot used for catalog scans was presently available. Specifically, the vacuum operation would not be aware of the oldest xmin for this special snapshot. The error would surface with a message such as:
"cache lookup failed for relation 1255"
This release ensures that vacuum operations will account for the catalog scan snapshots.
Additionally, there are several fixes to improved the stability of write-ahead-logging, including:
* A fix for BRIN index WAL logging where a replay could make a portion of the BRIN index useless and require recomputing
* A fix for an unlogged table where a WAL-log would be created under the "wal_level = minimal" setting, and upon replay after crash, the table would not appear to be properly reset
* A fix in the WAL page header validation when re-reading segments that fixes the error of  "out-of-sequence TLI" that could be reported during recovery
Theses issues are present in the 9.6 series of PostgreSQL releases and may also be present in the 9.2, 9.3, 9.4, and 9.5 series.

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few months. Some of these issues affect only the 9.6 series, but many affect all supported versions. There are more than 75 fixes provided in this release, including:
  • Several fixes for operating in hot standby mode
  • Disallow setting the num_sync field to zero in synchronous_standby_names
  • Don't count background worker processes against a user's connection limit
  • Fix check for when an extension member object can be dropped
  • Fix tracking of initial privileges for extension member objects so that it works correctly with ALTER EXTENSION ... ADD/DROP
  • Several vacuum and autovacuum fixes
  • Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options
  • Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
  • Several fixes to the query planner, including fixes for foreign tables and CTEs
  • Several fixes around the full-text search feature to improve accuracy and performance of the search
  • Several fixes and performance improvements in several array functions
  • Several fixes around the interaction of foreign-key constraints with trigger functions around specific ALTER TABLE operations
  • Remove optimizations for date/time data types that returned incorrect data
  • Fix incorrect use of view reloptions as regular table reloptions
  • Fix incorrect "target lists can have at most N entries" complaint when using ON CONFLICT with wide tables
  • Fix spurious "query provides a value for a dropped column" errors during INSERT or UPDATE on a table with a dropped column
  • Prevent multicolumn expansion of foo.* in an UPDATE source expression
  • Ensure that column typmods are determined accurately for multi-row VALUES constructs
  • Several fixes for the psql command-line tool
  • Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
  • Several fixes for pg_dump, pg_restore, and pg_basebackup, including a possible pg_basebackup failure on standby server when including WAL files
  • Several fixes for parallel workers and plans for parallel queries including fixing a crash if the number of workers available to a parallel query decreases during a rescan
  • Several fixes to PL/pgSQL, PL/Python, and PL/Tcl
  • Several fixes for contrib modules
  • Allow DOS-style line endings in ~/.pgpass files, even on Unix
Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

Updating

All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries.
If you believe you have been affected by the aforementioned CREATE INDEX CONCURRENTLY bug, you will have to rebuild the index. Here is an example of how to rebuild an index in a production system without losing the ability to utilize the index:
CREATE INDEX CONCURRENTLY new_index_name ON table_name (column_name);
DROP INDEX CONCURRENTLY old_index_name;
ALTER INDEX new_index_name RENAME TO old_index_name;
Note that using this method means you will briefly have two copies of the same index, so if disk space is an issue you may need to take other approaches.
Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.




Need some time to test and play with it!


- wong chee tat :)

Wednesday, November 9, 2016

Supported platforms, environments, and operating systems for ePolicy Orchestrator - KB51569

Supported platforms, environments, and operating systems for ePolicy Orchestrator - KB51569

Environment

McAfee ePolicy Orchestrator (ePO) 5.x, 4.x

Summary

As Microsoft releases new operating systems or Service Packs, the original Product Guides might not reflect the current Intel Security support policy for those platforms. Most of the following information is available in the Product Installation Guides and Readme.txt files. However, some of the information is available only in Product Management statements published in the Knowledge Base.

NOTES:
  • ePO 5.0 reached end of life (EOL) on December 31, 2014, and is no longer supported.
  • ePO 4.6 reached end of life (EOL) on December 31, 2015, and is no longer supported.
Microsoft Windows supported operating systems
The following tables detail the Intel Security products supported for use on Windows workstation and server operating systems. Only the most current versions are included because most customers upgrade to the latest Service Packs soon after they are released.

Server operating systems 
Microsoft operating systemePO 4.6
(EOL)
ePO 5.0
(EOL)
ePO 5.1ePO 5.3
Microsoft Windows Server 2012 R2
(Standard and Datacenter)
NoNoYes1Yes
Microsoft Windows Server 2012
(Standard and Datacenter)
No2 YesYesYes
Microsoft Windows Server 2008 Release 2 (64-bit)
(Standard, Enterprise, and Datacenter)
Yes YesYesYes
Microsoft Windows Server 2008 (64-bit)
(Standard, Enterprise, and Datacenter)
YesYes3Yes3Yes
Microsoft Windows Server 2008 (32-bit)
(Standard, Enterprise, and Datacenter)
YesNoNoNo
Microsoft Windows 2003 Storage ServerNoNoNoNo
Microsoft Windows Server 2003 Release 2 (32-bit)
Yes
NoNoNo
Microsoft Windows Server 2003 Release 2 (64-bit)
Yes
No NoNo
Microsoft Windows Server 2003 (32-bit)YesNoNoNo
Microsoft Windows Server 2003 (64-bit)YesNoNoNo
Microsoft Windows 2003 WebNoNoNoNo
1 See KB79062 for details on an error displayed when installing ePO 5.1 on a system running Windows Server 2012 R2. This error can be safely ignored. Also, see KB80065 for details on an issue when attempting to install a remote Agent Handler on Windows Server 2012 R2.
2 See KB75779 for more information.
3 Requires Windows Server 2008 Service Pack 2 or later.

 NOTES:
  • Cluster supportePO provides high availability for server clusters with Microsoft Cluster Server (MSCS) software. Also, Intel Security supports ePO installations where the ePO database itself is stored on a clustered instance of SQL. Clustering the SQL Database Server is done at the SQL Server level (not specific to the ePO database). For details on how to configure an SQL Database Cluster, refer to the documentation on SQL Server Books Online.
     
  • 64-bit hardware support 
    ePO only supports processors that use x86 or x64 compatible architecture. Itanium processors use the IA64 architecture and are not supported.
     
  • Remote Agent Handlers
    The requirements for ePO 4.x remote Agent Handlers are the same as the ePO server. For ePO 5.x, remote Agent Handlers can be installed on either the 32-bit or 64-bit versions of the supported OS versions.
     
  • Microsoft Windows Small Business Server (SBS) support
    ePO software versions 4.6 (and later) are supported only on Microsoft Windows Small Business Server suites that contain ePO-supported platforms (SQL version, OS, and so on).
    Example (for SBS support):
    Windows SBS 2011 is a suite that contains Windows Server 2008 R2 Standard, Exchange, SQL, and so on. For more information, see the Microsoft tech note at http://technet.microsoft.com/library/gg508696.aspx.

    Because ePO supports the Windows 2008 R2 operating system, ePO 4.6 (and later) is supported on platforms running Windows SBS 2011.
Virtual infrastructure software versions
Virtual softwareePO 4.6
(EOL)
ePO 5.0
(EOL)
ePO 5.1ePO 5.3
VMware ESX/ESXi 5.x and laterYes*YesYesYes
VMware Workstation 5.0NoNoNoNo
Microsoft Virtual Server 2005 R2 with SP1
No
NoNoNo
Windows Server 2012 R2 Hyper-V
No
No
YesYes
Windows Server 2012 Hyper-VNoYesYesYes
Windows Server 2008 R2 Hyper-VYesYesYesYes
Windows Server 2008 Hyper-V
No
YesNoNo
Citrix XenServer 6.0NoYesYesYes
Citrix XenServer 5.5YesNoNoNo

* ESX 5.x is supported with ePO 4.6.6 and later.
Internet browser versions
BrowserePO 4.6
(EOL)
ePO 5.0
(EOL)
ePO 5.1ePO 5.3
Safari 6.0 and later (on Mac OS X)NoYesYesYes
Chrome 17 and laterNoYesYesYes
EdgeNo**No**No**No**
Internet Explorer 9.0 and later
No*
YesYesYes
Internet Explorer 8.0*YesYesYesYes
Internet Explorer 7.0YesNoNoNo
Mozilla Firefox 10.0 and later
Yes*
YesYesYes

* See KB71550 for additional details.
** See KB85265 for additional details.
Microsoft SQL versions
Microsoft SQLePO 4.6
(EOL)
ePO 5.0
(EOL)
ePO 5.1ePO 5.3
SQL Server 2014 ExpressNoNoNoYes
SQL Server 2014NoNoNoYes
SQL Server 2012 ExpressYes1 YesYesYes
SQL Server 2012Yes1 YesYesYes
SQL Server 2008 R2 ExpressYes YesYes2Yes
SQL Server 2008 R2Yes YesYesYes
SQL Server 2008 ExpressYes Yes3 Yes3Yes3
SQL Server 2008Yes Yes3 Yes3Yes3
SQL Server 2005 ExpressYes4 NoNoNo
SQL Server 2005Yes4 NoNoNo

1 ePO 4.6 requires ePO 4.6.6 (or later) to support SQL Server 2012.
2 The ePO 5.1.x and ePO 5.3.x installer includes SQL Server 2008 R2 Express Service Pack 1. However, Microsoft does not support SQL Server 2008 R2 Express Service Pack 1 on Windows Server 2012 R2. In this scenario, Intel Security recommends upgrading to SQL Server 2008 R2 Express Service Pack 2 (or later).
3 ePO 5.x requires Service Pack 1 (or later) for SQL Server 2008.
4 ePO 4.6 requires Service Pack 3 (or later) for SQL Server 2005.
Current ePO Patches
Patch information is as follows:
  • To determine which ePO patch is installed, see KB52634.
  • For ePO server version information (build numbers), see KB59938.
McAfee product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site at:http://www.mcafee.com/us/downloads/downloads.aspx. 

NOTE:
 You will need a valid Grant Number for access. KB56057 provides additional information about the Product Downloads site, as well as alternate locations for some products.

Previous Document ID

614048



- wong chee tat :)