Thanks for your response Chris. Regarding your suggestions:
1. Does not apply to my client's scenario.
2. I couldn't validate said sk168055 but I'll keep it in mind.
I was able to perform a kind of workaround or artifice to be able to temporarily solve the problem of installing policies.
What I did was:
- Disassociate or remove the Security Zone check "DesktopVirtuales_SegNvl" from the bond2.12 subinterface.
Then just Post. And then I re-attached it or placed the Security Zone check.
Finally, I published and installed policies. And it was installed successfully.
But it seems that this policy installation problem occurs every so often.
Does anybody know what is it due to?
What could be a definitive solution?