This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Device control policy problem

Hi All,

The device control section is not functioning or being recognized. I am running SEC 4.5 and AV 9.5. I have created numerous policies to test and none are working. The SEC is installed on Windows Server 2003 R2 x64 with SP2 and the clients are installed on Windows XP SP3. Any info on this would be appreciated. Thanks

:4015


This thread was automatically locked due to age.
Parents
  • Weeellll, whatever is causing it to fail is obviously persistent. Guess you should engage support.

    I have seen (and still see) similar problems on 9.0 - computers "forgetting" about DatC or DevC or RMS seemingly not aware of them. While the mentioned folders and files exist (indicating that the component has been active at some time) the corresponding adapter file is not updated and the policy has no effect (I've written about it already). As the problem either rectifies itself or goes away after reprotect it might or might not be the same issue. I have sent one or two SDU logs to support but the case has never been resolved.

    Are others experiencing similar problems?

    Christian

    :4045
Reply
  • Weeellll, whatever is causing it to fail is obviously persistent. Guess you should engage support.

    I have seen (and still see) similar problems on 9.0 - computers "forgetting" about DatC or DevC or RMS seemingly not aware of them. While the mentioned folders and files exist (indicating that the component has been active at some time) the corresponding adapter file is not updated and the policy has no effect (I've written about it already). As the problem either rectifies itself or goes away after reprotect it might or might not be the same issue. I have sent one or two SDU logs to support but the case has never been resolved.

    Are others experiencing similar problems?

    Christian

    :4045
Children
No Data