Just release 5.14 with the following two new features:
As always, links/doc/info here: https://www.lieben.nu/liebensraum/onedrivemapper/
For a customer case/project, we wanted to move only recently synced/modified Sharepoint Online data from Tenant A to the user’s Desktop on the device itself.
The Desktop was synced to Onedrive for Business in Tenant B.
After copying, files from Tenant A should become read-only on the local device, and the link in Explorer to Tenant A’s sharepoint should be removed, including the actual onedrive sync relationship to prevent further ul/dl’s.
Resulting in https://gitlab.com/Lieben/assortedFunctions/-/blob/master/migrate-modifiedSpOSyncedFilesToUserDesktop.ps1
V3.24 of OnedriveMapper is now available for download.
When a user leaves the organization, their Onedrive folders/files remain until either the user is permanently deleted or the retention policy covering their data expires.
Many organizations have set up a retention policy in Office 365 to retain data in Onedrive for several years, sometimes even indefinitely.
Few know, that as long as you retain a user’s onedrive, the files and folders that were shared, by default, remain shared and accessible by those they were shared with, including externals.
This is often undesirable, and can easily be remediated by running a very simple unshare-orphanedOnedriveForBusinessSites.ps1 PowerShell function I’m hereby sharing with you 🙂
Above function detects all Onedrive Sites that no longer have an active associated user, and disables any sharing links on them.
The actual line that unshares an individual site could also be used directly if you have an automatic offboarding process.
With the introduction of Onedrive Sync Heath in the Office portal, we have a much improved view on sync errors of our users. Errors they may not even be aware of.
However, there is no remediation option, so I am sharing a framework based on previous work in Proactive Remediations that can report on the Onedrive client status and trigger a remediation, which looks like this:
Currently, the only remediation method is to restart the Onedrive client, but the script is easily adjusted for additional remediation actions or conditions the community deems useful.
When Paused or Disabled are detected, there is no remediation as this is not technically an error but something the user manually set. This can be adjusted to your local needs easily.
You can find the Proactive Remediation script on Gitlab:
https://gitlab.com/Lieben/assortedFunctions/-/blob/master/remediate-O4BClient.ps1
To use it, follow the steps in my previous article using proactive remediations (LAPS).
the only difference with LAPS config is that the script should run in user context:
The detection and remediation scripts are the same, the script is smart enough to detect if it is running in detection or remediation mode.
Credits go to Rudy Ooms for writing about the different status codes of the Onedrive client 🙂