As you may have heard/read at MSIgnite 2017, there is a new migration tool for Sharepoint to Sharepoint and Fileserver to Sharepoint migrations!
So, I will most likely discontinue maintenance of O365Migrator 🙂
Category Archives: Sharepoint Online
O365Migrator V1.00 released!
Couple of changes done, partially with the help of Alan Wallace of Oregon Tech:
- Chunked uploading of large files
- Retry of uploads (up to 3 times)
- Warning when uploading 5k+ items to the same library
- Replace _w and _t folder improvement
- No longer force a verify when uploading folders to Sharepoint
Get it here
OnedriveMapper v3.10 released!
Version 3.10 of OneDriveMapper has been released!
- handle the new tile / prompt that appears in IE login mode where Microsoft no longer always redirects to the portal
- Progress bar color is now a configurable option (cloud/non cloud)
- alphabetic ordering of configs (cloud only)
- Fixed auto update loop issue where auto update would break itself for subsequent updates.
- When restarting self (switching auth mode or auto updating) properly hide the console if this was set
Important Auto Update Instructions
If you were using Auto-Update, DO NOT do so for this version. Use the MSI to replace the old version (see last fixed issue).
New Azure AD Signin experience
As some may have read, Microsoft is previewing a potentially disruptive change without advance notice. My tenants don’t yet display the new behavior so I cannot test if OnedriveMapper will be affected. I haven’t heard of any issues yet 🙂
Get the new version here
Having issues with users synchronizing Sharepoint Libraries using the old client?
The ‘old’ Onedrive for Business client (groove.exe) is notoriously bad at synchronizing Sharepoint Online Libraries. If you want to block Onedrive from syncing Sharepoint Online libraries, just run the following command:
Set-SPOTenantSyncClientRestriction -GrooveBlockOption "HardOptIn"
Your users will receive a message to update their client.
Auditing your Sharepoint Online site collections
As, generally, we want to know what goes on in our environment, I like to enable Auditing wherever I can. Sharepoint is a more and more important resource where we store our data. Auditing can be very useful if files dissapear, auditors need specific information, or worse, cryptolockers rename all your files.
As setting audit logging through the interface is well documented, I wanted to share the Powershell way of doing this, assuming you’ve already installed the Sharepoint Client Components:
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client") | Out-Null [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime") | Out-Null
$Context = New-Object Microsoft.SharePoint.Client.ClientContext("INSERT YOUR SITE URL HERE")
$secPassword = ConvertTo-SecureString "YOUR PASSWORD"Â -AsPlainText -force
$Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials("YOUR LOGIN",$secpassword)
$Context.RequestTimeout = 16384000
$Context.Credentials = $Credentials
$Context.Load($Context.Web)
$Context.Load($Context.Site)
$Context.ExecuteQuery()
#set audit logging for the site collection to ALL
$Context.Site.Audit.AuditFlags = "All"
$Context.Site.Audit.Update()
$Context.ExecuteQuery()