Recently, I stumbled upon an article detailing how to migrate on-premises (or online) Public Folders to Office 365 Groups
Of course I had to try that out asap 🙂 I used an older script to make a report of my on prem public folders to pick one below 50GB.
It was mostly a breeze and the interface of Office 365 groups allows users to easily search and administer their old Public Folders. We purposely only use them for archive access, where the IM team manages access to the groups holding PF data. I can really recommend this strategy, especially if you can easily split them up in under 50GB sized groups.
I did have one slight error you may run into:
“MigrationTransientException: Couldn’t find a request that matches the information provided. Reason: No such request exists in the specified index. –> Couldn’t find a request that matches the information provided. Reason: No such request exists in the specified index. “
Reason for this: The source public folder path is incorrect, make sure your CSV is mapped correctly or your batch will spin forever (or at least longer than I had patience), never completing.
One of my customers is doing a full cloud-only pilot of Windows 10, Mobile (MDM) managed through Intune to leverage a least-infrastructure solution worldwide.
They’re using Azure AD, but opted out of Onedrive for Business and are using Box Drive instead.
To encourage their users to actually save data to Box instead of Onedrive or locally, I wrote a little Powershell script (since Intune native PS script deployment isn’t live yet). This script checks if Box has been configured, if not it throws a little popup to the user. If it has, it redirects My Documents, and copies any existing content from it to Box.
I used Advanced Installer to wrap this in an MSI for easy deployment through Intune, and would like to share this with you 🙂
ZIP download: configureBoxRedirection_v1.02.zip
- ps1 file which does the actual work
- vbs wrapper to run it silently (hidden windows)
- .aip file (advanced installer)
- .msi file (to roll out with Intune or other tools)
- added a caching mechanism to force Box Drive to locally cache files (normally Box only does this when they are opened)
- added a caching filter to prevent caching of files above 25MB to reduce initial bandwidth overhead
- added a 5 minute loop / wait cycle to allow box to initialize, as the script may otherwise run before Box can initialize