Content that is uploaded using PowerShell or some other third party tool will create extra BLOBs in the system cache. If this method is used, running the Unused BLOB cleanup will take care of the extra BLOBs.
After performing a Bulk Recall, it may be necessary to run the Unused BLOB Cleanup job to remove BLOBs from the endpoint. The Bulk Recall no longer removes blobs if they have not passed the BLOB retention period.
The issue occurs when selecting the scope of a profile. The change button is clicked which opens a window to show the SharePoint Farm structure. If a different Web Application is selected in the upper right corner, the new window that opens shows the Central Admin page instead of the list of Web Applications.
The root cause was that the Central Admin session that was opened to access StoragePoint was not using the default internal Alternate Access Mapping.
For example, to access Central Admin someone was using http://servername.fullyqualified:100 and not http://servername:100. The default internal AAM should be used.
When Archiving, Records or Holds are enabled on a profile, the Process Existing dialog is displayed when saving the profile. This allows those newly created rules to be applied to existing content, and categorically migrate the content to the correct endpoint.
If the job is to be scheduled for a later time (process existing content at a later time, such as when most users are not online) rather than immediately, the date and time pickers are displayed below, and scrolling down may be necessary.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center
