we didn't upgrade to epo 5,3 but do have the exact same issue when checking in the extensions for VSE patch 5
Anyone a solution yet ?
This is a huge issue for us because we can't add user defined rules now.
Many thanks in advance for interesting tips.
Ended up going into the extensions folder on the ePO server and copying the files from VSE P4 extension into the 220.127.116.112 folder. Access Protection rules are now visible again
We do have couple of customers reported this issue. Do you have ePO installation in non-root drive (other than C drive)? Do you have 8.3 naming convention setup correctly?
Please try the workaround below.
2. rebooted system
3. removed extension and then checked it back in. (before removing the extension. Please export, VSE poilcies/policy assignment, client task/client task assignments)
4. re-imported policies and extensions
Got the exact same issue here on ePO 5.1.1
After importing VSE 8.8 Patch 5 & its extention via the software manager.
This is a mayor issue for us as we depend on these application protection rules
As far as I know not. I'm asking this already for years. Export is possibel but import stops at the policies but the assignments are lost.
I had this discussion this morning agian with VP product engineering VSE and HIPS.
Based on the issue we had we received the following feedback
ePo is not supported on volumes where 8.3 (8.3 filename creation) is disabled. Windows 6.2+ disables 8.3 on non-C: volumes. If the product is to be installed on a non-C: volume in Windows 6.2+ then 8.3 must be manually enabled, first.
If ePO is installed on an improperly prepared volume then the VSE 8.8 Patch 5 extension will not display Access Protection content.
WARNING: Before applying these procedures the ePO server should ideally be fully backed up. This procedure removes product extensions. This results in a total loss of any configured policies and tasks. The customer MUST verify that their backup strategy allows for restoration, and they MUST verify that the policies and tasks exported below include ALL items that will be lost when the extensions are removed.
• BACKUP the ePO server.
• VERIFY the backup.
• Enable 8.3 on the volume where ePO is installed.
· fsutil.exe Commands to Query and Enable 8.3 Per Volume on Windows 6.2+
· where 'X:' is the volume where ePO is installed.
· fsutil.exe 8dot3name query X:
· fsutil.exe 8dot3name set X: 0 • Reboot.
• Export any policies and tasks for VSE dependencies such as VSES, VSEOVI, VSESAP, etc, if any.
• Export the VSE 8.8 policies and tasks.
• VERIFY that all required policies and tasks, and any other content that will be lost due to extension removal is present in the exports.
• Remove the dependencies' extensions, if any.
• Remove the VSE 8.8 Patch 5 extension.
• Install the VSE 8.8 Patch 5 extension.
• Install the dependencies' extensions, if any.
• Import the VSE 8.8 policies and tasks.
• Import any policies and tasks for VSE dependencies such as VSES, VSEOVI, VSESAP, etc, if any.
We created the shornames for the mcafee folder and the epolicy orchestrator folder and that solved the issue for us
> Yes happens also if you upgrade to VSE 8.8 PATCH 5 AND you are a smart guy who installs EPO Binaries on 😧 like they teach you.
> Enable 8.3 Naming Convention (Short) for the Disk you have EPO Path installed and reboot did the trick
> Export all Policies and Assigments
> Remove Extension foer VSE 8.8 Patch 6
> Download 8.8 patch 5 Repost and extract Extension files (two)
> Import Extension
> Import your expoted Policies
DO NOT FORGET to import and EXPORT POLICIES
<Drive:>\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\BOCVSE_1000\DAT\0000\or:<Drive:>\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\BOCVSE_1000\DAT\0000\