Open albandrod opened 1 year ago
Same behaviour trying to make a delta comparison between 2 configuration files
I can't reproduce the problem you're facing. Can you send the verbose logs, configuration and environment information, so there is more information to find a root cause?
I am seeing the same issue, but mine is for comparing only default AAD exports of 2 different tenants. Source is 7MB Destination is 1.5MB Command: New-M365DSCDeltaReport -Source '....\Source\AAD\SourceAAD.ps1' -Destination '....\Destination\AAD\DestinationAAD.ps1' -OutputPath '.\AADDelta.html' -Verbose
Output (after 30 minutes): VERBOSE: Obtaining Delta between the source and destination configurations VERBOSE: Loading file '....\Source\AAD\SourceAAD.ps1'
M365DSC version:
1.23.1011.1
Environment Information: Environment info: OsName : Microsoft Windows 11 Enterprise OsOperatingSystemSKU : EnterpriseEdition OsArchitecture : 64-bit WindowsVersion : 2009 WindowsBuildLabEx : 22000.1.amd64fre.co_release.210604-1628 OsLanguage : en-US OsMuiLanguages : {en-US}
PSVersion Table: Name Value
PSVersion 5.1.22000.1335 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.22000.1335 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
Please note: I was able to create reports for Exchange, Intune, OneDrive, Planner, Power Platform, Security/Compliance, SharePoint, and Teams.
Could you please run a quick test if this would work:
Convertto-DSCObject -Path
Hi, I got the same issue, seems to be a problem with "AADEntitlementManagementAccessPackageAssignmentPolicy" for me. I've been successful with the following:
I've tried doing "Convertto-DSCObject -Path" just stuck as screenshootbelow
Module version:
Using PowerShell 5 Windows 11
Update, did another new export of AADEntitlementManagementAccessPackageAssignmentPolicy and now it worked :) Might have been a version change between my orginal file and the new module.
@andikrueger I've added the following to my config file and think this might be the reason why it hangs:
The export is not exporting id for the group which is a bit of concern for access packages.
CC: @schmarrap
Could you run a test with the next release. This will contain some improvements in this area.
@andikrueger hello,
I have the same issue as mentioned above: parsing process for cmdlet New-M365DSCReportFromConfiguration freezes without any action. But it can be seen that Pwsh process consumes resources.
I've launched Convertto-DSCObject -Path and it freezes here:
Any suggestion?
Description of the issue
I tried to run the command stated in a VM, but it seems to take ages to parse the information, I've leaved the VM running during all night but it doesn't pass trought the first point:
I have tried with JSON, HTML and Excel as well,m with the same result. I have also tried to update the module and dependencies to the last available GA update
Microsoft 365 DSC Version
lastest version
Which workloads are affected
other
The DSC configuration
No response
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response