Closed fMichaleczek closed 6 years ago
My workaround is to execute a powershell script
Execute-PowerShell >>
$DomainAdministratorCredential = [PSCredential]::new("$DomainAdministratorUserName", ("$DomainAdministratorPassword" | ConvertTo-SecureString -asPlainText -Force) );
Invoke-DscResource -Name xADDomain -Method Set -Property @{
'DomainName'=$DomainName;
'DomainNetbiosName'=$DomainNetbiosName;
'DomainAdministratorCredential'= $DomainAdministratorCredential;
'SafemodeAdministratorPassword'= $DomainAdministratorCredential;
'DatabasePath'='C:\NTDS';
'LogPath'='C:\NTDS'
} -ModuleName xActiveDirectory
>>
(
Debug: true,
Verbose: true,
RunOnSimulation: false
);
@BenLubar I'm thinking, this issue is b/c the DSC operation isn't taking into consideration a PSCredential variable (i.e. something with "that prefix").
@
, it might break. (See the pull request for details on what's allowed.)
I would like to use PSDsc xADDomain from module xActiveDirectory to create a new Active Directory forest.
Here an extract from my plan :
The error is :
Extension Windows Version is latest : 1.6.3