Our Internal Security Scanner found that our dedicated Windows IIS Servers for internal facing HTTP Distributed Repositories are exposed to IIS ShortName scanner vulnerability:
The fix seems to be as easy as to run
But setting 8dot3name to disable is the reverse of typical ePO Server installation best practice (for VSE AP Long filename/short file name resolution).
Question is... is this safe for EPO Managed Distributed Repository?
I think so but I want to make sure.
Go to Solution.
Yes, the repository should be OK.
I offer the following as information.This article as it has a rather good description (in the 'Cause' section) of 'issues' '8 dot 3' can cause if its not accounted for correctly.
Unable to log on to the ePO console after migrating ePO to a new serverTechnical Articles ID: KB84177
Was my reply helpful?If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
It is not required for a distributed repository, only for the epo server itself.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center
2821 Mission College Blvd.
Santa Clara, CA 95054 USA
Consumer Support | Enterprise Support | McAfee.com
Legal | Privacy | Copyright © 2019 McAfee, LLC