The first public version of the O365Datacleaner has been released.
This script can make any given path to a folder/fileshare fully compliant with Onedrive for Business or Sharepoint Online standards, without user interaction. Including path depth resolution and intelligent renaming or moving of files and folders.
A bulk version of this tool is available for free upon request and will also be posted later.
Version 2.27 of OneDriveMapper has been released.
Get the new version here
connect-msolservice : Method not found:'VoidSystem.Runtime.InteropServices.Marshal.PtrToStructure(IntPtr, !!0)'.
Getting the above? Update .NET 3.5, one of the KB’s that comes down from Windows Update will add the correct DLL version.
So you noticed the ‘All Users’, ‘Everyone’ and ‘Domain Users’ groups are missing in Office 365! That’s a pity if you have a mailbox that your whole organisation should be able to access, because Dynamic Distribution lists can’t be used as a security group.
At first, I thought this would be as simple as enabling ‘Dedicated Groups‘ in AzureAD for the tenant. But no, apparently builtin groups already exist, but are simply invisible in the Office 365 / Exchange Online interface.
So, I looked up the SID of the group I wanted to add here, and used Powershell to add the group to the mailbox’s ACL. Here’s an example, where we’re giving Everyone access to a Office 365 shared mailbox called ‘Public Calendar’:
Add-MailboxPermission -Identity "Public Calendar" -User S-1-1-0 -AccessRights FullAccess
Note: these permissions will be invisible in the web interface of Exchange Online, user Get-MailboxPermission to verify / view them.
Warning: obviously, you should never give ‘everyone’ Full Access permissions to anything.
If you assign licenses in Office 365, you’re essentially assigning license bundles. Each license usually consists of several sublicenses, like this:
In a case I ran into for a customer, the ‘Exchange Online’ component was sometimes not enabled for certain users. It took us a while to notice that the serviceplan of the main license had been unchecked. In Powershell, it would normally look like this:
Of course now we’d like to know which of our thousands of users did not have a EXCHANGE _S_STANDARD ServicePlan with a ProvisioningStatus of “Success” after the migration to Office 365.
So, I wrote the following Powershell snippet Continue reading Verifying the ServiceStatus of a specific sublicense in Office 365