Endpoint Protection

I have noticed when I delete an object from SEPM, i.e. Group, Policy, etc, it stays in the MS SQL Database.

This is a problem because let us say I create test policy "ABC LiveUpdate GUP Policy" with the 5 GUP IP addresses. I apply the policy, and then delete it from SEP Management Console.

Now, I want to create an actual policy "ABC LiveUpdate GUP Policy", but let us say that I add 20 more GUP IP Addresses that are GUP servers. I then apply this policy, but the clients only use the the IP addresses of the 5 GUPs from the old "ABC LiveUpdate GUP Policy".

Then, I go into the SQL database and run the query

SELECT * FROM IDENTITY_MAP

WHERE NAME LIKE '%ABC LiveUpdate GUP Policy%'

and it outputs TWO instances of ABC LiveUpdate GUP Policy (only the ID is different). Then I have to delete ABC LiveUpdate GUP Policy.

DELETE FROM IDENTITY_MAP

WHERE NAME LIKE '%ABC LiveUpdate GUP Policy%'

Why does this happen? When I delete something from the SEP Management Console, I expect it to be deleted from the SQL Database the first time around.

I should be able to create a policy, delete it, then create a new policy with the same name without worrying about whether it will work or not.

Can someone shed some light on this? Is there a workaround for this? Is Symantec aware of this issue?

Does it remain even after the nightly maintenance runs, database logs are truncated, and indexes are rebuilt?

This is the first I've heard and being on the latest version, you can contact support if you wish

Right, wait till maintenace completes..check the policies after that in db.

Brian,

I also contacted support.

You can force the SEPM to Truncate and Rebuild Indexes. Just go to Admin >> select your DB and under tasks select "Truncate Transaction Log Now" and "Rebuild Indexes Now". See what that does. I believe there is also a nightly maintenance that runs but this happens automatically and you have no control over it.

With that said, it's odd it doesn't take affect immediately when you delete an object. Hopefully support shines some light on it.

So far, support is telling me that the deleted LiveUpdate policy should be removed from the database after nightly maintenance, but I have seen policies that were created at least 24 hours ago.

Take note of it, see what happens when you get in tomorrow and let them know if what they said should happen didn't

Were you able to get this resolved?

Thanks and take care,
Brian