Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Symantec Endpoint Protection configuration report

Created: 12 Feb 2013 • Updated: 12 Feb 2013 | 6 comments

Hi There,

 

One of our client is planning to migration SEP 11.0.6 to McAfee. they asked to provide a report with the current configuration of SEP. like exceptions, policies & settings.

Can you please let us know id there any way we can generate a report from SEP manager console?

 

Thanks in advance!

Comments 6 CommentsJump to latest comment

SebastianZ's picture

How to export/import an existing Symantec Endpoint Protection policy

http://www.symantec.com/docs/TECH106486

...using this you can export the policies and exception policy as well. There is unfortunately no way to export the settings - btw. what would be the purpose of SEPM settings export here? McAfee will definitely has its own configuration settings, ports, etc.

raviteja.prt's picture

Hi SebastianZ..

Thanks for looking into this.

I have tried the above option.. but it is exporting to .dat file, we want to configure the same policies in McAfee to avoid service disruptions..

I am looking for a way where i can export the policies and exceptions to flat text or CSV file.

 

Regards

SebastianZ's picture

You should be still able to read it this way:

1. Export the policy to  the.dat file

2. Rename  the .dat file to .zip

3. Extract the archive - it contains a file named main.xml - where you will have the policy in .xml format

 

That is the only way I know for exporting - SEPm does not provide any export to .CSV or .TXT directly.

raviteja.prt's picture

ok SebastianZ.. let me check if i can use for reporting. Thanks again

SebastianZ's picture

You should be able as well to have a glance at the applied exceptions directly from the SEP client in registry - HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\AV\Exclusions - the keys under this will containg the configured exceptions for the client machine - some reference here:

https://www-secure.symantec.com/connect/articles/s...