Issues due to multiple versions of M365DSC in regards to reporting - Test-M365ModuleValidity should be called

[andikrueger]

At the moment there are various issues that are caused by the presence of multiple versions of M365 DSC on the local system. These issues can be resolved by uninstalling the versions not needed.

The following command resolves most of the issues:

Update-Module Microsoft365DSC
Update-M365DSCDependencies
Uninstall-M365DSCOutdatedDependencies

I would suggest to introduce a new method Test-M365DSCUpdateStatus to verify if, there are updates available and/or multiple versions present on the local system. This function should be called within the repot and documentation functions and show warnings, if there issues detected.

[fldried]

so what you're suggesting is a method that just checks for multiple installations of the m365dsc module, checks if theres multiple versions installed (e.g by running

if ($null -ne (Get-Module -Name Microsoft365DSC -List)[1]) { <# uninstall outdated versions by comparing to psgallery version #> }

and the integrated method Test-M365DSCDependencies?

[andikrueger]

I would go with a function like this (sorry, I’m writing this on my mobile; PseudoCode)

$psgalleryversion = Find-module Microsoft365DSC
$localversion = Get-Module Microsoft365DSC

if($psgallery.Version -gt $localversion.Version)
Write-Host “there is a newer version of M365DSC. please run the three commands above”)

[fldried]

I'll go with your approach, changing my pr in a bit. appreciate the input :)

[fldried]

I've just pushed an update to my PR
The Uninstall-M365DSCOutdatedDependencies cmdlet still doesn't check for multiple installations of the latest version,
but it does for the Microsoft365DSC module now :)
I hope this is closer to what you imagined the extra cmdlet to do

[andikrueger]

Thanks. This is Beth close to what I had in mind.

It would be great to include this function in reporting and export cmdLets. This would solve many issues due to outdated modules.
I would go without prompting the user for input in both scenarios as this might break pipelines or automation.

[fldried]

updated again :D

[andikrueger]

Actually I think there is one thing missing. The new function is not called from the reporting mechanism, isn’t it?

[andikrueger]

Reopening this issue, as there is one part missing:

All Reporting functions within M365 should call Test-M365ModuleValidity and display a warning message.