We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
NetworkIpConfiguration
When using the NetworkIpConfiguration composite, it does not create the configuration in the MOF files.
I'm assuming the InterfaceAlias is supposed to have a - and be at the top of the list, which then would generate the
InterfaceAlias
-
No errors in logs/output. RSOP below NetworkIpConfiguration: Interfaces: DisableNetbios: True AllNodes\Dev\DSCFile01 IpAddress: 192.168.111.100 AllNodes\Dev\DSCFile01 DnsServer: 192.168.111.10 AllNodes\Dev\DSCFile01 Prefix: 24 AllNodes\Dev\DSCFile01 Gateway: 192.168.111.50 AllNodes\Dev\DSCFile01 InterfaceAlias: DscWorkshop 0
No changes from clone of DscWorkshop repo.
No. But if I understand correctly this is more of a Datum issue as the RSOP is incorrect?
OsName : Microsoft Windows 11 Business OsOperatingSystemSKU : 48 OsArchitecture : 64-bit WindowsVersion : 2009 WindowsBuildLabEx : 22621.1.amd64fre.ni_release.220506-1250 OsLanguage : en-GB OsMuiLanguages : {en-GB, en-US}
PSVersion 7.4.2 PSEdition Core GitCommitId 7.4.2 OS Microsoft Windows 10.0.22631 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
Using DscConfig.Demo 0.8.3
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem description
When using the
NetworkIpConfiguration
composite, it does not create the configuration in the MOF files.I'm assuming the
InterfaceAlias
is supposed to have a-
and be at the top of the list, which then would generate theVerbose logs
DSC configuration
No changes from clone of DscWorkshop repo.
Suggested solution
No. But if I understand correctly this is more of a Datum issue as the RSOP is incorrect?
Operating system the target node is running
PowerShell version and build the target node is running
CommonTasks2 version
The text was updated successfully, but these errors were encountered: