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

Error occurred when import IntuneDeviceConfigurationDomainJoinPolicyWindows10 #5465

Open
susan-nec opened this issue Nov 26, 2024 · 0 comments

Comments

@susan-nec
Copy link

Description of the issue

When I import a new IntuneDeviceConfigurationDomainJoinPolicyWindows10 policy, there was an error as followed:
{ 引数が空の文字列であるため、パラメーター 'DeviceConfigurationId' にバインドできません。 } \ Get-TargetResource、C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.24.1002.1\DscResources\MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows10\MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows10.psm1: 行 101
\ Test-TargetResource、C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.24.1002.1\DscResources\MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows10\MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows10.psm1: 行 429

contents in mof file:
instance of MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows10 as $MSFT_IntuneDeviceConfigurationDomainJoinPolicyWindows101ref
{
Description = "DomaimJoinPolicy-Discription";
DisplayName = "DomaimJoinPolicy";
ActiveDirectoryDomainName = "nec.cn";
Assignments = {
$MSFT_DeviceManagementConfigurationPolicyAssignments1ref,
$MSFT_DeviceManagementConfigurationPolicyAssignments2ref
};
ComputerNameStaticPrefix = "NEC-";
ResourceID = "[IntuneDeviceConfigurationDomainJoinPolicyWindows10]IntuneDeviceConfigurationDomainJoinPolicyWindows10";
Credential = $MSFT_Credential1ref;
Ensure = "Present";
OrganizationalUnit = "OU=workstation,CN=domain,CN=com";
SourceInfo = "D:\M365DSC\SVN\src\M365DSCTool\output\Intune\M365TenantConfig.ps1::14::9::IntuneDeviceConfigurationDomainJoinPolicyWindows10";
ModuleVersion = "1.24.1002.1";
ModuleName = "Microsoft365DSC";
SupportsScopeTags = True;
ComputerNameSuffixRandomCharCount = 12;

ConfigurationName = "M365TenantConfig";

Then, I add an Id parameter to ps1 file.
Id = "00000000-0000-0000-0000-000000000000"; or Id = "52c28ea1-4ce0-4d78-b1b9-ccb0f276b338";
But at this time, another error occured as followed:
[BadRequest] : { "_version": 3, "Message": "An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: b45b1de3-6788-44d1-b75c-31b9d8db3325 - Url: https://fef.msuc06.manage.microsoft.com/DeviceConfiguration_2410/ StatelessDeviceConfigurationFEService/deviceManagement/deviceConfigurations?api-version=5024-09-04", "CustomApiErrorPhrase": "", "RetryAfter": null, "ErrorSourceService": "", "HttpHeaders": "{}" } + CategoryInfo : InvalidOperation: ({ Headers = , b...Configuration }:) []、CimException + FullyQualifiedErrorId : BadRequest,Microsoft.Graph.Beta.PowerShell.Cmdlets.NewMgBetaDeviceManagementDeviceConfiguration_Create + PSComputerName : localhost

Microsoft 365 DSC Version

1.24.1002.1

Which workloads are affected

Intune

The DSC configuration

Verbose logs showing the problem

Environment Information + PowerShell Version

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

No branches or pull requests

1 participant