To give others with a bigger public folder environment an idea of how long the SourceSideValidations.ps1 script can take, in my case it ran for almost 5 full days before finishing and producing the "SourceSideValidations.<date>.log" file. Seems like a poorly written script as the output is not friendly for converting into a CSV that you could then use to take action on the findings more easily. In my case there was just under 68k folders that needed permission changes. An example of a log entry was: "this folder \<Folder Name> permission needs to be removed for user NT User:S-*-*-**-*********-**********-**********-*****". If you look in the script you could edit the function "function checkACL($ipmFolder)" and change the output to something like this: "$errorList.Add("this folder," + $ipmFolder.Identity + ",permission needs to be removed for user," + $perm.User.DisplayName) > $null". The commas would allow you to break up the log in Excel using Text to Columns - Delimited with the comma as the delimiter. In the log it included a line of how the permission errors could be resolved (Remove-PublicFolderClientPermission <folder identity> -User <username> -Confirm:False) but in my case since it was a NT User:-S* account that represented a user or group that no longer was in our Active Directory that did not work for me. Instead I just used the script found here to roll through all public folders and remove the unresolved SIDs.