09-13-2017 05:12 AM - edited 03-20-2019 09:31 PM
All,
We are running into this defect and I was wondering if anyone had any success/fallout from performing the work around by use of the new policy file from the BU? We only have one cluster impacted and it's got a lot of high profile users on it and want to try and build confidence that it won't cause any other issues. If anyone has experience with this, please share!
Thank you,
Jaime Kilpatrick
12-06-2017 02:39 AM
Hi Jaime,
I have had this problem for a few days too. Could you solve it already?
Kind Regards,
Nico
06-02-2021 08:35 AM
Hi all,
We are also having this issue, please can anyone comment if is it solved using Cisco workaournd? We tried it, but problem persists
Kind regards,
Juan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide