- Introduction to contentACCESS
- contentACCESS setup package
- contentACCESS components
- contentACCESS Central Administration
- Virtual drive
- contentACCESS Web Services (Proxy)
- Central login page
- contentACCESS Tools
- Installing Outlook forms
- Legacy email archive connectors
- Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
- Legacy archive connector for Email Lifecycle Manager (ELM)
- Installing TECH-ARROW’s WinShortcutter
- contentACCESS Outlook add-in
- Tenants in contentACCESS
- General system configurations
- User interface
- Users in contentACCESS
- Login providers
- Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
- Distributed environment in contentACCESS — Clusters
- Legal hold
- Task runner
- How to create/configure databases — All databases
- Common features
- Exchange connections
- Importing contentACCESS configurations from files
- Creating new jobs in contentACCESS
- Jobs’ page, jobs’ context menu
- File Archive
- Introduction to File system archive
- File archive settings
- File archive Databases
- File archive System settings
- File archive Retentions
- File archive Storages
- Root folders
- File archive Schedules
- Provisioning settings and managing access to contentWEB
- Configuring aliases
- Configuration of jobs available in contentACCESS File Archive
- Configuration of File system archive job
- Configuration of a File system restore job
- Configuration of File system recovery job
- Configuration of Delete job in File archive
- Configuration of Remote shortcutting job
- Active/inactive documents in File system archive
- Email Archive
- Important settings before creating an Email Archive job
- Database settings
- Email archive System settings
- Email archive Provisioning settings
- Retention settings
- Shortcuts in email archiving
- Storing of archived emails
- Creating email archive schedulers
- User experience
- Exchange 2013+: Mail app in OWA 2013+ or on MS Outlook 2013+ desktop version
- Exchange 2010: OWA 2010 integration
- Address book objects
- Granting access rights for mailbox users and explicit users to view the mailbox archive
- Creating contentWEB users (option 1)
- Manage access to a mailbox archive (option 2)
- Database and store assignment in email archiving
- How to assign database and storage to an Exchange group?
- How to assign database and storage to a mailbox?
- How to move data from source database/storage into a second (target) database/storage?
- Creating Email archive jobs: archive, restore, recovery, delete, mailbox move, shortcut synchronizaion, shortcut repair
- Email archive job
- Email restore job
- Email recovery job
- Configuration of Delete job in Email archive
- Mailbox move job
- Shortcut synchronization job
- Shortcut repair job
- Public folder archiving
- SharePoint archive plugin
- Custom plugins
- accessGATE Mobile
- Virtual drive configurations
- Application settings
- Download sample for the file to be imported does not work
- Archiving is not working, if MAPI is set to communicate with the Exchange server
- Virtual drive is still appearing after the uninstall
- Outlook forms problem
- Unable to open shortcuts of archived file on the server side
- Samples are not shown using 'Show sample" option in the Import dialog
- Do I need to create separate tenants for file archiving and email archiving
- What is the recommended database size for email, file and Sharepoint archiving
- The TEMP folder is running out of space when archiving big files
- The attachment could not be opened
- After updating Exchange 2013, the EWS connection might not work in contentACCESS
- If Windows authentication is not working in contentACCESS and an alias was created for contentACCESS
- contentACCESS Outlook add-in certificate issue
- PowerShell scripts for setting up Email archive
- Solution for Outlook security patches
- Solution for Outlook security patches through GPO
12.5.SharePoint archive Provisioning settings ↑ Back to Top
The provisioning job
- Creates and updates contentACCESS users and assigns contentACCESS roles to them based on information gathered from SharePoint
In contentACCESS, a provisioning job is created automatically when activating SharePoint archive for the first time.
The process is similar for on-premises SharePoint and SharePoint online. The differences are as follows:
- Scans SharePoint groups and users, then they are snapshotted in the SharePoint archive database
- Picks users with Windows login and creates these users in contentACCESS (see more in SharePoint Archive settings, section System settings) together with Windows login
- Grants permissions to access the given SharePoint connection (archive only)
The on-premises SharePoint is working with the Active Directory and using its users and groups to grant them access to sites, folders and items.
SharePoint defines SharePoint groups, which is a collection for AD users, AD groups and other users (Azure, etc.).
The provisioning job also collects information about AD groups and their members. This is important when permissions are evaluated, because they are configured through AD groups.
Snapshot means that a copy of the user/group is created in the archive which remains even after the user or group is deleted from SharePoint. This allows to use the last known permissions for the user when working with the archive.
At the end of the provisioning job, the archive has collected the following information:
- Collected all AD groups which are somehow related to SharePoint
- Collected all AD users which are somehow related to SharePoint
- Collected AD group memberships
- Collected SharePoint groups for the given root site connection
- Collected members of the SharePoint groups
To access the folders and documents the user requires individual permissions which is synchronized by the SharePoint archive job.
The users and SharePoint groups from Office 365 are also synchronized by the provisioning job.
Azure users, together with Azure logins, are also created automatically by the provisioning job.
SharePoint Archive provisioning settings are available on the Provisioning settings page (SharePoint Archive ⇒ Settings ⇒ Provisioning settings):
The status bar of the provisioning job offers the following options:
If a scheduler has not been selected, the provisioning job can be started/stopped manually with the “start immediately/stop” control button. For manual refresh of provisioning progress information, click on “refresh” button. To enable/disable auto refresh in every 5 seconds, click on “enable auto refresh”/“disable auto refresh” button. The provisioning job can be also deactivated with the “deactivate job” button. A deactivated job will not start neither automatically, nor can be started manually. The “edit” button is used to select the node, where provisioning job will be run. The user may also rename the provisioning job here. To view further event details of provisioning job (and also to detect any potential failures/errors in the provisioning events) click on “logs” button. This will redirect you to the monitoring page, where the last run of the provisioning job will be preselected, and the last events will be shown in the events table.
The following configuration sections are available on the Provisioning settings page:
- Role to assign: This configuration section allows to assign default contentWEB user roles. It is recommended to specify here a default role with less contentWEB permissions. The roles to be assigned must be created on the Roles page.
Note: Roles containing Manage system and/or Manage tenant permissions are unavailable in the default roles’ dropdown list.
- Scheduling settings: Select the running times of the provisioning job or create a new scheduler. For more information how to configure scheduler settings please refer to section Schedules.
- Notification settings: If the provisioning job could not run properly due to some reasons, contentACCESS can send a warning about the problem. The notification email message will be sent to the email address that is set here under Recipient list option. Here you can also choose, when these email messages should be sent: only if errors occur, or when errors or warnings occur, or always, regardless of the faultless running of the provisioning job.