Overview: While you may not realize it, any .dat policy exported from the Symantec Endpoint Protection Manager is simply a compressed XML file. By changing the extension from .dat to .zip, you gain access to the actual input values for the policies. By having direct access to these values, you are provided with a more granular way to control how your policy works.* One such example is creating administrator-defined scans based on drive letter (C:\, D:\, etc). Exploring the policies in their XML formats can provide a better understanding of the way that policies are constructed on the backend. In this document, I'll walk through the process of creating a custom scanning policy that relies on the drive letter to assign a new scan. This is just one of the many possibilities that editing the XML policies creates.** Requirements: Symantec Endpoint Protection 12.1.x*** Symantec Endpoint Protection Manager 12.1.x*** Difficulty Level: Intermediate-Advanced
Instructions:
Thank you for reading this article, please leave a comment below on your experience with this process.
*The information in this article is for education purposes only: editing policies in this way may create unexpected behavior in your environment or cause the product to malfunction. XML customized policies may not be compatible between versions of SEP. **Please be responsible and test your policies thoroughly before deploying them to your production network. ***Policies are not likely compatible between versions (e.g. policies created in 12.1.4 SEPM may not necessarily be deployable to 12.1.3 clients)
wonderful information, I used this information in my project work "dat file". thanks for sharing this article with us.