Powershell: Partner CmdLets are missing or not loading

[TravisEz13]

The following CmdLets are expected to be available in Nano but are not:

• [ ] Get-DnsClient
• [ ] Get-DnsClientGlobalSetting
• [ ] Get-DnsClientServerAddress
• [ ] Get-AutologgerConfig
• [ ] Get-EtwTraceProvider
• [ ] Get-EtwTraceSession
• [ ] Get-NetAdapter
• [ ] Get-NetAdapterAdvancedProperty
• [ ] Get-NetAdapterChecksumOffload
• [ ] Get-NetAdapterLso
• [ ] Get-NetAdapterPowerManagement
• [ ] Get-NetFirewallAddressFilter
• [ ] Get-NetFirewallApplicationFilter
• [ ] Get-NetFirewallInterfaceFilter
• [ ] Get-NetFirewallInterfaceTypeFilter
• [ ] Get-NetFirewallPortFilter
• [ ] Get-NetFirewallProfile
• [ ] Get-NetFirewallRule
• [ ] Get-NetFirewallSecurityFilter
• [ ] Get-NetFirewallServiceFilter
• [ ] Get-NetFirewallSetting
• [ ] Get-NetCompartment
• [ ] Get-NetIPAddress
• [ ] Get-NetIPInterface
• [ ] Get-NetIPv4Protocol
• [ ] Get-NetIPv6Protocol
• [ ] Get-NetNeighbor
• [ ] Get-NetOffloadGlobalSetting
• [ ] Get-NetPrefixPolicy
• [ ] Get-NetRoute
• [ ] Get-NetTCPConnection
• [ ] Get-NetTCPSetting
• [ ] Get-NetTransportFilter
• [ ] Get-NetUDPEndpoint
• [ ] Get-NetUDPSetting
• [ ] Get-NetIPConfiguration
• [ ] Test-NetConnection
• [ ] Get-PnpDevice
• [ ] Get-PnpDeviceProperty
• [ ] Get-DiskSNV
• [ ] Get-PhysicalDiskSNV
• [ ] Get-Disk
• [ ] Get-DiskStorageNodeView
• [ ] Get-InitiatorId
• [ ] Get-MaskingSet
• [ ] Get-Partition
• [ ] Get-PhysicalDisk
• [ ] Get-PhysicalDiskStorageNodeView
• [ ] Get-ResiliencySetting
• [ ] Get-StorageAdvancedProperty
• [ ] Get-StorageFaultDomain
• [ ] Get-StorageNode
• [ ] Get-StoragePool
• [ ] Get-StorageProvider
• [ ] Get-StorageSetting
• [ ] Get-Volume
• [ ] Get-SupportedFileSystems
• [ ] Get-VolumeCorruptionCount
• [ ] Get-VolumeScrubPolicy

[andschwa]

Where do they come from? (What module?)

[SteveL-MSFT]

Current design decision is that PowerShell Core doesn't include system32/windowspowershell into the module path as those modules are likely not to work until they've been ported to CoreCLR. The test needs to be updated for PowerShell Core so that automodule loading expectations are different

[TravisEz13]

I verified all of these load if you add $env:Windir\system32\windowsPowerShell\v1.0\Modules to $env:psmodulepath

[TravisEz13]

@SteveL-MSFT This is not true on Nano, so it would seem we should include the path on Nano.

[SteveL-MSFT]

Per Hitesh, this should work on Nano and IoT

[joeyaiello]

@SteveL-MSFT adding High Priority here because it's something we need to close on for Nano Server by our RC.

@xumins we should talk about this in our next sync.

[SteveL-MSFT]

@joeyaiello based on our last discussion with Nano team, it seems we can take this off 6.0.0-HIghPriority

[joeyaiello]

Just to summarize before I pull this off of HighPriority: I believe the fix here is basically to somehow include system32 in the PowerShell Core on Nano when those modules are present.

[SteveL-MSFT]

@joeyaiello perhaps the way to solve this problem is a StartupConfig setting to include WindowsPowerShell module path?

[TravisEz13]

@SteveL-MSFT This fix would be specific to nano

[lzybkr]

One possible fix - we don't change PSModulePath at all, instead we create symbolic links under PowerShell Core's $PSHome\Modules path to the tested Windows PowerShell modules.

This way, we don't pick up everything from Windows PowerShell, only stuff we've tested.

[chrisfcarroll]

May I comment that although this issue is labelled OS-Windows, most of this list are things we'd want to have cross-platform, e.g. Get-Net* ?

[iSazonov]

@chrisfcarroll Could you please open new Issue and enumerate all needed portable cmdlets Get-Net*?

[TravisEz13]

Also adding how you would use them would be useful.

[SteveL-MSFT]

This specific issue should be addressed by the WindowsPSModulePath module on PSGallery

[chrisfcarroll]

Noted ; and thankyou. I opened https://github.com/PowerShell/PowerShell/issues/6076