Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IntuneWindowsUpdateForBusinessDriverUpdateProfileWindows10: Assignments not exported correctly #4875

Closed
ricmestre opened this issue Jul 15, 2024 · 1 comment · Fixed by #4890 or #4902

Comments

@ricmestre
Copy link
Contributor

Description of the issue

Assignments are only exporting the property deviceAndAppManagementAssignmentFilterType but not groupId and groupDisplayName.

@FabienTschanz Running the code manually I'm getting the following below

image

Microsoft 365 DSC Version

1.24.710.3

Which workloads are affected

Intune

The DSC configuration

IntuneWindowsUpdateForBusinessDriverUpdateProfileWindows10 "IntuneWindowsUpdateForBusinessDriverUpdateProfileWindows10-IntuneWindowsUpdateForBusinessDriverUpdateProfileWindows10_1"
        {
            ApprovalType         = "manual";
            Assignments          = @(
                MSFT_DeviceManagementConfigurationPolicyAssignments{
                    deviceAndAppManagementAssignmentFilterType = 'none'
                }
                MSFT_DeviceManagementConfigurationPolicyAssignments{
                    deviceAndAppManagementAssignmentFilterType = 'none'
                }
            );
            Credential           = $Credscredential;
            Description          = "";
            DisplayName          = "IntuneWindowsUpdateForBusinessDriverUpdateProfileWindows10_1";
            Ensure               = "Present";
            Id                   = "012e7262-dc39-4156-aef8-f3d489ebabff";
            RoleScopeTagIds      = @("0");
        }

Verbose logs showing the problem

N/A

Environment Information + PowerShell Version

Win11 / PS5.1
@FabienTschanz
Copy link
Contributor

FabienTschanz commented Jul 15, 2024

Will have a look at it. At first glance no idea why that's happening, worked fine previously as I recall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants