Hey Guys!
We are currently working with Symantec to troubleshoot various issues with our ITMS 7.1 SP2 system, and some of these issues seem to stem from initial 7.0 to 7.1 migration. Right now I'm busy looking for things that seem wrong and reporting them to the group, while opening tickets for the new issues I'm seeing. This is one of those tickets.
Yesterday I was checking my 7.1 reports one by one to see where I might have reporting issues and noticed that the Software Compliance Remediation Summary report showed a policy that had attempted remediation over 2000 in just one day (over 5000 in two days). The thing is, the software used in this policy has long since been installed and shows as compliant on every PC we look at. The compliance schedule was only set to run once, yet we have this remediation running daily. This got me looking deeper into the policy (let's call this Policy A), and our desktop team brought to my attention a different policy (Policy B) that they could not delete.
They deleted all targets and software from Policy B, yet when attempting to delete the policy it said there were items referencing it and it could not be deleting. I took the GUID for Policy B and loading it in the Item Browser to see the referencing items. There are several item GUIDs referenced, with no names, and when I drill down into where those items are also referenced I see them associated with Policy A. These policies used different packages, yet they seem to have interelated reference items.
Policy B is a holdover from our 7.0 environment. I want to delete it, safely. Policy A was created by our desktop team while we were running 7.1. If we can delete Policy B and its item references I want to see if all of these remediation attempts for Policy A keep showing up in my reports.
Do you guys have any suggestions for this?
Thanks. n00b out.