Hi Kristin,
I reviewed the command you attached and found that the issue is likely related to the command syntax.
Your current command combines both install-local-package and install-product into a single LFGet operation. These are two separate LFGet commands and cannot be used together in the same execution.
For an online installation, the command should look more like:
.\LFGet.exe install-product `
--product WindowsClient `
--installation-code "XXXXXXXX" `
--iacceptlicenseagreement `
--iagreetoprereqs
Alternatively, for an offline installation, the command should look more like:
.\LFGet.exe install-local-package `
--package "\path_to_downloaded_package\WindowsClient 12.0.2603.1630.exe" `
--iacceptlicenseagreement `
--iagreetoprereqs
Please note that the command must be executed separately for each product you want to deploy. In other words, the --product parameter used with online installations accepts only a single product, not a list of products. Similarly, the --package parameter used with offline installations accepts only a single package path, not a list of package paths.
Additionally, if all you need to install are the desktop client components listed in your script, these components do not require licensing. Therefore, the following parameters are not necessary:
--licensing-mode lfds
--license-server "LFDS Server Name"
--license-database "LicenseSiteName"
If you're still encountering issues after making these changes, please provide the PowerShell error message or the LFGet log output (with sensitive information removed). This may help us better determine what's causing the issue.