
It's not hard to convert with basic TSQL, but you have to know the data is there in the first place (thanks again Tony). The table BASIC_METADATA stores binary data. Step 2: Query the table and convert it to something I can actually read I really can't take credt for this - our Symantec support rep (thank you Tony) was able to point me to the right table, BASIC_METADATA. PowerShell has been my tool of choice for managing our systems, so I wanted to build something that fit into our mangement module. So the first part to fixing the problem was reporting on it, and in spite of years and years of forum posts by quite a few users, I really hadn't seen a good solution. Managing SEP had been passed from admin to admin like a hot potato, and by the time I received it, the exception list was a mess of over 3,000 exceptions of dubious relevance and serious negative effects on our security. I work in a larger company and I was tasked with managing several thousand endpoints and a daunting list of exclusions that hadn't been updated in years.
