Error code; 0x80070005-0x000004dc-0x00000524 when trying to sent an email from shared mailbox

Recently a customer was getting the error code; 0x80070005-0x000004dc-0x00000524 when trying to email ‘sent as’ from a newly created shared mailbox.

After searching online I found a lot of potential solutions like;
– Make sure only Full Access and Full control are set as permissions, do not use sent on behalf aswell.
– Start Outlook in safemode
– Create a new Outlook profile
– Use the OWA

The only thing that worked was using the OWA, but then I saw that ‘Show in global addresslist’ was set to ‘No’. When I changed this to ‘Yes’ it was working again!

I hope this helpes you out and saves you some time.

Microsoft 365 – Create an organization library

Alot of posts have been written about the late-2019 rolled out feature to create organization library’s.

After playing around a bit I’ve decided to make a short manual on how to achieve these 2 types of library’s.

General info for this topic I used is:

There are two types of Organization asset types;
1. Office templates
2. Images

The name says it all, one is to use in the office tools, the ‘images’ one you can use to create a subset of images for all people to use while editing SPO pages for example.

To create any or both of these asset types open any SharePoint online site, this can either be a community or teamsite.
On this site create 2 new Document Librarys, by choosing, New -> Documentlibrary
You can decide the names yourself but you chould use someting like ‘Office Templates’ and ‘Default Images’.

Next step is to open PowerShell as administrator.
Make sure you have ‘SharePoint Online Management Shell’ installed. To download:

In PowerShell type;
Connect-SPOService -Url
For the Office Template library:
Add-SPOOrgAssetsLibrary -LibraryURL “ Templates” -OrgAssetType OfficeTemplateLibrary
For the Default Images library:
Add-SPOOrgAssetsLibrary -LibraryURL “ Images” -OrgAssetType ImageDocumentLibrary

Where Start is your sitename and Office Templates / Default Images are your newly created DocumentLibrary’s.
For the CDN messages you can choose ‘yes to all’, more information on this:

The Default Images library should be visible relatively quick, to check this open any SharePoint online site, and choose to edit the Site, browse for an image and you should see ‘Your organization’ listed in the left Menu.

For the Office Templates it’s a little different. Here is the catch, it seems Office 365 version 1908 is not supporting these SharePoint template settings, once you upgrade to version 2005 you will see the template folder immediately.
(To update to newest version make sure you tenants settings are on the curren-channel).
Or you can also run this in an elevated command prompt:
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\ /v CDNBaseUrl if %errorlevel%==0 (goto SwitchChannel) else (goto End)
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v CDNBaseUrl /t REG_SZ /d "" /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v UpdateUrl /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v UpdateToVersion /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Updates /v UpdateToVersion /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Common\OfficeUpdate\ /f

Let me know if this helped you out.

Windows 10 – Hide ‘Personal’ OneDrive from explorer window

When you or your client is using OneDrive for Business it might be hard to explain the difference between ‘OneDrive’ and ‘OneDrive for Business’ in the Explorer view, or you just want to remove it from the list.

To do this you have to make a change in the Windows registry.

# Windows+R type; regedit
# Browse to \HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\
# Look for the Key with the value ‘OneDrive’ or ‘OneDrive – Personal’ it probally will be key {018D5C66-4533-4307-9B53-224DE2ED1FE6}.
# Now go to HKEY_CLASSES_ROOT\CLSID and find the {018D…} key, change the ‘System.IsPinnedToNameSpaceTree’ from 1 to 0.
# Save and your are done.

Windows 10 – Can’t open .heic files

Recently I came across some devices who can’t seem to open the new iPhone picture format .heic.

I found some sites stating that only Windows needs to be up to date 1903 or higher, but in some cases that still does not resolve this.
To resolve this you can install the ‘Video extensions from device manafacturer’ from the Microsoft store.

After installation you should be able to open the .heic files.

SharePoint Online Migration Tool – Scan File Failure:The item created time or modified time is not supported

When migrating to SharePoint Online / OneDrive for business, you could get the error:
Scan File Failure:The item created time or modified time is not supported

This seems because the file or folder doensnt have a (valid) creation date, in my case it had the value “4-3-1601 05:27:48”. To resolve this issue, the files need to get a valid creation / LastAccess date, to achieve this do the following:

# Open PowerShell and typ go to the folder with the files giving the error;
cd "c:\iterrors"

# Check the CreationTimme, LastAccessTim
Get-ChildItem -force | Select-Object Mode, Name, CreationTime, LastAccessTime, LastWriteTime | ft

# Get all files in the folder and change the CreationTime, LastAccessTime and LastWriteTime entry
$modifyfiles = Get-ChildItem -force | Where-Object {! $_.PSIsContainer}
foreach($object in $modifyfiles)
$object.CreationTime=("11/11/2019 12:00:00")
$object.LastAccessTime=("11/11/2019 12:01:00")
$object.LastWritetime=("11/11/2011 12:02:00")

Sharepoint Migration Tool – Invalid SharePoint Online list

When migrating on premises files to SharePoint Online / OneDrive for Business, Microsoft made a simple tool available ‘SharePoint Migration Tool’.

Sometimes you will get the ‘Invalid SharePoint Online List’ error like;
“Invalid SharePoint Online list ‘Documents'”,”ACTION_STOP”,”0x0201000D”

Thanks to Thomasssssss on this technet topic; i found the solution.

So to get this working do the following:

– If not already done, create a new migration in SharePoint Migration Tool and start the migration, when you get the ‘Invalid SharePoint Online list’ error, close the tool
– Go to C:\Users\%username%\AppData\Roaming\Microsoft\MigrationToolStorage\\Sessions\SE_RANDOMNUMBER\ and open the session.dat file with notepad.
– Search and replace every “_libraryName”:”Documents” with your local ‘libraryName’, in my case; “_libraryName”:”Documenten” and save the file.
– ReOpen SharePoint Migration Tool and resume the saved migration.

It should work now!

Convert .qcow2 file to .vhd or .vhdx

Recently we had a ProxMox environment crash and needed to restore some files inside a VM. We did not want to rebuild the Proxmox environment and could access the virtual harddisk files used by Proxmox, in this case .qcow2 files.

There is a nice tool available to convert these files to convienent .vhdx files so you can browse the virtual harddisks within Windows.

Downlad the software:

Extrac the files and open an elevated powershell windows in this folder.

Run the folowing command where c:\iterrors\vm-123-disk1.qcow2 is your source file and c:\iterrors\vm123.vhdx is your destination file.

qemu-img.exe convert c:\iterrors\vm-123-disk-1.qcow2 -O vhdx -o subformat=dynamic vm123.vhdx

Depending on the size of your .qcow2 file it could take a while to complete.


qemu-img for Windows

PowerShell – Change homedirectory permissions in bulk.

Recently I was asked to change the homedirectory permissions for >4000 users from Full Control, to ready only.

I’ve used below powershell commands to achieve this.

Firstly we need to get all SamAccountName’s in a .csv list. (Change the searchbase).

Get-ADUser -Filter * -SearchBase "OU=www,DC=iterrors,DC=com" | Where { $_.Enabled -eq $True} | select SamAccountName | export-csv c:\temp\

Afer we created the .csv file we need to run below script, this will query all users for their homedirectory path and change the permissions.

Import-Module 'ActiveDirectory'
import-csv c:\temp\iterrors.csv | foreach-object{
$homeDrive = (Get-ADUser -Identity $_.SamAccountName -Properties homedirectory).homedirectory #Query AD for the HomeDrive attribute
$user = (Get-ADUser -Identity $_.SamAccountName -Properties SamAccountName).SamAccountName #Query AD for the SamAccountName attribute
$ACL = Get-Acl $homeDrive
$ACL.setAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule($_.SamAccountName, "ReadAndExecute", "ContainerInherit,ObjectInherit", "none", "allow")))
Write-Host "Changing permissions on $homeDrive for user $user" -ForegroundColor Magenta
Set-Acl $homeDrive $ACL

Sharepoint Online – Add members and owners via PowerShell

To add members and owners to a SharePoint Online TeamSite you have the below commands avaiable:

Note that if you need to make someone Owner of the Teamsite, the user first needs to be member! And then you make the user Owner.

#Get Credentials
$credObject = Get-Credential

#Connect to Exchange Online
$ExchOnlineSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $credObject -Authentication Basic -AllowRedirection

Import-PSSession $ExchOnlineSession

#Get Groupnames

#Check for current members
Get-UnifiedGroupLinks –Identity "groupname" –LinkType Members

#Check for current owners
Get-UnifiedGroupLinks –Identity "groupname" –LinkType Owners

#Add user as member
Add-UnifiedGroupLinks –Identity "groupname" –LinkType Members –Links

#Add user as owner (first make the user ‘member’)!!
Add-UnifiedGroupLinks –Identity "groupname" –LinkType Owner –Links

#Remove user as member
Remove-UnifiedGroupLinks –Identity "groupname" –LinkType Members –Links -Confirm:$false

#Remove user as Owner (Don’t forget to also remove the Members entry).
Remove-UnifiedGroupLinks –Identity "groupname" –LinkType Owners –Links -Confirm:$false

#Extra option, turn off the Welcome Message.
Set-UnifiedGroup "groupname" -UnifiedGroupWelcomeMessageEnabled:$false

We’ve run into a problem with your Office 365 subscription after tenant to tenant migration.

After a tenant to tenant migration multiple people got the message ‘We’ve run into a problem with your Office 365 subscription’.

I found a script wroted by someone on;
How to resolve “We’ve run into a problem with your Office 365 subscription” with PowerShell

So to resolve this issue you start powershell on the PC that has the problems and run the following command.
set-executionpolicy unrestricted

Then create an .ps1 file with the following code

<# .SYNOPSIS This script locates OSPP.vbs and removes all product keys to trigger O365 reactivation. It will remove ALL product keys. .NOTES File Name: Author : Johan Dahlbom, johan[at] Blog : The script is provided “AS IS” with no guarantees, no warranties, and they confer no rights. #>
#Check that the script runs with privileged rights
if (-not([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
Write-Warning "You need to have Administrator rights to run this script!`nPlease re-run this script as an Administrator in an elevated powershell prompt!"
#Find OSPP.vbs path and run the command with the dstatus option (Last 1...)
$OSPP = Resolve-Path -Path "C:\Program Files*\Microsoft Offic*\Office*\ospp.vbs" | Select-Object -ExpandProperty Path -Last 1
Write-Output -InputObject "OSPP Location is: $OSPP"
$Command = "cscript.exe '$OSPP' /dstatus"
$DStatus = Invoke-Expression -Command $Command

#Get product keys from OSPP.vbs output.
$ProductKeys = $DStatus | Select-String -SimpleMatch "Last 5" | ForEach-Object -Process { $_.tostring().split(" ")[-1]}

if ($ProductKeys) {
Write-Output -InputObject "Found $(($ProductKeys | Measure-Object).Count) productkeys, proceeding with deactivation..."
#Run OSPP.vbs per key with /unpkey option.
foreach ($ProductKey in $ProductKeys) {
Write-Output -InputObject "Processing productkey $ProductKey"
$Command = "cscript.exe '$OSPP' /unpkey:$ProductKey"
Invoke-Expression -Command $Command
} else {
Write-Output -InputObject "Found no keys to remove... "

Then you can launch the script via powershell and all should be fine.