SOLVED Not able to use Powershell to create Packages based on folder names

[abnrangerx67]

Hi all, I am trying to use a powershell script to create a lot of MECM packages using folder names. Script is below:

# Define paths and groups

$SourcePath = "\\TKUS001INVP003\Driver_Packages$\WIM_Packages\Lenovo"
$SiteCode = "TK1"
$DPGroup = "All Software Distribution Points"
# Import Module
Import-Module "$($env:SMS_ADMIN_UI_PATH)\..\ConfigurationManager.psd1"
Set-Location "$($SiteCode):"
# Get folders, create packages, and distribute
Get-ChildItem -Path $SourcePath -Directory | ForEach-Object {
    $Package = New-CMPackage -Name $_.Name -Path "$($SourcePath)\$($_.Name)" -Description "Imported via Script"
    # Distribute the content
    Start-CMContentDistribution -PackageName $Package.Name -DistributionPointGroupName $DPGroup
}

When I run the script, I keep getting: Get-ChildItem : A parameter cannot be found that matches parameter name ‘Directory’. If I use a literal path, it tells the path does not exist. I did some digging, and all I find is that it has something to do with the provider because I am not using the correct one. If that is the case, what is the correct provider? Oddly, every AI or chat GPT result I get for a script sample all return the same example using the Get-ChildItem -Directory. Has anyone done this, where they use folder names as the names for the MECM packages, and if yes, how?

 

[Prajwal Desai]

What is the PS version? Also, check if this helps - https://github.com/PowerShell/PowerShell/issues/24579

 

[abnrangerx67]

Hi, I was able to get it to work when I used what another person from another forum suggested, and that was to use a variable, but more importantly, make the connection to the path before connecting to the site code. I realized that whenever I was connected to the site code is when the path is not found.