Recent updates to this article:
| Date |
Update |
| July 22, 2021 |
Updated reference VSES-1830 in the non-critical table. Now resolved with VSES 1.3.0 Extension Repost Build 1.3.0.149. |
| May 13, 2021 |
Added known issue references VSES-1830 (KB94513) to the non-critical table. |
| April 23, 2020 |
Added VSES 1.3.0 Hotfix 1257876 Release To Support (RTS) details. |
| July 3, 2019 |
Added VSES 1.3.0 Hotfix 1270862 (Released to Support). Added references 1270862 and 1272538 to the Non-Critical table. |
| July 14, 2018 |
Corrected version number for 1230424 in the Non-critical table. |
{GENSUB.EN_US}
Product Release Information:
Product
Version |
Released Date |
Release
Notes
|
| VSES 1.3.0 Extension Repost Build 1.3.0.149 (GA) 2 |
July 21, 2021 |
Not Available |
| VSES 1.3.0 Hotfix 1257876 (RTS)1 |
April 21, 2020 |
RTS |
VSES 1.3.0 Hotfix 1270862 (RTS)1
(HF1270862) |
June 7, 2019 |
RTS |
| VSES 1.3.0 Extension Repost Build 1.3.0.115(GA) |
March 23, 2018 |
Release Notes |
| VSES 1.3.0 Build 1.3.0.109 |
January 8, 2018 |
Release Notes |
{GENRLS.EN_US}
{GENPA.EN_US}
CRITICAL: There are no critical issues.
Non-critical:
Reference
Number |
Related
Article |
Found
VSES
Version |
Resolved
VSES
Version |
Issue Description |
| VSES-1830 |
KB94513 |
1.3.0.147 |
1.3.0.149
Extension
(Repost) |
Issue: Performance statistic events fail to parse, and thus ePO default dashboards, for example, VSES NetApp: Filer Performance (1.3.0), remain unpopulated. The issue is seen when you have VSES extension version 1.3.0.147 installed.
Resolution. To clear the accumulated events, after checking in VSES 1.3.0.149 Extension Repost, see the Related Article. |
| 1272538 |
- |
1.3.0 |
1.3.0.176
(RTS) |
Issue: McShield throws a “file not found” / “0xB” error during the scan on NetApp filers. |
| 1270862 |
- |
1.3.0 |
1.3.0.176
(RTS) |
Issue: Threat Source Hostname field in Threat Event Log doesn’t display correct information for Threat Source system. |
| 1230424 |
- |
|
1.3.0.115
(Repost) |
Issue: VSES ePO Queries and Reports displays duplicate instances of the VSES120 Performance query. One of the instances must be displaying an instance for VSES130 Performance. |
| 1231671 |
- |
1.3.0 |
1.3.0.115
(Repost) |
Issue: Unable to migrate VSES 1.2 policies to VSES 1.3.0.
Resolution: VSES 1.3.0.115 includes the latest version of ePOPolicyMigration.exe. |
1226144
1227663 |
KB90226 |
1.3.0.109 |
1.3.0.115
(Repost) |
Issue: The following is observed after checking in the VSES Extension 1.3.0.109:
- Performance event data isn’t parsed to the ePolicy Orchestrator (ePO) Server.
- Performance data related to the VSES ePO dashboards remain empty/blank.
For unpopulated monitors, the error "No Data Found" is displayed. |
| 1215216 |
- |
1.3.0 |
- |
Issue: Client Upgrade: When the client is upgraded from 1.2 to 1.3, the installer drops readme files into installation folder. |
| 1217282 |
- |
1.3.0 |
- |
Issue: Windows Server Core releases are supported only when managed by ePolicy Orchestrator.
NOTES:
- Server Core for Windows is a minimal server installation, where there’s no Windows shell, and limited graphical user interface (GUI) functionality. This reason is why the standalone installation of VSES doesn’t support it.
- ePO is a requirement, because the VSE console can't function properly without the needed fonts, for example marlett.ttf.
|
| 1219470 |
- |
1.3.0 |
- |
Issue: The ePO help extension isn’t updated for this release. VSES 1.3.0 uses the VSES 1.2.0 help extension. |
