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...