Error updating public folder
Be aware that since this changes ALL # items that appear to have no categories, it could cause a lot of replication.
# do Appointments determines whether appointment items are processed.
# # Syntax info: # # Examples: # .\Fix-PFItems -folder Path "Departments\HR" -split On Badchar $true -reset Empty Categories $false -do Appointments $false -do Instance Key $false -do Subfolders $false # .\Fix-PFItems "Departments\HR" $true $false $false $false $false # # folder Path should be in the form: "Top Level Folder\Subfolder\Subfolder 2" # a folder Path of "" will run against all public folders # split On Bad Char determines whether we split the category into two names, or just replace bad Char # reset Empty Categories will clear all categories on items that already appear to have no # categories.
This ensures that the categories value is REALLY empty, and should fix # items that have an empty array in the categories.
# do Instance Key determines whether we clear PR_INSTANCE_KEY on items.
Note that if this is $true # and $commit Changes is set to $true, ALL items in ALL folders that you specify will be # be modified.
If you're not sure which replica of a folder your # profile is accessing, launch MFCMapi, logon to the same profile, navigate # to the public folder, and look at the PR_REPLICA_SERVER property.
This will # tell you which replica your client is looking at.
Keeping an eye on these servers is a tedious, time-consuming process.What I have noticed is that a member of staff did this onsite with the local PF on the same LAN subnet, yet the request created a relay of the data from the secondary PF database server to the Primary PF DB server.And then the Primary at another site over the WAN initiated a connection to the client.Solution: You can use the Add-Public Folder Client Permission cmdlet to do this: If you get an error like “An existing permission entry was found for user: Anonymous.”, you can remove the permissions using Remove-Public Folder Client Permissions, then repeat step above.In my post Accessing The Information Store From Powershell, I promised I would post a real-world Outlook Object Model example in the future, so here it is.