SharePoint Information Organizer is a Farm solution. Hence, the user should be a Farm Administrator of the SharePoint Farm to install it.
Make sure SharePoint Management Shell is running in the elevated context to access local SharePoint Farm resources.
SharePoint 2010/2013 Administration service is used to install Farm solution across SharePoint Farm. It will create timer jobs to replicate the solution in front-end and/or applications servers in the Farm. Please make sure that the SharePoint 2010/2013 Administration service is running in all SharePoint servers in the Farm.
Ensure that the new managed account has sufficient permissions to access the content database of the Web Application / Site Collection. For more information, please walk through the Getting started section in the help document.
If "Cannot access local farm" error occurs on executing the batch, it means that the current user doesn't have sufficient permissions to access the Configuration database of the SharePoint server. To assign permissions to current user launch the SharePoint management shell in elevated context and type the following command, Add-SPShellAdmin user domain\user name. This provides the necessary rights for the user to access the SharePoint resources.
Yes, you can create a new dedicated service application pool to host SharePoint Information Organizer service instance for better throughput. It is the recommended practice for enterprise SharePoint application deployment. For this, you can use SharePoint Central Administration Site upon creating new service instance.
The users should have Full Control permission in the Site Collection to access the SharePoint Information Organizer features.
SharePoint Information Organizer feature can be activated from the Site Collection features page of the respective Site Collection.
SharePoint Information Organizer uses the associated managed account (so called service account of the corresponding service application pool) that was configured in the service instance creation page.
The audit records/events are stored in SharePoint Information Organizer database. These events can be viewed from the Activity log page of the SharePoint Information Organizer. Also, SharePoint ULS logs will have some more additional information for diagnostic purposes.
The recycled Lists and List Items will be stored in the Site Collection Recycle Bin and can be retrieved at any time by the Site Collection Administrator.
Unlike Lists and List Items cleanup operations, the Webs and users cleanup operations are permanent and cannot be rolled back.
Please ensure that the service account using which the SharePoint Information Organizer runs has sufficient permissions to access the content database. See the SharePoint logs for more details.
Yes, you can update metadata in bulk for multiple SharePoint Lists and Libraries using the Update Metadata feature in SharePoint Information Organizer, but it is limited to a single field at a time. However, Import Metadata feature enables the flexibility of updating metadata for multiple fields against multiple SharePoint Lists and Libraries in a single operation.
Yes, SharePoint Information Organizer supports updating metadata to an external column seamlessly. The BCS column value along with the filter name should be specified for a successful update. SIO will search for the specified column value in the LOB entity using the given filter and assign the corresponding ID (when the BCS column value match is found) of the LOB record to the external column in SharePoint. Specify this value in filter name: value format. SIO also automatically fills-up the column values associated with the BCS column during update process.
Yes, in the List and Item query page, there will be an option for Sub-Site traversal. Select this option to retrieve the Items from the Sub-Site also.
Please ensure that the current user or the specified user has sufficient permissions to access the domain from which the user details have to be fetched.
Yes, the user can selectively export metadata for specific set of fields across SharePoint Lists using SharePoint Information Organizer. Also, the Filter criteria can be used to refine the results.
The exported files are saved in the default downloads folder of the local computer.
No, the users who don't have the full control permissions in the Site Collection will get a 'access denied' error, when they try to access the SharePoint Information Organizer.
Yes, this can be done by creating a new service instance and configuring the service application associations in the Application Management section in the Central Administration Site.
Yes, using the Merge/Copy content feature the List Items can be copied to any List or Library across Web Applications.
The reference column is used to verify the existence of content in destination to perform the overwrite and versioning operations.
Ensure that the Content Type is not in use. The Content Type usages will be shown in the View/Edit Content Type Feature. Content Type in usage cannot be deleted until the usage is removed from a List or Content Type.
Since the Metadata/Content Search feature uses the SharePoint Search Service, the Search service must be provisioned (running) to use this feature. Ensure whether the Search Service is provisioned in the Server.
Yes, using the Copy/Merge Sites feature, multiple Sites can be selected and copied to a different Site Collection.
Using the Copy/Merge Sites feature, sites can be copied to a different Site Collection. Before performing this operation, the user can create a new Site Collection or a Content database or a Web Application to move the selected sites.
If the new Term Store exists in the same SharePoint Farm, the Term Store Manager feature can be used to copy the Groups to a new Term Store, using the Copy and Paste options. If the new Term Store exists in a different Farm, the user can use the Export and Import options to create the Term Sets in the new Term Store.