Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About user risk score
- About bulk assignment of custodians
- Configuring Metadata Framework
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Configuring Object Storage Sources
- Section VIII. Health and monitoring
- Section IX. Alerts and policies
- Section X. Remediation
- Section XI. Reference
- Appendix A. Data Insight best practices
- Appendix B. Backing up and restoring data
- Appendix C. Data Insight health checks
- About Data Insight health checks
- About Data Insight health checks
- Appendix D. Command File Reference
- Appendix E. Data Insight jobs
- Appendix F. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Configuring user impersonation in Office 365
By default, Office 365 is set up such that the admin does not have access to files stored in the users' Office 365 OneDrive Business accounts. In order to allow Data Insight to discover all OneDrive user accounts and subsequently scan those accounts, you must configure impersonation for Office 365 OneDrive Business.
To allow Data Insight to impersonate Office 365 users, do one of the following:
1. Manually configure every user account to grant Data Insight access to the files in the account.
In the Office 365 Admin Center, click
> , and select .2. configure permissions using a PowerShell script.
To configure permissions using a PowerShell script
- Copy the script given below and paste it in a text editor such as Notepad.
#Give an administrator rights on all Onedrive for Business accounts ######## #Requirements: ######## <# Powershell 4 .NET 4.5 http://www.microsoft.com/en-us/download/details.aspx?id=35588 Sharepoint Server 2013 Client Components http://www.microsoft.com/en-us/download/details.aspx?id=35585 run "Set-Executionpolicy Unrestricted" in an elevated powershell window Windows 7+ or Windows Server 2008+ #> $o365login = "<account-name>" #Username of O365 Admin $o365pw = "<password>" #Password of O365 Admin $spAdminURL = "https://<domain>-admin.sharepoint.com" #URL to your SP Admin site $spMyURL = "https://<domain>-my.sharepoint.com" #URL to your SP MySites $logfile = "$($(get-location).path)\LogFile.txt" #Logfile in case of errors #Start script ac $logfile "-----$(Get-Date) $($env:COMPUTERNAME) Session log-----`n" #build Credential Object $secpasswd = ConvertTo-SecureString $o365pw -AsPlainText -Force $Credentials = New-Object System.Management.Automation.PSCredential ($o365login, $secpasswd) #Load sharepoint module try { [System.Reflection.Assembly]:: LoadWithPartialName("Microsoft.SharePoint.Client") | Out-Null [System.Reflection.Assembly]:: LoadWithPartialName("Microsoft.SharePoint.Client.Runtime") | Out-Null [System.Reflection.Assembly]:: LoadWithPartialName("Microsoft.SharePoint.Client.UserProfiles") | Out-Null } catch { $errorstring = "ERROR: Failed to load Sharepoint Libraries, exiting" ac $logfile $errorstring Write-Host $errorstring Pause Exit } #load SPOnline module $env:PSModulePath += ";C:\Program Files\SharePoint Online Management Shell\" try { Import-Module Microsoft.Online.SharePoint.PowerShell } catch { $errorstring = "ERROR: Failed to load Sharepoint Online module, exiting" ac $logfile $errorstring ac $logfile $error[0] Write-Host $errorstring Pause Exit } #Build sP credential object $creds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($o365login,$secpasswd) #build proxy $proxyaddr = "$spAdminURL/_vti_bin/UserProfileService.asmx?wsdl" $UserProfileService= New-WebServiceProxy -Uri $proxyaddr -UseDefaultCredential False $UserProfileService.Credentials = $creds $strAuthCookie = $creds.GetAuthenticationCookie($spAdminURL) $uri = New-Object System.Uri($spAdminURL) $container = New-Object System.Net.CookieContainer $container.SetCookies($uri, $strAuthCookie) $UserProfileService.CookieContainer = $container try { $UserProfileResult = $UserProfileService.GetUserProfileByIndex(-1) } catch { $errorstring = "Critical error, unable to get profiles" ac $logfile $errorstring ac $logfile $error[0] Write-Host $errorstring $error[0] Pause Exit } $NumProfiles = $UserProfileService.GetUserProfileCount() $i = 1 $ProfileURLs = @() Write-Host "Begin discovery of $NumProfiles profiles" While ($UserProfileResult.NextValue -ne -1) { Write-Host "Checking profile $i of $NumProfiles " $Prop = $UserProfileResult.UserProfile | Where-Object { $_.Name -eq "PersonalSpace" } $Url= $Prop.Values[0].Value if ($Url) { Write-Host "Adding $Url to the list" $ProfileURLs += $Url } $UserProfileResult = $UserProfileService.GetUserProfileByIndex($UserProfileResult.NextValue) $i++ } Write-Host "Finished discovery of profiles" Write-Host "Connecting to Sharepoint Online" try { Connect-SPOService -Url $spAdminURL -Credential $Credentials } catch { $errorstring = "Critical error, unable to Connect to Sharepoint Online" ac $logfile $errorstring ac $logfile $error[0] Write-Host $errorstring $error[0] Pause Exit } Write-Host "Start processing profiles" foreach ($profileURL in $ProfileURLs) { $fullPath = "$spMyURL$profileURL".TrimEnd("/") ac $logfile $fullPath Write-Host "Processing $fullPath" try { Set-SPOUser -Site $fullPath -LoginName $o365login -IsSiteCollectionAdmin $true Write-Host "$o365login permissions added to $fullPath" } catch { $errorstring = "Failed adding $o365login permissions to $fullPath" ac $logfile $errorstring ac $logfile $error[0] Write-Host $errorstring $error[0] } } ac $logfile "Script finished" Write-Host "Job Finished" Pause Exit
- Edit the following four variables in the script:
$o365login - Replace with your Office 365 service account or administrator account username.
$o365pw - Replace with your Office 365 service account or administrator account password.
$spAdminURL - Replace with the same URL used in your organization's OneDrive URL, with -admin suffix.
$spMyURL - Replace with the same URL used in your organization's OneDrive URL, with -my suffix.
- Save the file as OneDriveAccess.ps1
- Right-click the installed Management Shell, and click Run as administrator.
- From the SharePoint Online Management Shell, change your working directory to the location where you have saved the OneDriveAccess.ps1 script.
- On the Windows Server, ensure that the execution policy is set to RemoteSigned. This permits running of PowerShell scripts for device discovery and audit data collection. To configure the policy, start Windows PowerShell as administrator, and run the following commands:
To view the configured execution policy:
Get-ExecutionPolicy
To configure the execution policy to RemoteSigned:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
- Run the following command to run the OneDriveAccess.ps1 script: .\OneDriveAccess.ps1
- Press Enter to exit.