dsccommunity / dsccommunity/NetworkingDsc

NetConnectionProfile: does not find the interface (CIM object)

Open
#425 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

needs investigation
Dominant language
PowerShell
Stars
235
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Details of the scenario you tried and the problem that is occurring

I am trying to configure an interface profile to LocalNetwork but the resource does not find the CIM object.

Verbose logs showing the problem

TimeCreated : 23/10/2019 14:39:21
ProviderName : Microsoft-Windows-DSC
Id : 4103
Message : Job {033F100F-F592-11E9-AF98-005056A08475} :
This event indicates that a non-terminating error was thrown when DSCEngine was executing Set-TargetResource on MSFT_NetConnectionProfile DSC resource. FullyQualifiedErrorId is
CmdletizationQuery_NotFound,Set-NetConnectionProfile. Error Message is No matching MSFT_NetConnectionProfile objects found by CIM query for instances of the
root/StandardCimv2/MSFT_NetConnectionProfile class on the CIM server: SELECT * FROM MSFT_NetConnectionProfile WHERE ((InterfaceAlias LIKE 'LAN')) AND ((IPv4Connectivity = 3)) AND
((IPv6Connectivity = 3)). Verify query parameters and retry..

Suggested solution to the issue

So far I understand the error message, the resource is searching for an interface named LAN which has IPv4 and IPv6 set as LocalNetwork.

However, the conectivity type (LocalNetwork) is not the value the resource should be searching for but instead it shoud set it.

Searching an interface named LAN and setting it to LocalNetwork is the goal...

The DSC configuration that is used to reproduce the issue (as detailed as possible)

YAML format for Datum:

NetworkingDsc:
  NetConnectionProfile:
    - InterfaceAlias: LAN
      IPv4Connectivity: LocalNetwork
      IPv6Connectivity: LocalNetwork
      NetworkCategory: Private
The operating system the target node is running

OsName : Microsoft Windows Server 2019 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture : 64-bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : en-US
OsMuiLanguages : {en-US}

Version and build of PowerShell the target node is running

PSVersion 5.1.17763.316
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.316
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Version of the DSC module that was used ('dev' if using current dev branch)

Name : NetworkingDsc
Path : C:\Program Files\WindowsPowerShell\Modules\NetworkingDsc\7.4.0.0\NetworkingDsc.psd1
Description : Module with DSC Resources for Networking area
ModuleType : Manifest
Version : 7.4.0.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the NetConnectionProfile DSC resource and reproduce the configuration on Windows Server 2019 using the supplied InterfaceAlias and connectivity values. Inspect how Set-TargetResource queries the MSFT_NetConnectionProfile CIM object and compare that behavior with the requested LocalNetwork and Private settings. Done means the interface is found and configured without the reported CmdletizationQuery_NotFound error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.