|
This
often occurs when policy XPU levels do not match. I have run into this
when I have a custom policy that was last 'saved' at XPU (current - 1) and I
install the most recent XPU.
What
you'll have to do is open the policy and save it with the policy editor.
that should do the trick.
I
would also think that the same issue would occur if XPU's were not deployed
consistently across the network.
Best
of luck,
Jason
Bowen
NOTICE: This electronic mail message is intended exclusively for the individual or entity to which it is addressed. This message, together with any attachment, may contain confidential and privileged information. Any unauthorized review, use, print, retain, copy, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email message to the sender and delete all copies of this message. Thank you. |
- [ISSForum] Invalid policy format [EMAIL PROTECTED]
- Re: [ISSForum] Invalid policy format Thierry Bo^le
- RE: [ISSForum] Invalid policy format Maria Jose Valiente
- Re: [ISSForum] Invalid policy format Bowen, Jason (711)
- Re: [ISSForum] Invalid policy format ROBERT . SHEMO
- RE: [ISSForum] Invalid policy format Gorman, Michael
